Add capistrano for deployment and setup dev/qa stages #30
Conversation
|
I think this looks good. I'll try a deployment from the office tomorrow. In the meantime, can you please fix the issues reported by Code Climate? Thanks! |
|
👍 We may want to remove https://github.com/18F/identity-idp/pull/30/files#diff-21497849d8f00507c9c8dcaf6288b136R1 although I kind of like it until we're closer to a prod env. |
| @@ -31,6 +31,7 @@ gem 'sass-rails', '~> 5.0' | |||
| gem 'secure_headers', '~> 3.0.0' | |||
| gem 'sidekiq' | |||
| gem 'simple_form', github: 'amoose/simple_form', branch: 'feature/aria-invalid' | |||
| gem 'sinatra', require: false | |||
There was a problem hiding this comment.
Was there a particular reason you moved sinatra to the main group? As far as I know, it's only needed for tests (to run the fake IdPaaS server).
There was a problem hiding this comment.
I think this was inadvertent on your part. I just put it back in the test group and the deployment worked fine.
There was a problem hiding this comment.
I added that so we can view the Sidekiq admin UI on the remote servers. We can remove that when we're closer to a production ready app or add it at a later point/separate PR.
|
I just tried deploying and everything worked fine, after making the changes I noted: moving sinatra back to the test group, and adding the ubuntu user in This should be good to go after making those changes and fixing the Code Climate issues. |
|
CC fixes en route. |
|
I'll also add a snippet to the readme with deploy instructions. |
jgrevich
force-pushed
the
cap-deploy
branch
3 times, most recently
from
8694b38
to
edb5088
Compare
|
FYI, |
|
🚀 |
|
I looked into phony_rails. It's not that the method was removed, it's that they introduced a bug: joost/phony_rails#140 |
Better default certificate, install notes explaining the situation.
…adata Remove single logout service from metadata
This adds capistrano3 support so we can deploy to remote servers. I setup
devandqaenvs at https://upaya-dev.18f.gov and https://upaya-qa.18f.gov. They should be fully functional aside from SMS support; I need to setup a twilio subaccount and dev account to get that working.To deploy to a remote server use
cap <env name> deploy. We may need to whitelist your IP if you're not using the GSA VPN or in a GSA building. Similarly we'll need your ssh pub key (I have everyone from save-ferris). I created a base image with all of the OS deps and the app fully installed in case we need to spin up more envs. This should be converted to a cloud formation template if we're going to use this more often.