4 ms·
I was going to come comment that there must be a good way to solve this, since the Ruby community has such a rich ecosystem of tools. Heroku, for example, has
by bhuga 11y ago
I was going to come comment that there must be a good way to solve this, since the Ruby community has such a rich ecosystem of tools.
Heroku, for example, has a nice one-click deploy button for Rails (and many more languages/frameworks). It works straight from the source code, such as with this open-source rails app, and it's really quite impressive:
https://github.com/heroku/starboard#deploy-the-app https://github.com/heroku/starboard#deploy-the-app
The author also calls out error reporting as being terrible. And there's also great tools for managing that, such as newrelic and airbrake.
So surely this author was just unused to the tool ecosystem, I thought. What a perfect opportunity for a constructive yet snarky comment! But lo and behold, discourse has deprecated all non-docker installs:
https://github.com/discourse/discourse/blob/master/docs/install-HEROKU.md#warning-this-guide-is-deprecated https://github.com/discourse/discourse/blob/master/docs/inst...
I was, and am, completely baffled at that decision. And I learned a valuable lesson about trying to out-snark snarky blog posts.
- riking 11y ago> The author also calls out error reporting as being terrible. Actually, he never got far enough to see the error reporting tool, Logster.
- dikaiosune 11y agoSupporting multiple deployment options introduces a lot of overhead, and Docker (in particular) seems really good at reducing deployment overhead for both developers and admins. I'm not sure why it's a bad thing when it means that the team can focus resources on a single canonical deployment method that just works. Docker containers can also be run on a variety of public cloud services, so while Heroku may not be available, pointing your Dockerfile at EC2 or GCE shouldn't be too hard?