owl-agent-test-harness
Aries agent test framework, with agent backchannel support
- 72
- Python
- Apache-2.0
- 3 mo ago
For use in Service BC service centres for customer flow management and analytics.
Repo bcgov/queue-management, read from GitHub 5 h ago. bcgov has not joined Take My Repo.
bcgov/queue-management is a public repo on GitHub by bcgov. For use in Service BC service centres for customer flow management and analytics. It declares the Apache-2.0 license on GitHub. It is written mainly in Python, has 49 stars and last changed on 2026-11-18. Nobody has reviewed it on Take My Repo yet, which says nothing about its quality. Read from GitHub on 2026-11-22.
In the maintainer's words. Shown from GitHub; Take My Repo does not keep a copy.
The Q is the Service BC platform for managing in-person office flow, appointments, smartboard and digital signage displays, outbound notifications, and related service delivery workflows. The application is used by Service BC as well as other B.C. government ministries.
Service BC connects people with services offered by the B.C. provincial government. This application supports the day-to-day operations of Service BC locations by helping staff manage queues, appointments, exams, walk-ins, and communications across the province.
apiThe primary backend service for the platform. It serves the main REST API under /api/v1 plus Socket.IO endpoints used by the staff and public frontends.
Key responsibilities include:
frontendThe internal staff-facing Vue 2 application. Staff use it for queue management, office administration, appointments, exams, uploads, smartboard support, and optional service-flow integrations.
appointment-frontendThe public-facing Vue 2 application for booking appointments, viewing booked appointments, managing account settings, handling sign-in flows, and viewing walk-in queue status.
appointment-bookingThe new under development public-facing React 19 + TypeScript application for booking appointments at Service BC locations. It will eventually replace appointment-frontend. See appointment-booking/README.md for setup instructions.
notifications-apiA separate Flask service for outbound notifications. It exposes authenticated POST /api/v1/notifications/sms and POST /api/v1/notifications/email endpoints and supports pluggable delivery providers, including GC Notify, CHES, and logging/custom implementations.
feedback-api[!WARNING]
feedback-apiis deprecated, retained only for legacy compatibility, and will be removed in a future version.
This legacy Flask service accepts feedback submissions and forwards them to the older Camunda-based feedback flow.
Older references to RabbitMQ remain in the repository, but they are not part of the current development guidance in this README.
This repository supports two local development workflows:
compose.yaml definition and finish running the post-create scriptThe devcontainer now prepares local config files before API migrations/bootstrap and waits for PostgreSQL and Keycloak readiness before the post-create flow continues.
It also provisions project-local Python environments for both api and notifications-api, so the checked-in VS Code debug configurations work without extra manual setup.
5000: queue management API5002: notifications API5173: appointment booking frontend (React)8080: staff frontend8081: appointment frontend8085: Keycloak auth server5432: PostgreSQLThe devcontainer installs dependencies automatically for api, notifications-api, frontend, and appointment-frontend, applies database migrations, and may initialize seed data depending on the current database state.
uvnpmInstall backend dependencies:
cd ./api
uv sync --group dev
cd ./notifications-api
uv sync --group dev
Install frontend dependencies:
cd ./frontend
npm install
cd ./appointment-frontend
npm install
cd ./appointment-booking
npm install
Create the required local config files:
./scripts/setup-local-config.sh
This script copies the checked-in local config defaults from .devcontainer/config, creates missing destination directories, validates required API auth keys, and leaves any existing local files untouched.
Start the local auth server:
docker compose up -d keycloak
Local Keycloak details:
servicebc-localhttp://localhost:8085/authhttp://localhost:8085/auth/admin/admin / passworddemocsr@idir, demoga@idir, admin@idir, citizen@bceidboth, citizen2@bceidbothpasswordtheq-queue-management-apitheq-local-dev-secretMake sure the database settings in api/.env point to your local PostgreSQL instance.
Run database migrations:
cd ./api
uv run python manage.py db upgrade
Start the services in separate terminals.
Queue management API using the local Python environment:
cd ./api
uv run gunicorn wsgi --bind=0.0.0.0:5000 --access-logfile=- --config=gunicorn_config.py --reload --timeout=0
Queue management API using the production Dockerfile through Compose:
docker compose --profile api up --build api
The root compose.yaml is the single source of truth for local Docker services and the devcontainer. The optional api Compose service still serves the application on http://localhost:5000. It reads api/.env, then overrides container-only settings so it can reach the host PostgreSQL and host-run notifications API while continuing to use the local Keycloak on http://localhost:8085/auth.
Notifications API:
cd ./notifications-api
uv run gunicorn wsgi:application --bind=0.0.0.0:5002 --access-logfile=- --config=gunicorn_config.py --reload --timeout=0
Staff frontend:
cd ./frontend
npm run serve
Appointment frontend:
cd ./appointment-frontend
npm run serve -- --port 8081
Appointment booking frontend (React):
cd ./appointment-booking
npm run dev
Opens at http://localhost:5173. See appointment-booking/README.md for Docker and environment variable details.
These are the main local files you should expect to have in place when running the application locally:
api/.envapi/client_secrets/secrets.jsonfrontend/public/static/keycloak/keycloak.jsonfrontend/public/config/configuration.jsonappointment-frontend/.env.localappointment-frontend/public/config/kc/keycloak-public.jsonappointment-frontend/public/config/configuration.jsonThe checked-in local auth defaults now target the local Keycloak realm on http://localhost:8085/auth. If you need to switch back to the shared dev Keycloak server, update the copied local config files before starting the apps.
This repository includes Python/pytest suites, Artillery-based load tests, and Postman/Newman collections. The commands below assume you already completed the local setup for the relevant service and, for API-backed tests, have the local stack running.
The main application test suite lives in api/app/tests and is split into a DB-free smoke slice and a Postgres-backed integration slice.
From api:
./scripts/run_api_smoke_tests.sh
./scripts/run_api_integration_tests.sh
./scripts/run_api_full_tests.sh
Equivalent direct pytest commands:
uv run pytest app/tests -m smoke -q --override-ini "addopts=--strict-markers"
uv run pytest app/tests -m integration -q --override-ini "addopts=--strict-markers" --require-integration-db
uv run pytest app/tests -q --require-integration-db
Additional pytest suites:
cd ./notifications-api
uv sync --group dev
uv run pytest
cd ./feedback-api
make setup
make test
Load testing lives in tests/loadtesting and uses Artillery against the local API stack.
Initial setup:
cd ./tests/loadtesting
npm install
cp envs.example.sh envs.sh
chmod +x envs.sh profile-python.sh
Before running the load tests locally, start the local Keycloak realm and seed the API data:
docker compose up -d keycloak
cd ./api
uv run python manage.py db upgrade
uv run python manage.py bootstrap
Run the load suites from tests/loadtesting:
npm run tests:all
npm run tests:http
npm run tests:socket
Optional Python profiling commands are also available there:
npm run python:profile
npm run python:top
Postman collections live in api/postman. They target the local API and local Keycloak realm, and the checked-in local setup expects the demo users from keycloak-local/servicebc-local-realm.json.
Before running Newman locally, make sure the API database is migrated and bootstrapped:
cd ./api
uv run python manage.py db upgrade
uv run python manage.py bootstrap
Then install Newman and run the main collection from api/postman:
cd ./api/postman
npm install
./node_modules/newman/bin/newman.js run API_Test_TheQ_Booking.json -e postman_env.json --bail failure \
--global-var userid=cfms-postman-operator \
--global-var password=password \
--global-var userid_nonqtxn=cfms-postman-non-operator \
--global-var password_nonqtxn=password \
--global-var client_secret=theq-local-dev-secret \
--global-var url=http://localhost:5000/api/v1/ \
--global-var auth_url=http://localhost:8085 \
--global-var clientid=theq-queue-management-api \
--global-var realm=servicebc-local \
--global-var public_url=http://localhost:5000/api/v1/ \
--global-var public_user_id=cfms-postman-public-user \
--global-var public_user_password=password
See api/postman/README-local-auth.md for local auth troubleshooting details.
For deployment within the B.C. government, this project can be hosted on the B.C. government Private Cloud. The platform is the B.C. Government Private Cloud PaaS, powered by Red Hat OpenShift, and is designed for hosting government applications in a managed private-cloud environment.
This repository still includes deployment artifacts under openshift/templates for platform-specific builds and deployments.
To report bugs/issues/feature requests, please file an issue.
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
This project is licensed under the Apache License, Version 2.0. See the root LICENSE file for the full license text.
bcgov/queue-management is a public repo on GitHub by bcgov. For use in Service BC service centres for customer flow management and analytics.
It declares the Apache-2.0 license on GitHub.
Its maker tagged it for macOS, Windows and Linux, or as Docker or cross-platform. That is declared by the maker; Take My Repo has not tested it.
Open "Take it" on its page: Take My Repo writes an install plan for your machine and hands it to your AI agent (Claude Code, Codex or Cursor), which asks you before each step. Take My Repo has not tested it on any machine.
Its last change on GitHub was on 2026-11-18. GitHub counts 30 open issues and pull requests. Take My Repo does not judge from that whether it is maintained.

Aries agent test framework, with agent backchannel support
Nobody has reviewed it on Take My Repo yet, which says nothing about its quality.
This software stores and makes available tails files for use with Hyperledger Indy
Create, edit and publish forms
Platform services OCP project registry

Wildfire Predictive Services to support decision making in prevention, preparedness, response and recovery
The B.C. Design System helps public sector design and development teams build coherent, accessible products

Traction is designed with an API-first architecture layered on top of OpenWallet Foundation ACA-Py and streamlines the process of sending and receiving digital credentials for governments and organizations.

A simple container for a simple backup strategy.
This page is also available as structured data, with the same sources and dates.
/api/v1/resources/gh/bcgov/queue-managementTake My Repo has not tested this on your machine. Requirements come from the project's own documentation.