similar to DATAPACKS_FILE, a similar variable for auto downloaded mods may be nice.
DATAPACKS_FILE has the neat function that if changed, i dont have to compose up and down to apply, i can just restart the container. e.g. with MODRINTH_PROJECTS, i need to recompose the container / stack.
MODRINTH_PROJECTS_FILE would be nice, since its changeable like the datapack file
personal gripe: i use version control and have my modrinth stuff in a modrinth.env file. while fine since no secrets, including .env files in git always icks me a bit
I don't quite understand the problem though with re-running docker compose up to reapply the changes. You mention "stacks". Is it because you're using Portainer?
Enhancement Type
Improve an existing feature
Describe the enhancement
similar to DATAPACKS_FILE, a similar variable for auto downloaded mods may be nice. DATAPACKS_FILE has the neat function that if changed, i dont have to compose up and down to apply, i can just restart the container. e.g. with MODRINTH_PROJECTS, i need to recompose the container / stack.
MODRINTH_PROJECTS_FILE would be nice, since its changeable like the datapack file
personal gripe: i use version control and have my modrinth stuff in a modrinth.env file. while fine since no secrets, including .env files in git always icks me a bit