Have more clear Docker documentation

[DrakkoFire]

In the docs for NX Daemon it gets very short when it comes to Dockerization, now the NX Daemon is the main engine for hot reloading our apps, it gets a little confusing with Docker installations, as even when we customize the Socket location and map it to the containers it doesn't really work as the Daemon keeps saying it's off.

I think a more extensive documentation with examples on local dev Docker setups with docker-compose would be greatly appreciated, as I have a Nest app, and I'm not sure what alternative I have to NX Daemon when it comes to Hot Reloading with NX apps.

Thanks !

[isaacplmann]

The daemon is unrelated to Docker, but you're right that we need more documentation on how to use Docker with Nx. Unfortunately, I don't have much experience with Docker. It is on my eventual todo list to work with someone on the team who does use Docker regularly.

Alternatively, I'd be happy to work with you, if you want to contribute some documentation.

[DrakkoFire]

What would the procedure be then if we want to start a microservices app, without using the NX Daemon?

In my case it was a early on setup, so I decided to drop the microservice functionality and switch my back-end to Laravel for simplicity, but I would still be interested in having access to hot reload from my containers, as I have some clients setup in NX, it would make my life easier, in previous versions without the Daemon it was easy, as you would just map your code into the container and it's done, hot reload will look for changes kinda like nodemon does, but now I have no clue how it should be done with the Daemon, I've tried mapping the sock into the container, didn't work, tried to generate a new sock inside the container, didn't work, so I'm a little lost there, I have to run the app locally instead of in a container.

If I can help I would be happy to squeeze some time to help ! Just let me know

[isaacplmann]

It sounds like you're referring to any command run with the Nx CLI as the Nx Daemon.

The daemon is a background process that recalculates your repository's project graph asynchronously so that the next time you run an Nx command with the CLI, the project graph calculation is already done and you command will execute faster.

When you start an app, you'll run nx serve myapp or you might use something like nx watch ... to automatically run tasks when the files change. Both of those commands are made faster by the daemon, but neither directly invokes the daemon. Does that make sense? Am I misunderstanding what you're saying?

[jaysoo]

The daemon and file watching should work in a docker container just as they would on your host machine.

If there are specific problems, a repro and a new issue would be very helpful. For now, I don't think there's any actionable items from this.