Create some basic deployment-behind-a-http-front-end configuration examples.

[ribasushi]

Both novices and experienced administrators would benefit from short samples describing typical deployment of go-ipfs fronted by an authenticating nginx or apache http server.

Novices would benefit from a dramatic reduction of the cognitive overload needed to deploy an IPFS node with a let-sencrypt wss-enabled listener and an exposed 5001 API with the proper basic http access controls.

Experts would benefit from eyeballing such a sample config and going "ok, all of this is as I expect it" / "oh, this piece here looks odd, I need to read more"

cc @autonome @lidel

[welcome[bot]]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review. In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additiona round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment. Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

[autonome]

This is a really common use-case, and gets asked all the time. Yes, please to a detailed step-by-step guide.

[johnnymatthews]

This sounds very handy. Would you be interested in creating a draft for this @ribasushi, or tagging someone else that would?