Deployment relies on commercial services

[almereyda]

The current deployment instructions rely heavily on the Heroku ecosystem. The application uses proprietary Heroku add-ons and extra services.

This discourages small initiatives from deploying on own infrastructure (i.e. for privacy reasons), as it is just not possible.

We should try to formulate a way to easily deploy Lumen with Docker, for example.

[stephenreid321]

It's undocumented, but Lumen does work on dokku more or less straight out of the box.

On 25 November 2014 at 00:56, Jon Richter notifications@github.com wrote:

The current deployment instructions rely heavily on the Heroku ecosystem. The application uses proprietary Heroku add-ons and extra services.

This discourages small initiatives from deploying on own infrastructure (i.e. for privacy reasons), as it is just not possible.

We should try to formulate a way to easily deploy Lumen with Docker, for example.

— Reply to this email directly or view it on GitHub https://github.com/wordsandwriting/lumen/issues/4.

[almereyda]

This answer is like a mystery of mysteries.

If you find some time to document that close to now, I would favour it over GroupServer.

[stephenreid321]

Now documented in the README

[almereyda]

Thanks. As we have Dokku available now, I can give it a shot.

[almereyda]

@wordsandwriting Regarding the latest dokku commit, it came to my mind one could also try to write a whole guide on how to run all services seperately.

I'm especially interested in substituting

• the mail service integration with something more RESTful like https://github.com/mlandauer/cuttlefish and
• Amazon S3 with any other suitable kind of object storage, preferably those compatible with the S3 API first.

Please also note Discourse, for example, switched back from S3 static assetts to local file uploads.