Wildfire Predictive Services to support decision making in prevention, preparedness, response and recovery.
Note: Docker Compose and the VS Code dev container are currently unsupported. Native setup is the recommended (and supported) way to run the project locally.
Run the backend and front end natively — see the per-component setup docs:
- Backend: backend/README.md (uv, GDAL, Postgres/PostGIS, Redis). On macOS,
setup/mac.shinstalls the system dependencies. - Frontend: web/README.md (Node/yarn).
Native setup is the recommended and supported path. The Docker Compose and dev container flows further down are currently unsupported and may be out of date.
Refer to backend/packages/wps-api/README.md (setup in backend/README.md; on macOS, setup/mac.sh installs the dependencies).
Refer to web/README.md
- Create
web/.envusingweb/apps/wps-web/.env.exampleas a sample. - Create
backend/packages/wps-api/src/app/.env.dockerusing the repo-root.env.exampleas a sample. - Run
docker compose buildand thendocker compose up - Open http://localhost:8080 to view the front end served up from a static folder by the python api.
- Open http://localhost:3000 to view the front end served up in developer mode by node.
- Open the project and run
Dev Containers: Reopen in Container— VS Code picks up.devcontainer/devcontainer.json. - Sometimes VSCode doesn't pick up you've changed the docker container:
Dev Containers: Rebuild Container - Install extensions into the container, as needed.
- You can point the API database to:
host.docker.internal - You can start up other services outside of vscode, e.g.:
docker compose up dbanddocker compose up redis
Apache 2.0 License - see the LICENSE.md
Your Github PR is required to pass all our CI checks, including our test coverage threshold via CodeCov: https://docs.codecov.com/docs/about-code-coverage
- Issues
- PEP8 and PEP20 coding conventions, but with 110 character line breaks
- Code of Conduct