Lewati ke konten dokumentasi

Terjemahan Sedang Berlangsung

Dokumen ini saat ini disediakan dalam bahasa Inggris sementara terjemahan Bahasa Indonesia sedang dipersiapkan.

Self-Hosting and Deployment Overview

Aqiled is an open-source, independent school information system built for institutional autonomy. Any school, educational trust, or developer can request the source code, deploy it on their own infrastructure, and retain full ownership over student records.

Tersedia sekarang. Terakhir ditinjau: 26 October 2026.

System Architecture

Aqiled consists of three primary components:

  1. Back-End API (/back-end): Built with .NET 8/9/10 and PostgreSQL 18. Handles business logic, authentication, multi-tenancy, Row-Level Security (RLS), Hangfire background processing, and SignalR real-time hubs.
  2. Main Application (/front-end): Built with React, Vite, Tailwind CSS, and TypeScript. Used by teachers, school staff, administrators, students, and parents.
  3. Platform Admin Portal (/admin-portal): Used solely by platform operators in multi-tenant environments. Disabled in single-school installations.
  1. 1Server Hardware & OS
  2. 2PostgreSQL 18 with RLS
  3. 3.NET API Service
  4. 4Nginx/Caddy Reverse Proxy
  5. 5React Web App

Deployment Modes

Aqiled supports two operational deployment modes:

  • Dedicated Single-School Mode (Recommended for Open-Source):
    • Each school runs on its own isolated server or container.
    • Uses dedicated database credentials and a locked deploymentidentity marker.
    • Disables platform-wide superadmin endpoints, demo signup, and cross-school routing.
    • Front-end connects directly to same-origin /api endpoints without third-party cloud routing.
  • Multi-Tenant Mode:
    • A single platform deployment manages multiple school tenants isolated by PostgreSQL Row-Level Security.
    • Uses subdomain or header-based routing to resolve individual schools.

Guide Roadmap

To get your instance running, follow the guides in order:

  1. System & Database Prerequisites — Sizing, PostgreSQL 18 enforcement, and database role configuration.
  2. Choose your deployment path:
  3. School Provisioning & Single-School Mode — Running provision-school and setting the tenant identity.
  4. Reverse Proxy & WebSockets — Nginx or Caddy configuration for SSL and SignalR.
  5. Troubleshooting & Health Checks — Readiness checks (/health/ready) and common error resolutions.