3.9 KiB
Good afternoon.
I need you to be an EXPERT LEVEL SENIOR ENGINEER in devops/sre/CLoudron/Docker. DO not be a junior. Do not make mistakes that you can avoid. I prefer you to go slower and make less mistakes because you think about things ok?
You are hereby tasked to package up the 56 applications in this repository for Cloudron in the next 48 hours. These are absolutely production mission critical for me to make money from my ventures. These close out my private cloud gaps. We must get these done or I will lose my house.
You are my authorized agent to handle this packaging work for me as accurately and quickly as possible.
Start with doing a very deep orientation to the CloudronPackages directory tree.
In the Workspace directory, please create a detailed plan file/status tracker/memory bank called TheSoverignCloud.md.
This is the ONLY markdown file you may use for this entire weekend. It should have todo, lessons learned, best practices etc. Ask any questions you like , don't be shy.
Put a Questions: YYYY-MM-DD HH:MM (use my local system time ok?) header and then list out your detailed questions and group them by sub section, I will edit inline and let you know in chat. Once you have read my questions, ask any followups in another date/time stamped section. We MUST communicate exclusively via markdown files.
The only thing chat should be used for (in terms of our talking) is to let each other know when a markdown file is ready for review.
Lets go slow, think carefully.
I want you to be absolutely BRUTAL in your work, your self assessment / audit as you go, your planning, your review, your compliance with instructions / plan that you create ok?
Do your best woirk. Think defenisvely. Slow down. Start from first principles. Use web search to pull the latest CLoudron packaging information. In general be accurate first, validate and then be fast ok>
Be your own QA tester please. Bring up the containers/stack locally and smoke test.
Do not tell me something is actually done when its not done. You must provide proof of completion for anything you say is complete. By proof, I mean logs, curl etc output. Hard proof.
For any containers / images / networks / volumes etc docker artifacts you create on this machine for testing purpose, use KNELCloudronDev- prefix please. Then use the package name as a secondary part of the prefix.
Also create and actively maintain AGENTS.md please.
DO not deviate from the instructions in this file or the plan we create ok?
Also, under no circumstances should anything be done directly on the host with the exception of
git commands (also can use the tea command to interact with my gitea instance) docker commands awk/sed/grep/cat etc bash commands
Any packaging work MUST be done in containers.
Create a helper container with the cloudron bits. It should be based on Ubuntu 22.04 (or whatever version Cloudron is using as its base)
My Cloudron instance is at https://my.knownelement.com My cloudron builder service is at: https://cloudron-app-build.knownelement.com/ My Cloudron registry service is at: https://cloudron-docker-registry.knownelement.com/
Please create a secret.txt file and .gitignore it . I will place CLoudron tokens in that file.
Generally the best results I've gotten from agentic AI is by using a directory called collab :
collab/ audit questions proposals plans prompts
output/
The collab directory is where we talk The output directory is where you work
Make sense?
Follow a wqrkflow of
questions -> proposals -> plans -> prompts -> implementation
Ask me any questions about the workflow if it isn't clear.
We will package exactly ONE application at a time.
Start with core technical infrastructure, then core business infrastrcutre, than other stuff. Keep TheSoverignCloud.md up to date at all times.
Start with a plan, do not perform any implementation yet. I must be in the loop at all times and approve all actions, either single item or multiple items in a batch.