Save MySQL/Database credentials & settings as database.yml seperate so that its not pushed to github.

[TomLewis]

I manage my configs for plugins using Github and I also use test server/prod server which use different credentials and database setups.

please can you seperate the MySQL storage settings into its own file, so that it can be git ignored so its not pushed to the github exposing sensative details.

This is also a pain when you have 2 systems, I cant have one config.yml with a single database setting as my prod is different from my local dev, so there;s no way to easily have the files push to git, because I need a separate config.yml for local testing... very easily solved by separating database connection details, its why a lot of plugins separate the database info into its own file.

[Starmism]

+1, same for my server setup which uses a shared config that has different database connection details on each server.

[Jsinco]

This probably won't be coming since our new configs #56 have allowed us to diverge the recipes, custom items, and cauldron ingredients into their own respective files (recipes.yml, cauldron.yml, custom-items.yml). You can keep your sensitive data inside your config and push your recipes.yml to github.

If this feature is still requested after implementing okaeri, then I'll revisit it.

[TomLewis]

That seems a lot neater, should have had a /recipes folder, that can either contain a single file, or multiple files, so then you can seperate events/seasons into their own files.

I will have to trial the update, I had to backdate due to a plethora of issues with all sorts of lore and whatnot, so im using an older version atm.