1.6 KiB
1.6 KiB
AI Agent Maintenance Instructions
When maintaining this repository, you MUST adhere to the following rules based on the REQUIREMENTS.md.
Guidelines for Adding/Modifying Services
-
Volume Mapping:
- ALWAYS map system data to
/volume1/docker/<service>. - ALWAYS map large user data to
/volume1/media/<type>. - Use environment variables (e.g.,
${DOCKER_BASE:-/volume1/docker}) if possible for flexibility.
- ALWAYS map system data to
-
Setup Scripts:
- If a setup script does not exist, CREATE one named
create_<service>_folders.shin the service directory. - Use the following template for scripts:
#!/bin/bash BASE="/volume1/docker/service_name" MEDIA="/volume1/media/service_data" mkdir -p "$BASE/config" "$BASE/data" "$MEDIA" chown -R PUID:PGID "$BASE" "$MEDIA" chmod -R 750 "$BASE" "$MEDIA" - Ensure the script is idempotent (safe to run multiple times).
- If a setup script does not exist, CREATE one named
-
Setup Documentation (SETUP.md):
- Create a
SETUP.mdfile in the service directory based onSERVICE_SETUP_TEMPLATE.md. - Explicitly highlight MANUAL steps like Synology user creation and PUID/PGID lookup.
- Describe what the setup script does and what environment variables are needed.
- Create a
-
Docker Compose (Portainer Stacks):
- Name the file
docker-compose.portainer.yml. - Group dependent containers (DB, Cache) in the same file.
- Use
user: "${PUID}:${PGID}"unless root is required. - Prefer
env_file: stack.envfor environment variable management.
- Name the file
-
Code Quality:
- Check for typos in filenames and configurations.
- Ensure consistent naming conventions across all service directories.