Docker

Database Options

Skylite UX supports two database backends. SQLite is the default and recommended for most users.

SQLite (Default - Recommended)

SQLite runs inside the same container - no external database needed. Perfect for:

Single-user or family deployments
Raspberry Pi or low-resource devices
Simple self-hosted setups

Just mount a volume for persistent storage:

docker run -d \
  -p 3000:3000 \
  -v /path/to/data:/data \
  -e NUXT_PUBLIC_TZ=America/Chicago \
  --name skylite-ux \
  y3knik/skylite-ux:beta

Your database will be stored at /path/to/data/skylite.db.

PostgreSQL (Optional)

If you prefer PostgreSQL for production or multi-user deployments, set the DATABASE_URL environment variable:

docker run -d \
  -p 3000:3000 \
  -e DATABASE_URL="postgresql://user:password@host:5432/skylite" \
  -e NUXT_PUBLIC_TZ=America/Chicago \
  --name skylite-ux \
  y3knik/skylite-ux:beta

Quick Start with SQLite

The simplest way to get started:

# Create a directory for your data
mkdir -p ~/skylite-data

# Run Skylite UX
docker run -d \
  -p 3000:3000 \
  -v ~/skylite-data:/data \
  -e NUXT_PUBLIC_TZ=America/Chicago \
  -e GOOGLE_CLIENT_ID=your_client_id \
  -e GOOGLE_CLIENT_SECRET=your_client_secret \
  --name skylite-ux \
  y3knik/skylite-ux:beta

Then open http://localhost:3000 in your browser.

Note: Google OAuth credentials are optional but required for Google Calendar, Photos, and Tasks integrations.

Docker Compose

SQLite Version (Recommended)

services:
  skylite-ux:
    image: y3knik/skylite-ux:beta
    restart: unless-stopped
    environment:
      - NUXT_PUBLIC_TZ=America/Chicago
      - NUXT_PUBLIC_LOG_LEVEL=warn
      # Google OAuth (optional - required for Calendar, Photos, Tasks)
      - GOOGLE_CLIENT_ID=
      - GOOGLE_CLIENT_SECRET=
      # Photo storage (optional - default: /data/photos)
      # - PHOTOS_STORAGE_PATH=/data/photos
    volumes:
      - ./data:/data # Contains database (skylite.db) and photos (/data/photos)
    ports:
      - 3000:3000

PostgreSQL Version

services:
  skylite-ux:
    image: y3knik/skylite-ux:beta
    restart: unless-stopped
    environment:
      - DATABASE_URL=postgresql://skylite:password@skylite-ux-db:5432/skylite
      - NUXT_PUBLIC_TZ=America/Chicago
      - NUXT_PUBLIC_LOG_LEVEL=warn
      # Google OAuth (optional - required for Calendar, Photos, Tasks)
      - GOOGLE_CLIENT_ID=
      - GOOGLE_CLIENT_SECRET=
    depends_on:
      skylite-ux-db:
        condition: service_healthy
    ports:
      - 3000:3000
    networks:
      - skylite-network

  skylite-ux-db:
    image: postgres:16
    restart: unless-stopped
    environment:
      - POSTGRES_USER=skylite
      - POSTGRES_PASSWORD=password
      - POSTGRES_DB=skylite
    volumes:
      - postgres-data:/var/lib/postgresql/data
    healthcheck:
      test: [CMD-SHELL, pg_isready -U skylite]
      interval: 10s
      timeout: 5s
      retries: 5
    networks:
      - skylite-network

networks:
  skylite-network:
    driver: bridge

volumes:
  postgres-data:
    driver: local

Configuration

Required

Variable	Description	Example
`NUXT_PUBLIC_TZ`	Your timezone	`America/Chicago`, `Europe/London`

Database

Variable	Description	Default
`DATABASE_URL`	Database connection string	`file:/data/skylite.db` (SQLite)
`PRISMA_ACCEPT_DATA_LOSS`	Allow destructive schema changes on startup	`false`

DATABASE_URL formats:

SQLite (default): file:/data/skylite.db or file:/custom/path/mydb.db
PostgreSQL: postgresql://user:password@host:5432/dbname

If DATABASE_URL is not set, SQLite is used with the default path /data/skylite.db.

PRISMA_ACCEPT_DATA_LOSS:

When set to true, allows Prisma to apply destructive schema changes automatically during startup. Only use this if you understand the risks of potential data loss during schema migrations.

-e PRISMA_ACCEPT_DATA_LOSS=true

Application

Variable	Description	Default
`NUXT_PUBLIC_LOG_LEVEL`	Logging level	`info`

Valid log levels: debug, info, warn, error

Photo Storage

Variable	Description	Default
`PHOTOS_STORAGE_PATH`	Directory for downloaded photo cache	`/data/photos`

Important for Docker deployments:

When using Google Photos integration, selected album cover photos are downloaded and cached locally for persistent display. By default, photos are stored at /data/photos inside the container, which is included in the /data volume mount.

Default behavior (recommended):

Photos stored at /data/photos (persisted in /data volume)
Survives container restarts and rebuilds
Shared storage with SQLite database

Custom storage path:

-e PHOTOS_STORAGE_PATH=/custom/path

If you change this path, ensure it’s either:

Inside the /data volume (e.g., /data/custom-photos)
A separately mounted volume

Storage requirements:

Approximately 300-600 KB per photo (at 1920×1080)
1000 photos ≈ 300-600 MB

Google Integrations

To enable Google integrations (Calendar, Photos, Tasks), add these environment variables:

Variable	Description
`GOOGLE_CLIENT_ID`	Your Google OAuth Client ID
`GOOGLE_CLIENT_SECRET`	Your Google OAuth Client Secret

Setup steps:

Go to Google Cloud Console
Create a project (or select existing)
Enable APIs:
- Google Calendar API
- Google Tasks API
- Google Photos Library API
Create OAuth 2.0 Client ID (Web application)
Add authorized redirect URIs (use http:// for local/dev, https:// for production):
- http://localhost:3000/api/integrations/google_calendar/callback (or https://your-domain.com/api/integrations/google_calendar/callback for production)
- http://localhost:3000/api/integrations/google_tasks/callback (or https://your-domain.com/api/integrations/google_tasks/callback for production)
- http://localhost:3000/api/integrations/google_photos/callback (or https://your-domain.com/api/integrations/google_photos/callback for production)

See the integration documentation for more details: