Your code. Your deployment.
Keep it static.
Or give it a new home.
OpenStays has two different hosting paths: this lightweight project site, and the full booking application preserved in the source. Choose the one you actually need.
Two paths. Different responsibilities.
A project showcase
Publish the static-site/ directory. It needs no build, JavaScript, database, authentication or payment service. All examples remain fictional.
An operational booking app
Run the React frontend with a fresh Convex backend. Add property data and configure staff access, optional providers, backups and acceptance checks.
The former hosted booking service is no longer offered. Historical deployment URLs and keys are not a starting point for a new installation. The code remains available; each new operator owns a separate deployment.
Publish the static site.
The static-site/ folder is already the finished output. Upload it to Cloudflare Pages, Workers static assets, or any host that serves HTML and CSS. Use no application build command and provision no Convex project.
git clone --branch nostr-main https://github.com/murdawkmedia/openstays.git
cd openstays
python3 scripts/check-static-site.py
The GitHub repository is a passive public mirror of the maintained Nostr source. Check the latest source and release notes before choosing a revision.
- Publish directory:
static-site. - Primary path:
/openstays/, with/openstays/hosting/as this guide. - Backend variables and secrets: none.
- Portability: assets and navigation use relative paths. On another domain, update both HTML canonical/social URLs and structured data, then run the contract checker with the matching canonical base.
- Search discovery: include both page URLs in the host’s sitemap and keep the pages crawlable. Structured data describes visible content; it does not guarantee search features or AI citations.
Explore the booking app first.
For a disposable test installation, install a supported Node.js version that meets the pinned Vite engine requirement, then use the lockfile. The commands below create or select your own backend; verify that selection before pushing functions.
npm ci
npx convex dev
Follow the CLI to create a new, dedicated development project and leave it running. In a second terminal, configure only this disposable backend and seed its fictional inventory:
npx convex env set DEMO_MODE true
npx convex env set EMAIL_PROVIDER log_only
npm run seed
Add these non-secret frontend flags to the generated local environment file. They keep the experimental wallet and real payment rails out of this test view:
VITE_PUBLIC_SHOWCASE=true
VITE_PUBLIC_STAFF=false
VITE_PUBLIC_WAVELENGTH=false
VITE_PUBLIC_ZAPRITE=false
VITE_PUBLIC_SIMULATED=true
npm run dev
The CLI supplies the development VITE_CONVEX_URL. The seed contains fictional Pinewood Flats inventory. Demo mode enables simulated behavior and reset tasks: never enable it on a backend with real guest or payment data.
For account-free local exploration, the source quickstart also documents CONVEX_AGENT_MODE=anonymous npx convex dev. This is a development path, not a production hosting recipe.
Restart for a real operator.
Use the reduced production profile. It preserves lodging and staff foundations while excluding the experimental hackathon, wallet, reward, treasury and demo surfaces. Keep operator data and deployment secrets outside the public repository.
- Create separate development/staging and production backends. Never reuse an old showcase endpoint or copy an old deployment credential.
- Generate the reduced function tree:
npm run production:verify. In your deployment checkout, setconvex.jsonto use"functions": "convex-production/". Code generation and deployment must target this generated directory, not the full showcaseconvex/tree. - Set
VITE_OPENSTAYS_PROFILE=productionand the new backend’s publicVITE_CONVEX_URL. Keep demo/public-simulation flags disabled. Generate deployment-specific bindings before release. - Configure staff authentication and bootstrap the first authorized owner using the source runbook. An account alone does not grant staff access. Load reviewed property inventory, then enable and accept staff workspaces one at a time.
- Configure only the providers you need. Keep payment keys, email credentials, signing keys and deploy keys in backend or host secret stores. A
VITE_variable is public browser configuration, never a safe place for secrets.
For the frontend, build the production profile and serve the resulting dist/ on a static host. Configure navigation fallbacks for application deep links. Backend functions and frontend must be released together against the same target.
npm run production:verify
npm run typecheck
VITE_OPENSTAYS_PROFILE=production npm run build
With the generated backend directory configured and a fresh deployment key stored privately in the host, a paired release can use:
VITE_OPENSTAYS_PROFILE=production npx convex deploy --cmd 'npm run build'
Configure SITE_URL for the new frontend origin, deployment-specific auth keys and callback URLs, provider webhooks, and backup/retention behavior. Old URLs are historical records, not reusable service identities. Hosting and provider costs depend on your usage and plans.
Run the backend yourself.
Self-hosting the frontend does not remove the booking app’s backend requirement. To avoid Convex Cloud, use the open-source Convex backend on infrastructure you operate. Follow its current official setup instructions and use your own backend URL and admin/deployment credentials.
The application still depends on Convex’s transactional and reactive semantics. This is not a database swap. The backend has separate license terms from the MIT-licensed OpenStays app; review them for your intended use. You own storage, TLS, authentication configuration, upgrades, file storage, scheduled work, backups and restoration tests. The repository does not provide a fully packaged production self-hosted deployment.
Use the same reduced production function tree and operator acceptance boundary. Validate compatibility and deployment behavior against the backend version you choose; do not connect a new frontend to a historical hosted instance.
Before you accept real stays.
A successful build is one check. An operating lodging system needs the complete guest and staff paths verified against your own configuration.
- Run the source tests and typecheck. Verify that the release artifacts contain only the intended production profile.
- Test overlapping holds, cancelled stays, local dates, rates, taxes, deposits, minimum stays and turnover buffers.
- Verify staff roles and property scope, account recovery, and access to guest and payment information.
- Test provider sandbox payments, verified webhooks, retries and refunds. Browser redirects alone never establish payment success.
- Verify confirmation delivery and cancellation notices, iCal imports/exports and manual conflict handling.
- Review security, privacy, retention, monitoring, backups and an isolated restore. Keep customer data and sensitive archives out of public Git.
- For channel connectivity, obtain provider access and complete certification and property mapping. iCal polling is not instant OTA inventory locking.
The public source contains historical experiments and release notes. Prefer the production-profile runbook for a real lodging deployment, and treat every provider activation as a separate acceptance step.