First of all, thank you so much for this amazing project. Until now, I’ve been using Portainer in my home lab, with all its limitations, and Dockhand fills in a lot of those gaps and offers so much more on top of that. Since I'm currently setting up my home lab from scratch, I'd like to make extensive use of Dockhand. I especially like the Git sync feature and the deployment of a stack from a Git-Repository.
I have a question about Git Sync based on the following structure in a repository.
stack_1/
├─ docker-compose.yaml
├─ .env
├─ additional_files/
│ ├─ additional_config_1.conf
│ ├─ additional_config_2.conf
If I deploy stack_1 on the host where Dockhand is running, the entire stack - including additional_files and its contents - is synchronized, so that I can access additional_config_1.conf and additional_config_2.conf in the compos- file via volume.
If I deploy stack_1 to a remote server, the files from additional_files are not transferred to the remote host, so the stack cannot be started if additional_config_1.conf and additional_config_2.conf are mounted via volume in the compose-file.
Although this behavior is documented in the docs, I would still like to ask whether it is technically possible - or if there are any plans - to extend the Hawser client so that files are also transferred into the stack-directory on the remote server.
Best regards,
Oliver
First of all, thank you so much for this amazing project. Until now, I’ve been using Portainer in my home lab, with all its limitations, and Dockhand fills in a lot of those gaps and offers so much more on top of that. Since I'm currently setting up my home lab from scratch, I'd like to make extensive use of Dockhand. I especially like the Git sync feature and the deployment of a stack from a Git-Repository.
I have a question about Git Sync based on the following structure in a repository.
If I deploy
stack_1on the host where Dockhand is running, the entire stack - includingadditional_filesand its contents - is synchronized, so that I can accessadditional_config_1.confandadditional_config_2.confin the compos- file viavolume.If I deploy
stack_1to a remote server, the files fromadditional_filesare not transferred to the remote host, so the stack cannot be started ifadditional_config_1.confandadditional_config_2.confare mounted viavolumein the compose-file.Although this behavior is documented in the docs, I would still like to ask whether it is technically possible - or if there are any plans - to extend the Hawser client so that files are also transferred into the stack-directory on the remote server.
Best regards,
Oliver