Proxmox lxc/vm auto configuration. #78

New Issue

adam · 2025-12-29T14:24:22+01:00

adam commented

2025-12-29 14:24:22 +01:00

Originally created by @DmitriiMukhin on GitHub (May 20, 2025).

Hi.
Do you have any plans to implement for proxmox similar to docker containers configuration? Like in Traefik proxmox provider

Originally created by @DmitriiMukhin on GitHub (May 20, 2025). Hi. Do you have any plans to implement for proxmox similar to docker containers configuration? Like in [Traefik proxmox provider](https://github.com/NX211/traefik-proxmox-provider)

adam commented

2025-12-29 14:24:23 +01:00

@yusing commented on GitHub (May 20, 2025):

I did, when I implemented idle sleep function for LXCs. But I didn't find a place to store route config in Proxmox. "Notes" is definitely not a good place to store it.

@yusing commented on GitHub (May 20, 2025): I did, when I implemented idle sleep function for LXCs. But I didn't find a place to store route config in Proxmox. "Notes" is definitely not a good place to store it.

adam commented

2025-12-29 14:24:23 +01:00

@DarinDev1000 commented on GitHub (Jun 10, 2025):

I would be interested in this, and I might be interested in helping make it too

@DarinDev1000 commented on GitHub (Jun 10, 2025): I would be interested in this, and I might be interested in helping make it too

adam commented

2025-12-29 14:24:23 +01:00

@dacagi commented on GitHub (Jul 15, 2025):

I was too thinking about this. It would be a great feature, at least for LXCs since they tend to start and stop very quickly, not so sure about full VMs. In my case at least, I have one service per LXC, but I have some VMs running multiple services (via Docker and Coolify). And for that I wouldn't shut down the whole VM but stop the underlying Docker container. I mean that the VM sleep function is far more complicated not just to implement, but it also depends on the use case.

Regarding LXCs only then, I too find it a bit 'dirty' to use the notes=description field of the .conf files. But it's either that, or the tags field which I like even less. Otherwise we would require storing those config details in a local file on the godoxy side.

Maybe have an array property in the existing yaml where we would list the LXC ids that we want to enable sleep for?

Since we will be already accessing the Proxmox API to obtain all LXC details, that should allow us to even show the list of LXC ids+hostnames and toggle via UI config editor too.

config.yml sample

config ui options, either comma separated or with individual checkboxes

I only listed ids here for brevity, but it would be useful to display the lxc hostname as well.

@dacagi commented on GitHub (Jul 15, 2025): I was too thinking about this. It would be a great feature, at least for LXCs since they tend to start and stop very quickly, not so sure about full VMs. In my case at least, I have one service per LXC, but I have some VMs running multiple services (via Docker and Coolify). And for that I wouldn't shut down the whole VM but stop the underlying Docker container. I mean that the VM sleep function is far more complicated not just to implement, but it also depends on the use case. Regarding LXCs only then, I too find it a bit 'dirty' to use the notes=description field of the .conf files. But it's either that, or the tags field which I like even less. Otherwise we would require storing those config details in a local file on the godoxy side. **Maybe have an array property in the existing yaml where we would list the LXC ids that we want to enable sleep for?** Since we will be already accessing the Proxmox API to obtain all LXC details, that should allow us to even show the list of LXC ids+hostnames and toggle via UI config editor too. ### config.yml sample <img width="502" height="110" alt="Image" src="https://github.com/user-attachments/assets/819168b6-ab1d-416e-ab94-8aeb13ec9958" /> ### config ui options, either comma separated or with individual checkboxes <img width="896" height="676" alt="Image" src="https://github.com/user-attachments/assets/98a3f22b-bd21-4dc8-9814-a3e890f0c701" /> I only listed ids here for brevity, but it would be useful to display the lxc hostname as well.

adam referenced this issue

2025-12-29 14:25:46 +01:00

[PR #78] [CLOSED] Feat/godoxy agent #159

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/godoxy-yusing#78