Automated tests
PHPUnit for the backend, Vitest for the frontend and Playwright for end-to-end tests in a real browser.
Technology
Modern stack. No exotic know-how.
QuickTribe relies on widespread, long-term maintained open-source technologies. That makes operations predictable – and it is easy to find developers who can work with the source code.
Stack
What QuickTribe is made of
One app image for web and background jobs, plus MariaDB, Redis and a real-time hub. That is all it takes.
The architecture is designed for several app containers behind a load balancer, should your community grow.
- Backend
- PHP 8.5, Symfony 8, Doctrine ORM, Messenger, Scheduler
- Frontend
- Vue 3 with TypeScript, Vite, Pinia, Tailwind CSS
- Database
- MariaDB 11 (InnoDB, utf8mb4) with versioned migrations
- Cache & queue
- Redis for sessions, cache, rate limiting and background jobs
- Real time
- Mercure hub for chat and live notifications
- Editor
- Tiptap, output sanitised on the server
- Videos
- Transcoding to HLS with ffmpeg for adaptive streaming
- Operations
- Docker Compose, configuration purely through environment variables
Quality
Tested from backend to browser
Static analysis
PHPStan at a strict level (level 8), strict TypeScript, ESLint, Prettier and php-cs-fixer.
Typed API
The JSON API is described as OpenAPI from the PHP DTOs; the frontend TypeScript types are generated from it.
Verified releases
Every release package is started and tested exactly like a licensee would before delivery – including a browser test.
Security & operations
Built for production
Per-community permissions
Every query is scoped to the community; permissions are checked centrally via Symfony voters.
Sign-in
Two-factor authentication, optional Google sign-in, rate limiting against brute-force attempts.
Secrets
The app refuses to start with missing or placeholder secrets – misconfigurations surface immediately.
Monitoring
Health endpoint for uptime monitoring, JSON logs with request ID, optional Sentry or GlitchTip.
For developers
Extend instead of work around
The source code follows clear conventions: every area (feed, courses, calendar, members, messages …) is its own Vue app with its own API, and the backend separates domain, application, infrastructure and HTTP layers.
- Local development environment via
make upwith demo data - Architecture decisions documented as ADRs in the repository
- One pipeline for tests, linting, image build and release package
Let's get started
Technical questions?
We are happy to walk you or your development team through architecture, operations and customisation options.