Customize a micro's startup

Goal: adjust how a micro starts in native mode (a Maven multi-module, some jvmArgs, a specific property) without touching its repository. All of this lives in your settings.local.yml (non-versioned) except the pre-commands, which belong to the team.

It’s in the micro’s editor → Local startup configuration.

The day-to-day (always visible)

• Database — point at another DB.
• Startup script / command according to the stack.
• Pre-commands — what runs before starting the micro, in order and only the checked ones: build the workspace libraries, install the sibling modules of a Maven multi-module, generate code… They accept ${mvn} (the repo’s Maven, its mvnw if it has one) and ${port}. They live in the manifest: valid for the whole team. You can uncheck one to skip it without deleting it.

Advanced (collapsible)

• Extra arguments — added at the end of the command (in JVM, JVM arguments; in Node/Angular, the script’s flags).
• System properties and environment variables — one per line, key=value.
• Full startup command — entirely replaces the command MicroLab generates (the ports and URLs are still added when running it).
• Preview — the template of the effective command that will be run.

Import and export

A micro’s startup configuration can be exported/imported per file, to move or share it. From the CLI: microlab run show|set|clear|preview|export|import.

See also

• Native vs container mode · Micros section