Skip to main content

​
Conceptual questions

Several common “can I do X?” questions come down to something not being built yet — see Known Limitations for the full list in one place.
Not today — see Known Limitations.
Less than you’d expect — see Known Limitations.
Not through the UI yet — see Known Limitations.
Not today — see Known Limitations.
The admin role only goes to the very first account in an empty users table. If you’re testing this and it didn’t happen, you likely registered against a database that already had a user in it — reset with php artisan migrate:fresh (or make fresh in Docker) and register again on a clean database.

​
Setup issues

This almost always means one of the setup steps was skipped: copying .env.example to .env, generating an app key (php artisan key:generate), or running migrations. Re-run composer setup (native) or make setup (Docker) — see Quickstart.
Make sure you’ve actually run a frontend build (npm run build) or have the Vite dev server running (npm run dev, or composer dev / make dev which start it alongside the backend). Orbit’s pages expect Vite-built assets to be present — the app won’t render correctly with a .env set up but no frontend build.
See the dedicated troubleshooting note in the Docker guide — this is a known issue with the file watcher desyncing, especially on non-native storage.
Orbit needs PHP 8.4+ and Node.js 22+. If composer setup or npm install fails with dependency resolution errors, check your local versions before assuming it’s a project bug.
Didn’t find your issue here? Search existing issues on GitHub, or open a new one.