# content
@ozoned@social.ozoned.net Thanks for sharing! That was very useful to watch even if painful at times (mostly because I wanted to jump in with pointers but it was prerecorded :D). I took many notes of things to improve with the documentation and tooling.

Overall, the docs and tooling for deploying directly with docker (compared to those using @coopcloud@social.coop which is the recommended and simpler approach) are out of date and too complex mostly because they've been adapted from the dev ones, and we're thinking about how to offer an alternative method with only a compose file and a .env (though I'd welcome advice about how to do so in a simple way, as the just commands are mostly there to reduce the guide to a handful of steps/commands instead of having to copy paste a lot more, and they also set some variables used in the compose file to make it more flexible, but maybe that's not worth it, or there are some other ways to simplify?)

Here's some hints on the main blockers you encountered:

you first entered MIX_ENV=ember when you wanted FLAVOUR=ember

if you enter ctrl+c in iex it pauses the app so it wouldn't respond unless you unpause it (by pressing c for continue)

we recently closed port 4000 which now not open outside of docker's internal network by default (for security since you usually want people to connect through the web proxy in prod) and need to update the docs

we need to better document that it's also running a web proxy by default on ports 80/443, and point to where the caddy config is

at one point you were looking at docker-compose.yml instead of the release one docker-compose.release.yml

during of the following attempts where you tried to run dev you were still following the prod guide instead of the dev guide which uses different just commands and env vars

I'm not sure why you weren't able to connect on port 80 during the first attempt though, as the elixir app logs didn't show anything, and caddy's error log was pretty cryptic, I'd be curious what you'd see on port 4000 if you opened it in docker-compose.release.yml

@bonfire@indieweb.social

# source.content
[@ozoned@social.ozoned.net](https://social.ozoned.net/users/ozoned) Thanks for sharing! That was very useful to watch even if painful at times (mostly because I wanted to jump in with pointers but it was prerecorded :D). I took many notes of things to improve with the documentation and tooling.

<br/>

Overall, the docs and tooling for deploying directly with docker (compared to those using [@coopcloud@social.coop](https://social.coop/users/coopcloud) which is the recommended and simpler approach) are out of date and too complex mostly because they've been adapted from the dev ones, and we're thinking about how to offer an alternative method with only a compose file and a .env (though I'd welcome advice about how to do so in a simple way, as the just commands are mostly there to reduce the guide to a handful of steps/commands instead of having to copy paste a lot more, and they also set some variables used in the compose file to make it more flexible, but maybe that's not worth it, or there are some other ways to simplify?)

<br/>

Here's some hints on the main blockers you encountered:

<br/>

* you first entered `MIX_ENV=ember ` when you wanted ` FLAVOUR=ember`
* if you enter `ctrl+c in` iex it pauses the app so it wouldn't respond unless you unpause it (by pressing c for continue)
* we recently closed port 4000 which now not open outside of docker's internal network by default (for security since you usually want people to connect through the web proxy in prod) and need to update the docs
* we need to better document that it's also running a web proxy by default on ports 80/443, and point to where the caddy config is
* at one point you were looking at `docker-compose.yml` instead of the release one `docker-compose.release.yml`
* during of the following attempts where you tried to run dev you were still following the [prod guide](https://docs.bonfirenetworks.org/deploy.html) instead of the [dev guide](https://docs.bonfirenetworks.org/hacking.html) which uses different just commands and env vars

I'm not sure why you weren't able to connect on port 80 during the first attempt though, as the elixir app logs didn't show anything, and caddy's error log was pretty cryptic, I'd be curious what you'd see on port 4000 if you opened it in `docker-compose.release.yml`

<br/>

[@bonfire@indieweb.social](https://indieweb.social/users/bonfire)