Describe the bug

I like the idea of this tool, however the suggested paths of this tool are pretty poor. The biggest issue I see is that it's using non-hardlink-capable suggested paths instead of more optimal paths. Here's a link to TRaSH's hardlink guide for reference: https://trash-guides.info/File-and-Folder-Structure/How-to-set-up/Docker/

In an ideal setup, you should have two mounts, one for config and one for media. In radarr's default configuration, your tool spits out three:
- ${CONFIG_PATH}/radarr:/config
- ${DATA_PATH}/movies:/data/movies
- ${DATA_PATH}/downloads:/data/downloads

Having /data/movies as well as /data/downloads as two separate mounts makes them appear as two separate filesystems (even though on the host they're adjacent paths). Instead, the example should look like:
- ${CONFIG_PATH}/radarr:/config
- ${DATA_PATH}:/data

And then in your Radarr settings, you'd set a root folder at /data/movies. This will allow hardlinks, atomic moves, and much less headache for those of us who provide support for these apps.

Steps to reproduce

Generate a compose for *arr apps

Impact

This leads to poor paths which end up causing double the storage being used, slow moves, and general headache for users.

Browser

Firefox

Operating System

MacOS

Additional information

I'm happy to help if you have any questions!