Configuration
Platformatic Node is configured with a configuration file. It supports the use of environment variables as setting values with configuration placeholders.
application
Supported object properties:
basePath
: Service proxy base path when exposing this application in a composer when setting theproxy
property. If not specified, the service will be exposed on the service or a value specified in the service code viaplatformatic.setBasePath()
.outputDirectory
: The subdirectory where production build is stored at when usingwattpm build
orplt build
. The default isdist
.include
: The paths to include when deploying the service. The default is['dist']
.commands
: An object specifying the commands to manage the application instead of directly executing the service entrypoint. Supported commands are:install
: The command to execute to install the service dependencies. The default isnpm ci --omit-dev
.build
: The command to execute to build the application.development
: The command to execute to start the application in development mode.production
: The command to execute to start the application in production mode.
node
Configures Node. Supported object properties:
main
: The entrypoint of the application. This is only needed if themain
property is not set in the servicepackage.json
file.absoluteUrl
: If set totrue
, then the service will receive the full URL from a Platformatic Composer. The default isfalse
.dispatchViaHttp
: If set totrue
, then the service will serve requests coming from the mesh network via a TCP port.disablePlatformaticInBuild
: If set totrue
, then no Platformatic code will be started when running thebuild
command.
logger
Configures the logger
, see the runtime documentation.
server
Configures the HTTP server, see the runtime documentation.
watch
Manages watching of the service, see the service documentation.
Issues
If you run into a bug or have a suggestion for improvement, please raise an issue on GitHub or join our Discord feedback channel.