Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,14 @@ and the project adheres to CalVer (`YYYY.MM.PATCH`).

## [Unreleased]

### Fixed
- **Quick Start health check.** Step 4 told you to run `./scripts/healthcheck-web.sh`
on the host, where it fails: the file is not executable and calls `forail-manage`,
which exists only inside the backend image. Those scripts are the *container*
probes Compose mounts at `/etc/forail/`. The README now points at
`docker compose ps` and, for a manual run,
`docker compose exec forail-web bash /etc/forail/healthcheck-web.sh`.

### Added
- AWX → Forail migration importer (`forail-manage import_from_awx`) — see the
backend changelog and `forail-deploy/docs/RELEASE_NOTES_v2026.07.0.md`.
Expand Down
10 changes: 9 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,15 @@ cp .env.example .env
docker compose up -d

# 4. Check health
./scripts/healthcheck-web.sh
docker compose ps # every service should report (healthy)
```

The scripts under `scripts/` are the container health probes — Compose mounts
them into the containers and runs them there (`bash /etc/forail/healthcheck-web.sh`),
so they call `forail-manage` and only work inside the image. Run one by hand with:

```bash
docker compose exec forail-web bash /etc/forail/healthcheck-web.sh && echo healthy
```

## Architecture
Expand Down
Loading