Add docker support

[DeyanM1]

added Docker container support to lanis-ui:

Run it

From the project folder, on any machine with Docker + Docker Compose installed:

docker compose up --build

To run it in the background:

docker compose up --build -d

To stop it:

docker compose down

[appwrite]

Lanis

Project ID: 698337a60017b46df380

Sites (2)

Site	Status	Logs	Preview	QR
LANiS Appwrite Preview lanis-ui-appwrite-preview	Queued	Authorize	Preview URL
lanis_ui 6a180889003c768d3660	Queued	Authorize	Preview URL

Tip

Trigger functions via HTTP, SDKs, events, webhooks, or scheduled cron jobs

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 4d41c4ab-60ac-477b-b218-be5614aba381

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[greptile-apps]

Confidence Score: 3/5

The PR should not merge until container startup preserves developer file ownership and rebuilt images reliably use updated dependencies.

The default Compose workflow can create a root-owned .env in the host repository and can continue using stale node_modules after dependency manifests are rebuilt.

Files Needing Attention: Dockerfile, docker-compose.yml, and dockerentry.sh

Important Files Changed

Filename	Overview
Dockerfile	Builds the Node/Chromium development image, but leaves runtime startup as root, causing host-mounted files created by the entrypoint to be root-owned.
docker-compose.yml	Publishes the correct development port and enables live source mounting, but its persistent node_modules volume can mask dependencies from rebuilt images.
dockerentry.sh	Initializes .env and launches the requested command, but neither handles non-root ownership nor synchronizes the mounted dependencies.
.dockerignore	Excludes local dependencies, Git metadata, environment data, and Docker metadata from the build context.

_{Reviews (1): Last reviewed commit: "Add docker support" | Re-trigger Greptile}

[greptile-apps]

Root-owned environment file

When Compose starts without an existing .env, the root entrypoint writes the file through the bind-mounted repository, causing the host-side .env to be root-owned and potentially uneditable or undeletable without elevated privileges.

[greptile-apps]

Stale dependency volume

When a dependency manifest changes and the documented docker compose up --build command recreates the service, the existing /app/node_modules volume masks the dependencies installed in the rebuilt image, causing missing-module failures or execution against stale package versions.