Getting Started with Docker Compose in README issues

[megastary]

In the repo README, the Gettings Started guides is to clone repo, copy .env, modify them and start docker compose.
Sadly the docker-compose.yaml does not use .env file, instead it overrides them directly in docker-compose.yaml

Also for the love of Git, can we in new projects such as this one use modern syntax and not drag deprecated things into it?
Just for docker alone you should:

• Rename docker-compose.yaml to compose.yaml (proposed in 2021 and at least from 2024 it is already as prefered name in offical documentation)
• Drop version from the compose.yaml alltogether (also thing from 2021, docker compose now complains each time you use compose file using version string)
• In example do not call docker-compose command, it has been replaced by plugin and is called docker compose now.

[pierre-b]

thanks for the feedback, to be honest the docker compose file has been generated by Claude Code and as long as it worked for testing I didn't mind much... but your point is totally valid, let's increase the standard as much as we can! I'll update it when I'm back to home in 2 days 🙏

[megastary]

Thanks for quick reactions on this and other issues! Honestly the project looks really promising already. Very amazed how young project can look almost finished, just need to polish out bugs.
Looking forward to using it to send internal newsletters from our department to the rest of the company, Keep it up!

[pierre-b]

The https://github.com/Notifuse/notifuse/releases/tag/v14.0 is now live and provides a compose.yaml file and a link to the official docs instead of an outdated README!

[bilogic]

if I may, there should be 2 sets of compose.yaml

1. For development/testing, can use build: .
2. For production, should be standalone (copy the YAML to start the container and not git clone) and using only docker hub image (not build)

Would also be a bonus if batteries came included, i.e. include database service in the YAML