Skip to main content
Omnibeds is a Next.js app, so you start it, migrate it and test it with npm scripts from the project’s package.json. This page lists those scripts in the order you use them while working on a change.
Supplier keys and the database connection live only in .env.local on your machine and in the hosting provider’s settings. They are never committed, and these docs never show them.

Work on a change

1

Start the app

The dev server runs on port 3086, so open http://localhost:3086.
2

Apply database migrations

This applies every migration the database hasn’t had yet. Running it again changes nothing. See Data.
3

Check types and lint

4

Run the unit tests

Database tests run against an in-process Postgres (PGlite), so they never touch a real database.
5

Run the end-to-end tests

Playwright starts the app itself and drives the real screens: search, booking, quotes, trips, documents and every screen in both languages.
6

Build for production

Live supplier checks

These tests call the real suppliers’ test environments, so they spend real quota. Every test that makes a booking cancels it at the end, even when the test fails. Run them when you change a supplier adapter, not on every change.

The layers

Where your change belongs.

Testing

What each kind of test covers, and the boundary tests.