Is it possible to add a custom startup command?

[ISensuiI]

I am not sure whether loco currently supports custom startup commands like clap.

For example, my current problem is that I have added all the configuration options to dev.yaml. Start it with -e. But some options are single choices. For example, I have a startup mode RELAY/NDS mode, and only one of these two modes can be run. Suppose I need to run these two modes on the same server. I can only run one of the modes first, then modify the configuration file, and then start another process. Or copy them. Is it possible to add a custom parameter?

In this way, I can specify the mode through -mode without modifying or copying yaml

I searched the loco manual and did not find the relevant custom commands

[kaplanelad]

Hey @ISensuiI,

I'm not entirely sure I understand your use case fully — could you share the exact command flow you're using? That would help clarify things.

[ISensuiI]

iroh:
###### iroh public related configuration ######
iroh_common:
# Operation mode
# Relay mode
# DNS mode
common_mode: "dns"
# Maximum room limit per service
common_max_room: 128
# Default starting IP of the room
common_room_start_ip: "10.0.0.10"

common_mode This is my network module after startup. There are 2 modes, relay dns. Suppose I am currently running relay mode. But I want to start dns mode while relay is still running. I can only modify this configuration common_mode dns. Then start dns mode.
In general, the configuration file is fixed and not flexible enough. Although I can solve the current problem by building 2 configuration files such as confg-dns.yaml config-relay.yaml. But this method is very clumsy and there is an extra configuration file.

But if we can customize the command, I can solve this problem without modifying the configuration file by using cargo run -e config.yaml --mode relay/dns . In fact, it is a similar method to clap.

[kaplanelad]

Got it. It's not possible to extend the default Loco CLI with custom startup arguments like --mode.

You have two options:

1. Setup via environment variables
2. Disable the cli feature by take full control by disabling the built-in CLI and implementing your own.