[Bug]: `$DEVSY_HOME` / `--home` having no effect?

[DavidToneian]

Before submitting

• I have searched existing issues to confirm this is not a duplicate
• I am running the latest version of Devsy

What happened?

Say /tmp is empty. When I run devsy --home /tmp/.devsy provider add docker or DEVSY_HOME=/tmp/.devsy devsy provider add docker, I expect /tmp/.devsy to be created and ~/.devsy to be ignored.

Likewise, if I run devsy workspace up my_new_workspace, I expect /tmp/.devsy to be created and to host the workspace information.

What did you expect to happen instead?

Instead, /tmp/.devsy is not created, and devsy complains about the docker provider existing already (in ~/.devsy).

In the second case, the new workspace does get created, but again in ~/.devsy, as opposed to /tmp/.devsy.

Steps to reproduce

ls /tmp/.devsy # Expect this to fail, as the directory does not exist
devsy --home /tmp/.devsy provider add docker # Expect this to succeed, regardless of state of ~/.devsy
ls /tmp/.devsy # Expect this to exist now, and contain the provider configuration

devcontainer.json

Error output / logs

How often does this happen?

Every time

Operating system

Linux

Linux distribution (if applicable)

No response

Architecture

AMD64

Desktop app or CLI?

CLI only

Devsy version

v1.5.1

Devsy provider

Docker

Provider version

No response

Screenshots

No response

Anything else?

No response