Files
TSYSDevStack/CloudronStack
ReachableCEO 91d52d2de5 feat(cloudron): add tirreno package artifacts
- Add CloudronStack/output/CloudronPackages-Artifacts/tirreno/ directory and its contents
- Includes package manifest, Dockerfile, source code, documentation, and build artifacts
- Add tirreno-1761840148.tar.gz as a build artifact
- Add tirreno-cloudron-package-1761841304.tar.gz as the Cloudron package
- Include all necessary files for the tirreno Cloudron package

This adds the complete tirreno Cloudron package artifacts to the repository.
2025-10-30 11:43:06 -05:00
..

🛰️ CloudronStack

CloudronStack contains Cloudron packaging artifacts for various upstream projects focused on different business capabilities. This stack serves as a catalog of third-party services grouped by capability for easy deployment and management.


📚 Service Categories

This repository contains all of the Cloudron packaging artifacts for the following upstream projects:

Monitoring & Observability

Security & Compliance

Developer Platforms & Automation

Infrastructure & Operations

Data & Analytics

Business & Productivity

Industry & Specialized Solutions


🚀 Quick Start

To use these Cloudron packages:

  1. Navigate to the CloudronStack directory:

    cd CloudronStack
    
  2. Review the collab/ directory for planning documents and collaboration notes:

    ls -la collab/
    

🧭 Working Agreement

  • Stacks stay in sync. When you add or modify automation, update both the relevant stack README and any linked prompts/docs.
  • Collab vs Output. Use collab/ for planning and prompts, keep runnable artifacts under output/.
  • Document forward. New workflows should land alongside tests and a short entry in the appropriate README table.
  • AI Agent Coordination. Use Qwen agents for documentation updates, code changes, and maintaining consistency across stacks.

🤖 AI Agent

This stack is maintained by CloudronBot, an AI agent focused on CloudronStack documentation and packaging.


📄 License

See LICENSE for full terms. Contributions are welcome—open a discussion in the relevant stack's collab/ area to kick things off.