I utilisey own Planning tool to build a development schedule and ensure that testing is thoroughly completed and acceptance obtained before an epic is signed off. This ensure that at each stage the current build items work, and, the existing build items still work as intended. I also retain a list of common coding errors and utilise that for AI context.

This could be a daft question, but here goes; Is it possible I can change my reverse proxy to renew certs every 45 days? or is the renewal allowance date driven by let's encrypt? I could update my reverse proxy with this option ahead of the changes.

@Ivo Dell I have certificate management built into the reverse proxy I developed.

Based on previous requests it has a knowledge centre, it uses that to draft future workflows that a human can then approve and enable, or reject. The aim is to always have the guardrails in place, but, allow self development of the deterministic agents by learning. You can also see them working in the workflow and allocating to another agent in the team where the task is out of its remit. My next development will be to create peer agents that can check off the detail proposed and with some further guardrails in place auto create and approve lower risk tasks. the aim of all of this is for the agent to manage my eco-system whilst ensuring that instances arent over or under provisioned. The app will run agentless or you can deploy an agent. With regards to proxmox, you can enable a proxmox api with the app and it will in turn monitor/manage subordinates within the HV.

@Brandon Lee

In my earlier Lab days I used to, not anymore.