To update the metadata in the distro/configuration folder (e.g., adding new forms, concepts, etc.), follow these steps:
Step 1: Stop the Running Instance
If your instance is currently running, first bring it down:
docker compose down
This command stops and removes the current containers, ensuring a clean start for your updated metadata.
Step 2: Build the Local Docker Image
To reflect the updated metadata in your instance, you'll need to build a local Docker image. Ensure your configuration files follow the accepted conventions for each configuration, as incorrect formats might prevent the metadata from appearing in the instance as expected.
TAG=your-custom-tag docker compose build
Replace `your-custom-tag` with any unique tag of your choice. It’s advisable to use a tag not found on Docker Hub (e.g., `qa` or specific release versions) to avoid conflicts.
Step 3: Run the Instance with the Updated Image
Next, start your instance using the locally built image:
TAG=your-custom-tag docker compose -f docker-compose.yml up -d
Ensure that the `TAG` variable matches the one you used in the previous step. This command launches the instance using your locally built image instead of pulling one from Docker Hub.
Step 4: Wait for the Instance to Start
The backend script should start running at this point. To verify if the instance is running, refer to the step 4 of the dev guide of setting up an instance of O3.