[Feature Request] Add systemName config option

[benface]

There's already isSystemOn and timezone so I think it would make sense to add systemName.

[brandonkelly]

Do you have a use case for it, especially where it would make sense to customize it on a per-environment basis? If you just want to be able to edit it in code, that is already possible in 3.1 by editing the system.name value in config/project.yaml.

[benface]

It's mostly, like you said, to be able to edit it in code, and not so much because it would change per environment (although I can see a use case where someone would want to append (Staging) to the system name for clarity). So for me, the project.yaml solution is great. Thank you :)

[brandonkelly]

Cool :)

[leevigraham]

@brandonkelly I also wanted this so I can flag if the system is Local / Dev / Prod in the siteName. Also we have a boilerplate and we control a lot of settings / labels from the .env file.

[khalwat]

@leevigraham sounds like a good use case for https://github.com/TopShelfCraft/Environment-Label

[brandonkelly]

@leevigraham Next release will allow you to set your System Name setting to an environment variable.

[leevigraham]

👍🏻 Looks like the way Craft is moving is that env variables are going to be used in fields in the admin rather than config overrides?

[brandonkelly]

Yep, config overrides make less sense now that things are stored and shared in project.yaml (especially sensitive data). If something needs custom values in different environments, better to have the actual config-stored “value” just be a reference to an environment variable.

[khalwat]

Only argument I could make would be for plugin settings in a multi-environment config, and there only because I'd hate to see my .env with tons of entries in it, none of which are scoped.