You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can override the default config values in your project's config/midcom directory by creating a subfolder named like your component (e.g. net.nehmer.blog) and creating a file called config.inc. Settings are merged, so the ones you don't override will still use the component defaults.
If you don't want to store your configuration in the filesystem, you can also save it in the database in a special Snippetdir called sitegroup-config. To configure a component, a Subsnippetdir with the name of the component has to be created, and then a Snippet named config.
Additionally, you can also set config values for specific Topics, which are then saved as Parameters in the database. These take precedence over both the component defaults and the project config/sitegroup-config values.
If you provide an appropriate [Datamanager Schema](Datamanager Schemas) component configuration can be done in the UI, either in the Asgard backend, or via the MidCOM Toolbar.
This documentation is very much a work in progress, and pull requests