Can path modifications and config JSON support tilda or $HOME

[Integralist]

I've recently moved laptops where my laptop name has changed.

This appears to be an issue with regards to .config/humanlog/config.json:

"log_dir": "/Users/integralist/.state/humanlog/logs",

I pulled this config from my dotfiles repo and just happened to notice that the path was wrong now my computer name is different.

Is ~ supported in the JSON path? For example:

"log_dir": "~/.state/humanlog/logs",

But also I noticed this affects the modifications made by humanlog to the user's shell configuration:

export PATH=/Users/mmcdonnell/.humanlog/bin:$PATH

The problem with the above is that it makes it hard for me to commit this change into my dotfiles repo because in the future my laptop name could change again and I don't want to have to keep remembering to check various configuration files for hard-coded path references.

It would be nice if the export PATH could just use $HOME so that I could commit the change:

export PATH=$HOME/.humanlog/bin:$PATH

Thanks.

[KevRiver]

Thanks for the report. I'll look into it.

[KevRiver]

@Integralist I've changed default config to use ~ instead of user home-directory path

"serve_localhost": {
            "port": 32764,
            "engine": "advanced",
            "engine_config": {
               "path": "~/.state/humanlog/data/db.humanlog"
            },
            "show_in_systray": true,
            "log_dir": "~/.state/humanlog/logs",
            "otlp": {
               "grpc_port": 4317,
               "http_port": 4318
            }
         },

So config.json will look like the above when the changes are applied

I've also started working on fixing install script to use $HOME.