reVISit study – Interactive, Web-Based User Studies

Create interactive, web-based data visualization user studies by editing study configs and adding stimuli in public/.

For full local + DigitalOcean deployment/testing instructions, see deploy/DEPLOYMENT_RUNBOOK.md.

Local development (native)

1. Install Node + Yarn.

2. Install dependencies:

   yarn install

3. Run the frontend dev server:

   yarn serve

4. Open http://localhost:8080.

Optional: local Supabase for native dev

1. Start Supabase services (with local ports):

   docker network inspect revisit_net >/dev/null 2>&1 || docker network create revisit_net

   docker compose -f supabase/docker-compose.yml -f supabase/docker-compose.local.yml --env-file supabase/.env up -d

2. Point your local Vite app to Kong by setting:

   VITE_STORAGE_ENGINE="supabase"

   VITE_SUPABASE_URL="http://localhost:8000"

   VITE_SUPABASE_ANON_KEY="<same value as ANON_KEY in supabase/.env>"

Full local Docker workflow

This runs app + reverse proxy + Supabase in containers.

1. Create shared network once:

   docker network inspect revisit_net >/dev/null 2>&1 || docker network create revisit_net

2. Start Supabase stack:

   docker compose -f supabase/docker-compose.yml --env-file supabase/.env up -d

3. Start app + Caddy proxy:

   VITE_SUPABASE_ANON_KEY="<ANON_KEY from supabase/.env>" docker compose -f docker-compose.local.yml --env-file deploy/.env.local.example up -d --build

4. Open:

   • App: http://localhost:8080
   • API base: http://api.localhost:8080

If api.localhost does not resolve on your machine, add 127.0.0.1 api.localhost to your hosts file.

Production Docker deployment (DigitalOcean/VM)

This setup uses two public domains:

• Study UI: study.<your-domain>
• Supabase API gateway: api.<your-domain>

1. Copy and edit env templates:

   • cp deploy/.env.prod.example deploy/.env.prod
   • Update deploy/.env.prod with real domains.
   • Update supabase/.env with strong secrets and production URLs.

2. Ensure these Supabase values match your domains:

   • SITE_URL=https://<study-domain>
   • API_EXTERNAL_URL=https://<api-domain>
   • SUPABASE_PUBLIC_URL=https://<api-domain>

3. Create shared network:

   docker network inspect revisit_net >/dev/null 2>&1 || docker network create revisit_net

4. Start Supabase services:

   docker compose -f supabase/docker-compose.yml --env-file supabase/.env up -d

5. Build/start app + reverse proxy:

   VITE_SUPABASE_ANON_KEY="<ANON_KEY from supabase/.env>" docker compose -f docker-compose.prod.yml --env-file deploy/.env.prod up -d --build

6. Open firewall only for 80/443 publicly. Keep admin/internal ports private.

Notes

• The app image now serves SPA routes correctly via nginx fallback to index.html.
• Production Docker build forces VITE_BASE_PATH=/.
• Configure your root app .env / build args for VITE_STORAGE_ENGINE, VITE_SUPABASE_URL, and VITE_SUPABASE_ANON_KEY to match your deployment.