The provided docker config makes it easy to spin up a fully-functioning instance of the system, with separate containers for all the different components that use the example config and are configured to talk to each other.
This serves as an easy demonstration of the system for new users and also provides a useful development environment: By having each service in its own container and by using the host network driver with those containers, we can use the same config both inside the container and outside on the host system. This allows a developer who is working on the syslogsrv (for example) to quickly spin up all the other components in docker, but then run syslogsrv from the host OS (in a debugger, for example) and have them all continue to talk to each other as usual.
This provides a great development experience on Linux but sadly the host network driver is not supported on Mac so this won't work in that environment. Ideally we could find a solution that:
- Allows all services to be spun up within a container and be configured to talk to each other
- Allows developers to run all services outside of a container using the same config (and still work)
- Allows developers to run all services except one inside containers, run the remaining service outside of a container, all using the same config, and still work the same way as if they were all running either inside or outside of a container.
I don't know if this is possible today, but at the very least we can use this issue as a place to discuss potential solutions.
The provided docker config makes it easy to spin up a fully-functioning instance of the system, with separate containers for all the different components that use the example config and are configured to talk to each other.
This serves as an easy demonstration of the system for new users and also provides a useful development environment: By having each service in its own container and by using the host network driver with those containers, we can use the same config both inside the container and outside on the host system. This allows a developer who is working on the syslogsrv (for example) to quickly spin up all the other components in docker, but then run syslogsrv from the host OS (in a debugger, for example) and have them all continue to talk to each other as usual.
This provides a great development experience on Linux but sadly the host network driver is not supported on Mac so this won't work in that environment. Ideally we could find a solution that:
I don't know if this is possible today, but at the very least we can use this issue as a place to discuss potential solutions.