easy deploy to heroku button #86
Merged
Conversation
This file contains 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
- this is used by Mesa team to post to a Slack channel, but we don’t want every deployment in the world to post in there. - also, this add on needs an extra parameter (the url of the slack web hook) and since it wasn’t included in the config, the deploy was failing.
we only need one database.
- adds new rake task app:deploy which in turn calls `db:migrate`, `council_districts:load`, and `legistar_all:refresh`. - uses task in app.json for auto deploy and in README
- Note that currently the website and repo url are the same but that may change eventually (if we create a github pages landing page for instance).
- stack must be cedar for this to work (see #42). - region is almost always going to be in the US, at least for now.
- 2.1.2 is recommended on Heroku: https://devcenter.heroku.com/changelog-items/468 - `debugger` gem does not build on 2.1.2; switching to `byebug` `bye bug` is the recommended debugger for current Ruby + Rails (see cldwalker/debugger#125 (comment) and rails/rails#14533) - The following commands may help in switching your local version (assuming you use rbenv): rbenv install 2.1.2 rbenv local 2.1.2 gem install bundler bundle
Heroku support says: “I’m afraid our interface or the app.json format doesn't currently allow this. Our API does, but this probably wouldn't fit your use case.”
After testing, this didn’t seem to have any effect.
tbuckl
added a commit
that referenced
this pull request
Nov 3, 2014
…oku-button easy deploy to heroku button
|
question: how does the deploy to heroku button work? can we configure it to have different database (paid and not paid)? thinking about using github deploy for testing (free) and then production (paid?). |
|
@buckleytom AFAIK there isn't much possibility of that kind of configuration. I think that once we completely eliminate the PostGIS requirement we can make the default |
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 fixes #42
Important note:
It also does these things:
debuggergem doesn't work anymore.app:deployrake task which calls the tasks to migrate the database and load districts + legistar; the app.json uses this one global task and I update the README to reflect this new-found simplicity.