BankID Registrator

---

✅ Local Environment

Features:

• 🔄 Live Reload
• 🛠️ PhpMyAdmin for DB inspection

🚀 Setup with Docker

1. Create .docker/local/.env based on .docker/local/.env.example.
2. Prepare your local database (credentials, schema, etc.) as per the .env.
3. Start the containers:

   ./env.sh local up

4. Stop the containers:

   ./env.sh local down

---

🧪 Running Tests in Local Environment

Java / Spring integration tests

1. Make sure src/test/resources/tests.properties exists.
   • If missing, create it by copying from src/test/resources/tests.properties.example.
   • Fill in the required test credentials (e.g., for LDAP).
2. Run the app container:

   docker exec -it bankid-app bash

3. Run all tests inside the container:

   ./mvnw test

Playwright E2E tests

The Playwright suite in e2e/ covers complete registration and membership-renewal journeys, including Bank iD verification, employee registrations, vouchers, Comgate payments, payment failures and retries, and admin-dashboard checks.

1. Make sure the application is running in a configured local or testing environment.
2. Install the E2E dependencies and Chromium:

   cd e2e
   npm install
   npx playwright install chromium

3. Create the E2E environment file and fill in the required application, admin, Bank iD sandbox, patron, and employee-test values:

   cp .env.example .env

4. Run the complete suite from the e2e/ directory:

   npm test

Useful commands:

# Run one specification
npx playwright test tests/registration/normal-no-discount.spec.ts

# Run with a visible browser
npm run test:headed

# Open the latest HTML report
npm run report

Tests run sequentially because customer journeys modify shared Aleph state. Fine-dependent renewal scenarios require patrons with manually prepared fines; their optional environment blocks and bootstrap workflow are documented in e2e/.env.example.

---

🧪 Testing Environment

Features:

• ❌ No Live Reload
• ❌ No PhpMyAdmin
• ⚠️ Database only accessible from within the container

🐳 Deploy with Docker

1. SSH into the testing server:

   ssh username@your-server

2. Navigate to the project directory. If not cloned yet:

   git clone https://github.com/your-username/bankid-registrator.git
   cd bankid-registrator

3. Pull the latest code (do this regularly):

   git pull

4. Create .docker/testing/.env based on .docker/testing/.env.example.
5. Start the containers:

   ./env.sh testing up

6. Stop the containers:

   ./env.sh testing down

---

🗃️ Checking the Database

1. List running containers:

   docker ps

2. Enter the DB container:

   docker exec -it bankid-database bash

3. Access MySQL:

   mysql -u root -p

4. Run your queries:

   SHOW DATABASES;

---

🚀 Production Deployment

⚠️ Ensure that sensitive .env files are securely stored and never committed to the repository.

🔐 Secure Setup & Deployment

1. SSH into the production server.
2. Clone the repo or pull latest changes:

   git pull

3. Create the environment file:

   cp .docker/production/.env.example .docker/production/.env

   • Fill in all production secrets: database credentials, JWT secret, BankID client ID/secret, etc.
4. Start the app:

   ./env.sh production up

5. To stop:

   ./env.sh production down

🔍 Post-Deployment Checklist

• Check logs: docker logs bankid-app