Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/FlasheyEstudi/Oasis-Liquido/llms.txt

Use this file to discover all available pages before exploring further.

Both the Backend and Frontend are Next.js applications. Each produces a self-contained standalone bundle at .next/standalone/server.js when built. In production you start each bundle with Bun, passing NODE_ENV=production. The Backend API listens on port 8000 and the Frontend on port 3000. Both directories also include a Caddyfile if you want to place a reverse proxy in front of them.

​
Services at a glance

ServicePortStart command
Backend API8000NODE_ENV=production bun .next/standalone/server.js
Frontend3000NODE_ENV=production bun .next/standalone/server.js

​
Build and deploy

1

Set environment variables

At minimum the Backend requires DATABASE_URL. Set it in a .env file or export it before building:
DATABASE_URL="file:./prisma/db/oasis.db"
2

Build the Backend

From the repository root:
cd Backend && npm run build
This runs next build and then copies the static assets and public directory into the standalone output folder.
3

Start the Backend

NODE_ENV=production bun .next/standalone/server.js
The API is now available on port 8000.
4

Build the Frontend

cd Frontend && npm run build
5

Start the Frontend

NODE_ENV=production bun .next/standalone/server.js
The web app is now available on port 3000.
Both the Backend and Frontend directories contain a Caddyfile for optional reverse proxy configuration. Use Caddy to add HTTPS, handle domain routing, or proxy both services behind a single hostname.
Use Bun as your runtime. Both apps ship a bun.lock lockfile, which means dependencies were resolved with Bun and the standalone server is tested against it. Running the server with bun instead of node is the recommended and tested path.

Build docs developers (and LLMs) love

Get started for freeTalk to us