-
Notifications
You must be signed in to change notification settings - Fork 102
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
Automatic deploy to heroku #150
Comments
So, to be certain, we are deploying our Shoes programs to Heroku or is it something else? |
We want to deploy hackety-hack.com automatically to heroku when the travis-ci build on master is green. E.g. see this blog post. However this probably is more a task for someone with access to heroku. |
It would look very much like this: steveklabnik/meloria#1 You'd have to get the key from me or someone else on heroku, though |
Oh why can't we have @rkh do that for us as well? :-) |
If it's OK I'd like to point something out. When I did the Hartl Ruby on Rails tutorial apps, I found that sqlite3 does NOT "play well" with Heroku. Hartl makes this clear himself in his Rails tutorials. I have a Heroku account. I can use Heroku so long as any app I want to push up there does NOT use sqlite or sqlite3. Heroku is fantastic and will work with MySQL, Postgrel, and I think also NoSQL. But not with SQL or sqlite3. |
We already deploy to heroku so everyone works fine :-) We only use sqlite3 in the development environment, when we deploy we use Postgres. |
what do you use Postgres for in Hackety.com? Are you saying we use something other than mongo? On Sep 6, 2013, at 3:51 AM, Tobias Pfeiffer [email protected] wrote:
|
There are some Active Record leftovers for which a normal sql database is needed, it was tried to be fixed in this pull request #146 but somehow that got stuck/did not move on. |
Travis supports heroku automatic deploys, we should have this.
The text was updated successfully, but these errors were encountered: