Adding a guide/an aid for deploying prologue web applications #167
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a PR to add instructions for deploying a prologue webapplication.
Disclaimer:
I do not claim to be a good guide writer, neither do I claim that this is in any way a finished piece of text.
This is merely my first draft that I wanted to submit for further refinement in discussion on what should be cut out, added or restructured.
I do not care how much of it remains the way it is or if somebody else rewrites this or what not.
My only goal is that after this PR is merged, that there is some guidance on how to deploy a prologue webapp for beginners like I used to be.
I welcome pretty much any feedback (or even better: additions!) to this aid to make it as useful as possible.
Things I could further include but didn't since I didn't see where:
I've made pretty good experiences with an alpine image that got glibc frankenstein'd onto it:
frolvlad/alpine-glibc
It leads to really small image sizes (30MB for my project!), but there's a decent amount of people advising against it.
Things I think would be neat but could not figure out myself: