3 ms·
You sound like a Python guy, but that's exactly how Heroku works. It totally sold me on the idea of just pushing to your production/staging repo to update a ser
by dickeytk 16y ago
You sound like a Python guy, but that's exactly how Heroku works. It totally sold me on the idea of just pushing to your production/staging repo to update a server.
I imagine to set it up yourself would be a bit of work, but it sounds like you have continuous integration built in? That's cool.
- senko 16y ago> you have continuous integration built in? Well, it's not specifically continuous; I do manually run the script when I want to make a deployment. But I make it a point for my (main) master to be the same code as is in the production. So I work in smallest possible changes (one feature, or one bugfix), push to main repo, and run the deployment script.
- dickeytk 16y agoright, CI was the wrong term there, just that you're using your automated testing to make sure your deployments won't crash. This really is the way to go for developing software, deployment should be painless. I would like to see some sort of drop-in tool you could put on your own server without having to configure all the post-commit hooks. Although, that's probably a pipe dream.
- chrisaycock 16y ago> that's exactly how Heroku works $ git remote add heroku git@heroku.com:myapp.git $ git push heroku Just beautiful. http://heroku.com/how/workflow http://heroku.com/how/workflow
- dickeytk 16y agoyeah I freaked out when I first saw how it worked. Everyone was annoyed with me. I don't even want to make webapps that aren't ruby with heroku around.