Entities to use for the api
Controllers to use for the api
Will be called to get the current user based on the current request
Will be called for each request and can be used for configuration
Will be called once the server is loaded and the data provider is ready
Data Provider to use for the api.
Will create tables and columns in supporting databases. default: true
when set to true, it'll create entities that do not exist, and add columns that are missing.
The path to use for the api, default:/api
If you want to use a different api path adjust this field
The default limit to use for find requests that did not specify a limit
When set to true (default) it'll console log each api endpoint that is created
A subscription server to use for live query and message channels
A storage to use to store live queries, relevant mostly for serverless scenarios or larger scales
Used to store the relevent request info for re running a live query
Storage to use for backend methods that use queue