Malai 0.3 - A user defined config file and better identity handling

[siddhantk232]

We will create a 0.3 release which will not automatically create .malai.id52
file (or any other file). The user has to create a config file.

We create malai identity {create, import, export, rename, delete} cmds to
interact with the system keyring.

A malai run ./my_service.toml command which takes the following config schema:

[malai]
log = "/var/log/malai.log" # (full tracing output)

# my_service.toml
[http.swyn]
identity = "<id52>" # | "path to file" | "$ENV" (`malai identity` is required)
port = 3000 # exposes port 3000 on your server
pubilc = true # required for now (equivalent of `--public` in `malai http`)
active = true # set this to false and malia will ignore this
access-log = "/var/log/swyn.log" # (stdout)
debug-log = "/var/log/swyn.log" # (full tracing output)
error-log = "/var/log/swyn.error.log" # (stderr)

# [tcp.<service-name>]
# [folder.<service-name>]
# ... other services

Existing subcmds will continue to exist except that it'll simply crash if the
identity is not found. It will not create identities (malai.id52 file) for you unless explicitly
asked.

[overflowz]

is config file required or optional? can't I do something like MALAI_IDENTITY=xxx MALAI_SECRET=yyy malai http 3000 --public?

[amitu]

It is optional. MALAI_SECRET=yyy malai http 3000 --public will work. You do not need to pass both (ID52 can be derived from SECRET). If you have had used malai identity sub-command to store the secret key for an identity in your keyring, then you can also use MALAI_ID52=yyy malai http 3000 --public.

The config file is when you want to expose multiple services in one command or want to setup systemd etc.

[amitu]

Default malai conf

malai run will use .malai/services.toml as the default file name if its not passed.

Why not .malai.toml?

For future readiness point of view we should have a .malai so in future we can add other files etc there if needed.

[overflowz]

what's the point of hidden folder? I'd say it's fine if it lays in /home, but inside current directory, hidden folder is kinda off. If I want to have config files, it's better to have them visible, no?

[amitu]

So like /etc/malai/? Do we have a convention for such files in Mac/Windows/Linux. In linux I am used to dot files / dot folders. If we do ~/.ssh, why not ~/.malai?

[overflowz]

~/.malai would be better IMO, but is it really necessary though? If I want to have files where services are defined, isn't it better to explicitly tell which config files should it read?

[amitu]

Seems there is a confusion.

malai run will use .malai/services.toml as the default file name if its not passed.

I think I was not clear, we are looking at malai run <optional-config-file-default-to-dot-malai-in-home-folder behavior.

[ovo-Tim]

I think if we could manage multiple services (means having multiple ID52 and exposing multiple ports) in a single conf files, it would be neater. Additionally, if we could support running multiple conf files in a single command, it would be much more convenient, especially when dealing with a large number of services.