Create .deploy/ space and move nginx config there

[abitrolly]

No description provided.

[staaas]

@abitrolly can you briefly document your plan?
that will be easier to review prs having that in mind. we'll also be able to help with some steps if we understand your intensions.

[abitrolly]

@nott the plan for now is to move scripts related to deployment into .deploy/ dir

[abitrolly]

This particular PR is needed to make nginx config readable.

[staaas]

i don't see much difference here

[abitrolly]

nginx config can be put into repo root, but there is already too much files irrelevant to Django application there.

[staaas]

@davojta what do you think?

[davojta]

I think move all deploy relate files to separate folder is good point. If it doent anything working right now.

[abitrolly]

I will get back to it in after 14th of December. Docker is awesome. @nott is there any tools to measure memory, CPU and disk space footprint of those containers? Ideally I want to run it and then freeze, and then get immediate and average values.

The point is to have bare minimum necessary for deployment in root, and move everything else to .deploy. This way I, as administrator, could get quick overview of deployment requirements without getting too deep into application structure.

[staaas]

@abitrolly I have plans to get rid of nginx and replace it with haproxy
let's close this pr

[abitrolly]

@nott I don't see how HAProxy is different from Nginx in this context. I want the ability to edit and copy servers configs without Docker.

So if you agree that embedding config files for one app as strings into config files of other app is a bad pattern, let's discuss it further - where should we place your new HAProxy configs, so I can move current stuff there for now.

My problem with current solution "configs as Dockerfile stings" is that I can not read through quoted \n at line ends, and my syntax highlight doesn't work there.

[staaas]

@abitrolly

I don't have strong opinion about place for configuration

• if they are small, I see many benefits in embedding them into Dockerfiles
• however I also see your concerns

We can just remove production.yml and Dockerfile-nginx for now.