The Basics
Configurations
Configurations or "configs" are where you define your application settings.
Overview
Our configuration setup is closely integrated with Laravel's existing configuration setup. Upon making a request we essentially merge and overwrite the existing Laravel configs with the data stored in our config table and then cache the settings to prevent fetching the data again for subsequent requests.
You should know!
It's important to note that we don't allow every setting to be accessed that you may be able to access in a standard Laravel application. Also, for security purposes, we only send application config data to the client.
Upon the creation of a project, two configs are added to the configs table by default, one for your application and another for your database connection credentials.
Application Config
The application config is where you can define your application settings. This includes things like the name of your application, the URL, and other settings that you wish to apply to your entire application for example, setting a meta title at application level would result in every page in your application defaulting to this meta title.
Database Config
You can setup your own database connection using the config when you're using our Editor which is why it is created by default as most users are likely to want to work with their own database given that you cannot create tables using our database which is obviously very limiting.
You can review the full Configuration API specification here.