Add next.timeoverflow.org Capistrano deploy #525
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sauloperez
added a commit
to coopdevs/timeoverflow-provisioning
that referenced
this pull request
Nov 20, 2019
This is needed for coopdevs/timeoverflow#525 to work. Otherwise, Rails can't find the appropriate entry in `config/database.yml`. It also provides a different Rails secret for `next.
This is the upgraded server we are setting up to host the app. Time to deploy and start testing! 🎉 The Capistrano environment is tightly coupled with Rails environments so we need to add a new one called `next`.
This needed when deploying to a server for the first time or when you want to wipe out a database. The issue I'm fixing is this. Things have evolved and in https://github.com/coopdevs/timeoverflow-provisioning we no longer set things up to enable PostgreSQL extensions such as `pg_trgm`. Because Capistrano runs `db:migrate` when deploying very old migrations like `db/migrate/00000000000002_setup_pg_trgm.rb` don't work anymore. I prefer to make this step explicit in the code and with some context rather than having to do this manually in the server and let the dev in charge figure it out every time. Apparently, from capistrano/rails#118 I see this is a known issue for which there's no provided solution. I copied a solution proposed by a capistrano/rails member so should be good. Just run it as follows: ``` $ bundle exec cap staging deploy COLD=1 ```
sauloperez
force-pushed
the
add-next-environment
branch
from
a3a8bdf to
05dcbdc
Compare
|
All of a sudden the PostgreSQL 9.4 setup in Travis CI is broken 🤦♂️ Develop was green a month ago in #523 and now, restarting that same build makes the 9.4 service fail: It simply times out and then the rake task can't find any database running. We assume the risk and merge this as it's needed to migrate the production server, which we're going to do today. We'll work on fixing the build before the actual migration. |
sauloperez
added a commit
that referenced
this pull request
Dec 4, 2019
It comes installed in Travis CI boxes. This might fix the service start, which is currently timing out. See details: #525 (comment)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the upgraded server we are setting up to host the app. Time to deploy and start testing! 🎉