Best Practices: Site Level Variables
Unanswered
Northeast Congo Lion posted this in #help-forum
Northeast Congo LionOP
Is there a best practice of where to store site level variables that are configurable by the site admin team. Stuff like maybe "site name" or "site description" or "logins disabled"
I realize .env can hold stuff that is changed at the developer level but what about stuff an end-user would set.
In the olden days I'd probably store these in the database with a settings table where each row was a separate setting. Is that still how its done or is there a new approach to this?
Thanks
I realize .env can hold stuff that is changed at the developer level but what about stuff an end-user would set.
In the olden days I'd probably store these in the database with a settings table where each row was a separate setting. Is that still how its done or is there a new approach to this?
Thanks
4 Replies
@Northeast Congo Lion Is there a best practice of where to store site level variables that are configurable by the site admin team. Stuff like maybe "site name" or "site description" or "logins disabled"
I realize .env can hold stuff that is changed at the developer level but what about stuff an end-user would set.
In the olden days I'd probably store these in the database with a settings table where each row was a separate setting. Is that still how its done or is there a new approach to this?
Thanks
yes user-edited variables can be implemented with a persistent database
@Rafael Almeida yes user-edited variables can be implemented with a persistent database
Northeast Congo LionOP
right can be. but is that still considered best practice or common practice?
that's like the only way to do it 🤔
Northeast Congo LionOP
great sounds like commonly practiced to me 🙂 thanks