Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Config split (env specific config) #55

Open
boazpoolman opened this issue May 8, 2022 · 2 comments
Open

Config split (env specific config) #55

boazpoolman opened this issue May 8, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@boazpoolman
Copy link
Member

Feature request

Summary

Have subdirectories inside config folder like dev or prod. In there you could place config files to overwrite the config for specific environments.

Why is it needed?

To have different config in different environments.

Suggested solution(s)

Subdirectories inside the sync folder in which you can override the config. Could be used for env specific config, but maby also for logic based config split.

@Achder
Copy link

Achder commented Aug 30, 2024

I noticed this is quite an old request. Is there any progress?
Right now we are excluding some configs from our sync that have data specific to staging or prod environment. In particular the core-store.plugin_users-permissions_advanced config. I saw an environment attribute in the config itself. Is it maybe already possible to create specific files for staging and prod?

@boazpoolman
Copy link
Member Author

This issue has not been worked on since it's creation.

As you noticed the core-store table actually has an environment column which suggests that you can specify different configs for different environments. I haven't played around with this, and haven't seen any documentation about it in the Strapi docs. But it's worth trying out!

Do post your findings here if you've figured out a way to make it work :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants