Skip to content
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

Clarify reason for discouraging "simple setup" for production #64

Open
lennart opened this issue Jan 27, 2020 · 3 comments
Open

Clarify reason for discouraging "simple setup" for production #64

lennart opened this issue Jan 27, 2020 · 3 comments

Comments

@lennart
Copy link

lennart commented Jan 27, 2020

https://hoffnung3000.de/installation.html clearly states it is not recommended to use the simple setup for official festival settings. I am unsure why that is. Could you clarify and maybe add a little note on how to decide on whether to disregard the recommendation and when to follow it.

I could imagine one reason may be performance of a free heroku instance and limitations like, no automatic ssl certificates, but maybe I am missing other crucial aspects.

thanks and thanks again for the work on the project

@adzialocha
Copy link
Owner

Hi @lennart! Thank you for this!

The thing with Heroku is that it does not offer any real data storage by itself, which means all uploaded images etc. during your use of HOFFNUNG 3000 might / will get deleted at one point by Heroku. You can read more about it here: https://devcenter.heroku.com/articles/dynos#ephemeral-filesystem

For testing / trying something out this does not matter, but for a real festival-use you need to get an external storage service (like AWS) running or host it on your own server.

I will add this point to the documentation.

@adzialocha adzialocha changed the title clarify reason for discouraging "simple setup" for production Clarify reason for discouraging "simple setup" for production Feb 11, 2020
@aerugo
Copy link

aerugo commented Feb 14, 2020

@adzialocha, Urban Burn Stockholm want to set this up with Heroku, and that should be fine if they just configure the Heroku dyno to use S3 through setting the ENV vars, right?

@adzialocha
Copy link
Owner

@aerugo ah, fantastic! How cool! Yes, with using S3 for all user content you will be fine 🌟

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants