What do you mean using only cowboy? It uses only cowboy by default, so unless you changed it?
OvermindDL1
mmmrrr
I think @Nvim meant how to deploy a phoenix application without a reverse proxy like nginx in front of it. Hence the “only cowboy”.
Op: I think you should not forgoe setting up a reverse proxy in front of you application. From an ops perspective it is probably much easier to integrate nginx with an automated SSL setup. Also you get things like rate limiting, basic auth, static file handling, etc. out of the box with nginx.
It seem the advice by @gutschilla is solid.
Personally I deploy elixir projects via GitLab CI and some bash-scripts…
4
Nvim
yes but how do you set up in a VPS? For instance run mix.phx.server automatically? A complete step by step guide would be helpful.
0
NobbZ
Usually you don’t, you use releases in a docker instead or bare, and their lifecycle be managed by docker or systemd respectively.
Distillery has documentation for both variants.
3
Qqwy
TypeCheck Core Team
I wrote a guide a while back ago as well, which very much uses the stack you desire: Using LetsEncrypt with Phoenix (behind Nginx). How to make this more optimal?
1
OvermindDL1
I deploy docker’s for my personal projects. At work I deploy into a systemd management full VM, so systemd manages all the launching and so forth. I’ve documented how in PidFile - create and manage a PID file from the BEAM process if curious, but I recommend docker when possible.
3
Exadra37
Do you have any guide how you are doing your releases with Docker?
I am building an Elixir Docker Stack for development, but I would like to also include a release and deploy command 
0
OvermindDL1
No guide but nothing special about it. I just have a builder image that brings in otp/elixir/rust, builds, then copies the compiled release to the main image and run that, nothing special or out of the norm.
Why would you need a release or deploy commands? The ‘release’ is building the image, the deploy is loading the docker image, docker handles it all.
0
Exadra37
You mean that docker does docker build --tag organization/project:tag .?
So this is what I want to wrap in the Elixir Docker Stack, plus the build arguments. Basically just a simple wrapper around this command, that will use a Docker image in the root of the project or a default one provided by the stack.
When i used the term deploy I was not referring to docker deploy, but instead to a command to deploy the release into the target server.
If I end-up to include the release and deploy commands in the Elixir Docker Stack, they will target only pet projects that we deploy to the likes of Digital Ocean, Linode or similar.
0
OvermindDL1
I don’t even make a wrapper because I make a different tag much of the time (so I have a couple old versions around in case I need to switch back to them quickly), it’s simple enough as it is. 
I use docker swarm with docker compose for that, so it’s still docker. ^.^
0