ReachableCEO
77e10af05c
- Add new PROMPT file in collab directory for AI collaboration guidance - Add STATUS.md file in collab directory to track current status - Create output directory for project artifacts - Remove redundant commit-template.txt that is now centralized at top level - Update collab directory structure and content for better organization These changes improve the CloudronStack component's structure and documentation for better collaboration.
33 lines
1.2 KiB
Plaintext
33 lines
1.2 KiB
Plaintext
Create Cloudron packages for all upstream applications found in:
|
|
|
|
collab/GitUrlList.txt for Cloudron.
|
|
|
|
Create shell scripts todo the packaging work and run three packaging projects in parallel.
|
|
|
|
Create a master control script to orchestrate the individual packaging scripts.
|
|
|
|
Create and maintain a status tracker in collab/STATUS.md
|
|
|
|
Take on these roles/perspectives for this chat:
|
|
|
|
- Prompt engineering expert
|
|
- Cloudron packaging expert
|
|
- Dockerfile expert
|
|
|
|
Do all of your work in the output/ directory tree.
|
|
|
|
It contains two subdirectories:
|
|
|
|
CloudronPackages-Artifacts for storing the actual Cloudron package artifacts
|
|
CloudronPackages-Workspaces for cloning git repo, storing logs and whatever else is needed during packaging work
|
|
|
|
The docker images must build as part of package smoke testing.
|
|
|
|
Use this prefix for all docker images created by this process:
|
|
|
|
tsysdevstack-cloudron-buildtest-
|
|
|
|
If a packaging script has a problem and you cant solve the problem after five tries, flag it in STATUS-HumanHelp-<application> and move on
|
|
|
|
This is a big project. I expect it to run fully autonomously over the next four days or so. Be careful. Be Brutal. audit your work as you go.
|
|
be methodical. start from first principles and develop a robust system and think/code defensively. |