Skip to the article
Aniq-UI

HollinaRun the booking business locally

Run the booking business locally

Get your package running on your computer, with Docker.

For the Full Stack package

DockerRecommendedManual setup

Before you start: install and open Docker Desktop, or Docker Engine with Compose.

View requirements

  1. Download your template

    Open My templates and download the ZIP for your package.

    Expected result: A file named like hollina-vacation-rental-full-stack-….zip is in your downloads.

  2. Unzip and open the folder

    Open a terminal where the ZIP is, extract it and move into the hollina-vacation-rental-full-stack folder. On Windows, you can extract it in File Explorer instead, then open a terminal in the folder.

    Terminal
    unzip -q hollina-vacation-rental-full-stack-*.zip
cd hollina-vacation-rental-full-stack

    Expected result: The folder lists admin-dashboard, back-end, storefront and docker-compose.yml, beside README.md, QUICKSTART.md and LICENSE.md.

    Having trouble?

  3. Start the apps

    Build and start the API, the stays website and the booking dashboard. Nothing has to be configured first. The first start builds three images and fills the database with the demo company, which takes a few minutes; later starts take seconds.

    Terminalin hollina-vacation-rental-full-stack
    docker compose up --build

    A port is already in use?

    If the start stops with ports are not available, address already in use or port is already allocated, another program uses 3030, 3031 or 8000. Either stop it, or create a file named .env in the hollina-vacation-rental-full-stack folder, beside docker-compose.yml, with the port you need, such as ADMIN_PORT=3041 (SITE_PORT for the website, API_PORT for the API). Run docker compose up --build again and open the app on its new port.

    A port is already in use

    Expected result: The three services keep running and the log stops scrolling. Leave this terminal open.

    Having trouble?

  4. Open the stays website

    Open localhost:3030Local. English is at /en and Arabic at /ar. The website has no accounts: saved stays are kept in the visitor's browser, and a guest finds a booking again with its reference and the email it was made with. Without payment keys the shipped simulator takes every card and PayPal booking, so the whole checkout works; a card number ending in 0 is declined, to show the failure path.

    Expected result: The website opens on its home page with the demo stays, their photographs and the destinations.

    Having trouble?

  5. Sign in to the booking dashboard

    Open localhost:3031Local. Sign in with admin@hollina.example and the password Admin@123. For the manager, type manager@hollina.example with Manager@123. Change both passwords before the stack is reachable from the internet.

    Expected result: The dashboard opens on its overview, with this month's occupancy and revenue, today's arrivals and departures, and the latest bookings.

    Having trouble?

Take a tour

What the demo company looks like once everything runs.

AccountEmailPassword
Super Admin: every page and permissionadmin@hollina.exampleAdmin@123
Manager: the overview, calendar, bookings, stays, inquiries, reviews and the AI assistant; no admins, roles or company settingsmanager@hollina.exampleManager@123

The seed adds 14 stays (12 published, 2 drafts) with 42 photographs, 6 destinations, 18 amenities, 60 bookings across the year, 8 blocked ranges, 12 guest questions, 24 reviews and 6 home page questions, so every screen opens full. Dates are stored as offsets from the day of the seed, so a fresh database always has arrivals today. These are local demo accounts only.

Stop and start again

Press Ctrl+C in the terminal to stop the apps, or run this from the hollina-vacation-rental-full-stack folder. Your data, the database and the uploads, is kept in the hollina-data volume.

Terminalin hollina-vacation-rental-full-stack
docker compose down

Start again with the same command as step 3. Without --build it reuses the images you already built.

Terminalin hollina-vacation-rental-full-stack
docker compose up

Keep your data

docker compose down -v also deletes the data volume. The next start seeds a fresh copy of the demo company, and everything you created is gone.

Run the stays website

This package is the stays website on its own. It reads everything from the Hollina API, so start the API first. Unless you build it with another address, the website expects the API at http://localhost:8000. The API is a separate package and is not in this download.

  1. Download your template

    Open My templates and download the Stays Website ZIP.

  2. Unzip and open the folder

    Terminal
    unzip -q hollina-website-*.zip
cd hollina-website

    Expected result: The folder has a Dockerfile and a package.json.

    Having trouble?

  3. Build the image

    The NEXT_PUBLIC_* values are compiled into the JavaScript the browser loads, so they are build arguments. Without any, the website uses the API at http://localhost:8000/api and calls itself http://localhost:3030. For an API somewhere else, pass its address.

    Terminalin hollina-website
    docker build -t hollina-website .

    With your own API and domain:

    Terminalin hollina-website
    docker build -t hollina-website --build-arg NEXT_PUBLIC_API_BASE_URL=https://api.your-company.com/api --build-arg NEXT_PUBLIC_SITE_URL=https://www.your-company.com --build-arg NEXT_PUBLIC_MEDIA_HOSTNAME=media.your-company.com .
    Having trouble?

  4. Start it

    Inside the container localhost is the container itself, so API_INTERNAL_URL tells the website's own server where to reach the API on your computer, for the page titles, the first render of the home and stay pages, and the sitemap. --add-host makes host.docker.internal work on Linux; Docker Desktop already has it. If port 3030 is taken, change the number on the left of -p, for example -p 3041:3030, open that port instead, and add http://localhost:3041 to the API's CORS_ORIGIN.

    Terminalin hollina-website
    docker run -p 3030:3030 -e API_INTERNAL_URL=http://host.docker.internal:8000/api --add-host=host.docker.internal:host-gateway hollina-website

    Expected result: localhost:3030Local opens the website with the stays from your API. English is at /en, Arabic at /ar.

    Having trouble?

Run the booking dashboard

This package is the booking dashboard on its own. Every screen reads the Hollina API, so start the API first. Unless you build it with another address, the dashboard expects the API at http://localhost:8000. The API is a separate package and is not in this download.

  1. Download your template

    Open My templates and download the Booking Dashboard ZIP.

  2. Unzip and open the folder

    Terminal
    unzip -q hollina-booking-dashboard-*.zip
cd hollina-booking-dashboard

    Expected result: The folder has a Dockerfile and a package.json.

    Having trouble?

  3. Build the image

    Without build arguments the dashboard uses the API at http://localhost:8000/api. For an API somewhere else, pass its address, its address without /api for the live notifications, and the website's address for the "Back to website" link and the stay editor's "View stay".

    Terminalin hollina-booking-dashboard
    docker build -t hollina-dashboard .

    With your own API:

    Terminalin hollina-booking-dashboard
    docker build -t hollina-dashboard --build-arg NEXT_PUBLIC_API_BASE_URL=https://api.your-domain.com/api --build-arg NEXT_PUBLIC_WEBSOCKET_BASE_URL=https://api.your-domain.com --build-arg NEXT_PUBLIC_MEDIA_HOSTNAME=api.your-domain.com --build-arg NEXT_PUBLIC_SITE_URL=https://your-domain.com .
    Having trouble?

  4. Start it and sign in

    If port 3031 is taken, change the number on the left of -p, for example -p 3041:3031, open that port instead, and add http://localhost:3041 to the API's CORS_ORIGIN (and set its FRONTEND_URL to it, the address the live notifications connect from).

    Terminalin hollina-booking-dashboard
    docker run -p 3031:3031 hollina-dashboard

    Expected result: localhost:3031Local opens the sign-in form. Sign in with admin@hollina.example and the password Admin@123, which a seeded API accepts.

    Having trouble?

Run the API

This package is the NestJS API on its own, on a SQLite file kept in a Docker volume with the uploads. The stays website and the booking dashboard are separate packages and are not in this download.

  1. Download your template

    Open My templates and download the Backend API ZIP.

  2. Unzip and open the folder

    Terminal
    unzip -q hollina-backend-*.zip
cd hollina-backend

    Expected result: The folder has a Dockerfile, a docker-entrypoint.sh and a package.json.

    Having trouble?

  3. Build the image

    Terminalin hollina-backend
    docker build -t hollina-api .
    Having trouble?

  4. Start it with the demo company

    A new volume gets empty tables and no accounts unless you ask for the demo company, so keep -e SEED_DEMO_DATA=true for a first start. The hollina-api-data volume keeps the database and the uploads between runs. If port 8000 is taken, change the number on the left of -p, for example -p 8010:8000, and add -e PUBLIC_MEDIA_URL=http://localhost:8010/media so the photograph addresses use it too. Your frontends must then point at http://localhost:8010/api.

    Terminalin hollina-backend
    docker run -p 8000:8000 -v hollina-api-data:/data -e SEED_DEMO_DATA=true hollina-api

    Expected result: localhost:8000/api/healthLocal answers with "status":"ok" and "database":"up".

    Having trouble?

The container accepts the website on http://localhost:3030 and the dashboard on http://localhost:3031. On other addresses, set CORS_ORIGIN (both, comma separated), FRONTEND_URL (the dashboard) and SITE_URL (the website, where a payment processor sends the guest back) with -e. Without payment keys the shipped simulator settles every card and PayPal booking.

To give the container your own keys (Stripe, PayPal, R2, AI, MCP), create .env from .env.example with cp .env.example .env, fill it in, and add --env-file .env -e NODE_ENV=production to docker run:

Terminalin hollina-backend
docker run -p 8000:8000 -v hollina-api-data:/data -e SEED_DEMO_DATA=true --env-file .env -e NODE_ENV=production hollina-api

A value given with -e wins over the same name in the file, so the container runs in production whatever .env says, and it moves the file's relative paths (SQLITE_DATABASE, MEDIA_UPLOAD_DIR) into the volume. Without a JWT_SECRET of your own, or with the example one, the container generates a secret and keeps it in the volume, so sign-ins survive a restart.

Next

Stuck on a step?

Find a fix before you start over.

Troubleshooting

Cookie Preferences

We use cookies to enhance your browsing experience, analyze site traffic, and personalize content. By clicking "Accept All", you consent to our use of cookies for analytics and personalized advertising.