Skip to main content

​
Install the application (PWA)

Open Marketplace for families, tutors and institutes, or the school portal for an OHADA school. In Chrome/Edge, use the install icon or offered button. On Android use the installation menu; on iOS Safari use Share then Add to Home Screen. See getting started. The installed app uses the same account. Its previously loaded interface may remain available offline; payments, messages and remote APIs still require connectivity. Local school operations always require a reachable school server.

​
Deploy Ardoise School for an OHADA school

This is not an Austrian School offering and is not required for an institute. The German guide is an OHADA reference, not an OHADA product language.
  1. The founder obtains their activation code. Prepare Docker and Docker Compose on the machine dedicated to the school.
  2. Use the current release’s deployment package, including docker-compose.yml and its referenced docker/ files. A Compose command in an empty directory does not download those files.
  3. Review database/file volumes, network access and database credentials. Replace shipped demonstration Compose credentials for production, consistently across services. Do not publish secrets.
  4. Start services from the deployment directory:
  1. Open http://localhost:8000 on that machine, finish setup with the code and restart the application service if requested. The installation key and configuration are stored locally; the setup journey requires no .env file.
  2. For remote access, start the existing tunnel connector. In API Integrations, check the read-only address and connection probe before adding staff. A reserved address is not an online server.

​
Production and backups

Production uses one school, one PostgreSQL database, persistent database/file volumes and the provided backup service. SQLite or standalone docker run is for compatibility/testing/development, not this production installation. Check backups and a test restore. An exposed server must use HTTPS through the existing tunnel or a correctly configured HTTPS entry point. Do not directly expose the application port on the internet. Security/cookie settings must match HTTPS; HTTP development settings are not production settings.