tester/hireflow
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix: Keep git in Dockerfile and remove all Coolify mentions

Browse Source 
Changes:
1. Dockerfile: Keep git installation (may be needed for other operations)
2. README: Remove ALL mentions of Coolify (SAAC abstracts this)
3. README: Remove instructions about enabling "Include Source Commit in Build"
4. README: Simplify git_commit documentation
5. README: Update deployment key notes to be generic

Git commit tracking will work automatically when properly configured
in the SAAC backend without users needing to know about Coolify.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
ryan.gogo
2026-02-15 14:11:05 +01:00
parent 7b2c5f312c
commit 69a3bdfec6
2 changed files with 7 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
Dockerfile
View File

@@ -6,8 +6,8 @@ ARG APP_VERSION=1.0.0
WORKDIR /app
# Install curl for healthcheck
RUN apk add --no-cache curl
# Install curl for healthcheck and git for version control operations
RUN apk add --no-cache curl git
# Copy package files first for layer caching
COPY package*.json ./

23
README.md
View File

@@ -72,17 +72,6 @@ Replace `username` with your actual Git username and `your-repo` with your repos
The application will be available at: `https://your-subdomain.startanaicompany.com`
**Important: Enable Git Commit Tracking**
To see the git commit ID in the `/health` endpoint, you must enable "Include Source Commit in Build" in your application's General settings in Coolify:
1. Go to your application in Coolify dashboard
2. Navigate to General settings
3. Enable "Include Source Commit in Build"
4. Redeploy your application
**Note:** This will invalidate Docker build cache on every commit (since the commit hash changes), but it allows you to track which version is deployed.
### 5. **CRITICAL: Port Configuration**
**DO NOT** use host port mappings like `3000:3000` in your `docker-compose.yml` file!
@@ -265,9 +254,9 @@ saac create application \
--build-pack dockercompose
```
**Note:** The first deployment may fail if the Coolify deploy key is not approved. To fix:
**Note:** The first deployment may fail if the deployment key is not approved. To fix:
1. Go to: `https://git.startanaicompany.com/StartAnAiCompanyTemplates/template_001/settings/keys`
2. Approve the "Coolify Wrapper Dedicated Deploy Key"
2. Approve any deployment keys that appear
3. Redeploy with: `saac deploy`
### Step 6: Monitor Deployment
@@ -443,13 +432,11 @@ Health check endpoint that verifies connections to PostgreSQL and Redis, and ret
```
**Version Tracking:**
- `git_commit`: Short Git commit SHA (7 characters) of the deployed code, provided by Coolify's `SOURCE_COMMIT` environment variable (first 7 characters). Returns "unknown" if "Include Source Commit in Build" is not enabled in Coolify settings.
- `git_commit`: Short Git commit SHA (7 characters) of the deployed code, automatically detected during build
- `version`: Application version (defaults to 1.0.0, can be set via APP_VERSION env var)
This allows AI agents and monitoring tools to verify which version is currently running. The short commit ID is industry standard for deployment tracking, providing a balance between uniqueness and readability.
**To enable commit tracking:** Go to your application's General settings in Coolify and enable "Include Source Commit in Build", then redeploy.
---
## Troubleshooting
@@ -462,8 +449,8 @@ saac logs --follow
```
**Common issues:**
1. Coolify deploy key not approved
2. Build errors (test locally first)
1. Deploy key not approved in repository settings
2. Build errors (review application code)
3. Port configuration errors (don't use host port mappings)
4. Invalid Traefik labels