|
1 | 1 | # XLSForm Builder Helm Chart |
2 | 2 |
|
3 | 3 | This Helm chart deploys the XLSForm Builder application, |
4 | | -consisting of a backend API service and a frontend web application. |
| 4 | +consisting of a backend API service, a frontend web application, and |
| 5 | +a pyxform-http service for XLSForm to XForm conversion. |
5 | 6 |
|
6 | 7 | ## Prerequisites |
7 | 8 |
|
@@ -85,11 +86,18 @@ Key configuration values: |
85 | 86 | - `ingress.backend.hostname`: Backend API hostname (default: `api.xlsforms.field.hotosm.org`) |
86 | 87 | - `image.backend.tag`: Backend image tag |
87 | 88 | - `image.frontend.tag`: Frontend image tag |
| 89 | +- `image.pyxform.tag`: Pyxform-http image tag (default: `latest`) |
88 | 90 | - `frontend.env.apiUrl`: Backend API URL for frontend to use (default: `https://api.xlsforms.field.hotosm.org`) |
89 | 91 | - `frontend.env.metadataUrl`: S3 metadata.json URL (default: `https://xlsforms.s3.amazonaws.com/metadata.json`) |
| 92 | +- `pyxform.healthCheck.enabled`: Enable health checks for pyxform service (default: `false`) |
| 93 | +- `pyxform.healthCheck.path`: Health check path (default: `/`) |
90 | 94 |
|
91 | 95 | **Note:** The frontend uses runtime configuration injected via environment variables. |
92 | 96 | These are used to generate a `config.js` file at container startup, allowing the |
93 | 97 | frontend to work with different API URLs without rebuilding the image. |
94 | 98 |
|
| 99 | +**Note:** The backend automatically connects to the pyxform service via the |
| 100 | +`PYXFORM_URL` environment variable, which is set to the pyxform service URL |
| 101 | +based on the Helm release name. |
| 102 | + |
95 | 103 | See `values.yaml` for all available options. |
0 commit comments