:gear: Setting or hook to customize the project / home path

[jefftriplett]

Nice work on the project btw.

I wanted to try out dsd-vps on a few projects on my DO or Hetzner stack but I noticed the plugin was defaulting to files living in /home/{server_username} and even /home/{dsd_config.server_username}/{dsd_config.local_project_name}

Can the root / home path be more customizable so that we can integrate with existing projects more easily? I use and have clients that end up /srv or /opt and it'd be nice to be able to support that.

If that's out of scope and dsd-vps is only intended to deploy one project per server then that's fine/reasonable. Otherwise, making the default path be configurable would make it easier to integrate with existing projects.

• https://github.com/django-simple-deploy/dsd-vps/blob/main/dsd_vps/platform_deployer.py#L146
• https://github.com/django-simple-deploy/dsd-vps/blob/main/dsd_vps/platform_deployer.py#L209

[ehmatthes]

Yes, absolutely. I think I'll add a CLI arg, and a config file as well. I really like CLI args for small sets of options, but this plugin is almost certainly going to have more options than makes sense for CLI args only.

Any quick thoughts on that approach? Also, any strong preferences for a config file format? I've never had complex enough use cases to have a strong preference over ie TOML vs YAML.

[jefftriplett]

Any quick thoughts on that approach? Also, any strong preferences for a config file format? I've never had complex enough use cases to have a strong preference over ie TOML vs YAML.

Do you have access to Django settings while running the plugins? If so, that feels low friction. I'd probably go Django setting, cli override, and then a pyproject.toml value (toml) vs. inventing a new config format or standard.

[ehmatthes]

Thanks, it never occurred to me to just use a Django setting.