Brett and I have discovered that although this app...
Makes reference to Capistrano in its README.
Contains Capistrano files
It does not use Capistrano for deployment.
Its files reference timwaters/mapwarper and ./config/deploy/[ENVNAME].rb reference
either servers that aren't ours or the auto-generated boilerplate.
Also, logging onto our qa and production servers, there isn't the familiar Capistrano /releases & /current directory structure/.
If this app continues to live on our servers - we should probably use Capistrano to require
less human intervention during deployments.
@NYCPlanning is trying to deploy to this for a side project. Interested in bumping this conversation - it seems like the documentation is missing some information.
Brett and I have discovered that although this app...
It does not use Capistrano for deployment. Its files reference
timwaters/mapwarper
and./config/deploy/[ENVNAME].rb
reference either servers that aren't ours or the auto-generated boilerplate.Also, logging onto our qa and production servers, there isn't the familiar Capistrano
/releases
&/current
directory structure/.If this app continues to live on our servers - we should probably use Capistrano to require less human intervention during deployments.