• docker-compose

• Start the development environment: docker-compose up -d
• Stop dev environment: docker-compose down
• If you want to clean up all the stored data use -v: docker-compose down -v

Website will be available at http://localhost:3001.

After you signup, you can approve your user and make him admin with:

./dc.sh exec db psql -U unep -d gpml -c "UPDATE stakeholder SET review_status='APPROVED', role='ADMIN' WHERE email='<your email here>'"

Backend API is available at http://localhost:3000

You can connect to the REPL using your IDE tools or using the backend container

docker compose exec backend lein repl :connect localhost:47480

Run the following command in the REPL

(make-user! "<user email here>")

Run the following command in the terminal shell

docker compose exec db psql -U unep -d gpml -c "UPDATE stakeholder SET review_status='APPROVED', role='ADMIN' WHERE email='<your email here>'"
docker compose exec db psql -U unep -d gpml -c "INSERT INTO rbac_super_admin(user_id) SELECT id FROM stakeholder WHERE email='<user email here>'"

To "injects" the new bytecode into the running JVM, run the following command in the REPL

(refresh)
(go)

Copy the backend/dev/resources/local.example.edn file to backend/dev/resources/local.edn.

Logs are helpful when debugging errors. Edit backend/dev/resources/local.edn and add the following lines

{
  ;; ...

  ;; print log to stdout
  :duct.logger.timbre/println   {}
  :duct.logger/timbre           {:set-root-config?  true
                                 :level             :info
                                 :appenders         {:println #ig/ref :duct.logger.timbre/println}}
  ;; ...
}

Edit backend/dev/resources/local.edn and add the following lines

{
  ;; ...

  [:duct/const :gpml.config/common] {:storage-client-adapter #ig/ref :mocks.boundary.adapter.storage-client/local-file-system
                                     :storage-bucket-name #duct/env ["LOCAL_FS_STORAGE_BUCKET_NAME" Str]}
  ;; ...
}

Edit backend/dev/resources/local.edn and add the following lines

{
  ;; ...

  :mocks.boundary.adapter.chat/ds-chat  {}
  [:duct/const :gpml.config/common]     {:chat-adapter  #ig/ref :mocks.boundary.adapter.chat/ds-chat}

  ;; ...
}

The project uses GitHub Actions for continuous integration and deployment:

Runs on:

• All pull requests
• Pushes to main branch

The workflow consists of three jobs:

1. Backend QA - Runs in parallel

   • Migration validation
   • clj-kondo linting
   • Eastwood linting
   • Unit tests (eftest)
   • Uberjar build verification
   • Caches Maven dependencies (~/.m2) and Lein dependencies (~/.lein)

2. Frontend QA - Runs in parallel

   • Node modules installation
   • ESLint linting
   • Next.js build
   • Caches node_modules

3. Integration Tests - Runs after both QA jobs complete

   • Builds all Docker images
   • Runs end-to-end API tests
   • Tests authentication flows
   • Validates HTTP endpoints

Automatically deploys to test cluster after QA passes on main branch:

• Triggers after "Quality Assurance" workflow completes successfully
• Builds Docker images (nginx, frontend, backend, strapi)
• Pushes images to container registry
• Performs Kubernetes rollout to test environment

The project is in the process of migrating from Semaphore CI to GitHub Actions. Currently both systems are running:

• Semaphore CI: Legacy build system (to be deprecated)
• GitHub Actions: New QA and deployment workflows

Once GitHub Actions is fully validated, Semaphore CI will be deprecated and the ci/ folder will be removed.