1.3 KiB
1.3 KiB
Running the service
To fully function, the service needs to run two main components:
- An HTTP server
- A background worker
By default, the mas-cli server command will start both components.
It is possible to only run the HTTP server by setting the --no-worker option, and run a background worker with the mas-cli worker command.
Both components are stateless, and can be scaled horizontally by running multiple instances of each.
Runtime requirements
Other than the binary, the service needs a few files to run:
- The templates, referenced by the
templates.pathconfiguration option - The compiled policy, referenced by the
policy.pathconfiguration option - The frontend assets, referenced by the
pathoption of theassetsresource in thehttp.listenersconfiguration section - The frontend manifest file, referenced by tge
templates.assets_manifestconfiguration option
Be sure to check the installation instructions for more information on how to get these files, and make sure the configuration file is updated accordingly.
TODO: systemd service, docker, etc.