Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Come Up With A Deployment Strategy #82

Open
nodanaonlyzuul opened this issue Jan 18, 2018 · 1 comment
Open

Come Up With A Deployment Strategy #82

nodanaonlyzuul opened this issue Jan 18, 2018 · 1 comment

Comments

@nodanaonlyzuul
Copy link
Contributor

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.

@allthesignals
Copy link

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants