**Tags:** "Hello World" Examples · React # React Router Static Hello World A complete [React Router v7](https://reactrouter.com) hello world recipe for [Zerops](https://zerops.io) — deploying a React Router v7 SPA (static mode, no SSR) as a static site built by Node.js and served by Nginx, with ready-made environment configurations demonstrating build-time environment variable injection via Vite. ### Available Environments - [AI Agent](https://app.zerops.io/recipes/react-router-static-hello-world.md?environment=ai-agent) - [Remote (CDE)](https://app.zerops.io/recipes/react-router-static-hello-world.md?environment=remote-cde) - [Local](https://app.zerops.io/recipes/react-router-static-hello-world.md?environment=local) - [Stage](https://app.zerops.io/recipes/react-router-static-hello-world.md?environment=stage) - **Small Production** ← current - [Highly-available Production](https://app.zerops.io/recipes/react-router-static-hello-world.md?environment=highly-available-production) ### Services in this Environment **Services:** - **core** (core@1) - Containers: 1 × Shared Core, 0.00 GB RAM, 0 GB Disk - **app** (static) - Containers: 2 × Shared Core, 0.38 GB RAM, 1 GB Disk - Repository: [zerops-recipe-apps/react-router-static-hello-world-app](https://github.com/zerops-recipe-apps/react-router-static-hello-world-app) **Total Resources:** 3 containers, 0.75 GB RAM, 2 GB Disk ### One-Click Deploy (Import YAML) Use this YAML with `zcli project import` to deploy this environment: ```yaml # React Router v7 Hello World — Small Production Environment # # A production-ready setup optimised for moderate throughput. # Two Nginx containers distribute traffic and ensure the app # remains available during zero-downtime deploys. project: name: react-router-static-hello-world-small-prod services: - hostname: app type: static # Zerops pulls the source code and zerops.yaml from this # public repo to trigger the build/deploy pipeline. buildFromGit: https://github.com/zerops-recipe-apps/react-router-static-hello-world-app # Selects the 'prod' setup — Node.js compiles the React # Router v7 SPA into static assets; Nginx serves them. # The build container is deleted after deploy; Node.js is # NOT present in the Nginx runtime containers. zeropsSetup: prod enableSubdomainAccess: true # Always run at least 2 containers so traffic is distributed # and the app stays available while new containers start # during zero-downtime deploys. minContainers: 2 envVariables: # Runtime env var exposed as RUNTIME_APP_ENV in the build # shell (Zerops auto-prefixes runtime vars with RUNTIME_). # The zerops.yaml buildCommands inject it as VITE_APP_ENV, # baking the environment name into the compiled JS bundle. APP_ENV: production # Zerops auto-scales RAM within these bounds. minFreeRamGB # reserves headroom for Nginx worker processes and traffic # spikes — without it the container gets exactly minRam and # risks OOM kills under load. verticalAutoscaling: minRam: 0.25 minFreeRamGB: 0.125 ``` --- ## Next Steps After deploying one of the environments and getting to know Zerops, you have two paths to choose from: 1. **Template Flow** — Clone our GitHub repositories and use the whole recipe as a template 2. **Integrate Flow** — If you already have an existing application on a similar stack, integrate the recipe setup with your application Select a flow: [Template Flow](https://app.zerops.io/recipes/react-router-static-hello-world.md?environment=small-production&guideFlow=template) or [Integrate Flow](https://app.zerops.io/recipes/react-router-static-hello-world.md?environment=small-production&guideFlow=integrate) Both flows are shown below: ## How to take over the Small Production environment ### 📦 Clone the template repositories Fork or clone the following repositories to your local machine or GitHub account: - [zerops-recipe-apps/react-router-static-hello-world-app](https://github.com/zerops-recipe-apps/react-router-static-hello-world-app) ### 1. Find your service name Many commands and configurations need the exact name of your service. You can find it in the Zerops Dashboard. - Open your project in the Zerops Dashboard. - In the project overview, find the service you want to manage. - Use this exact name whenever a command or pipeline configuration asks for ``. Zerops GUI: Locating the Service Name ### 2. Configure deployment pipeline Go to Service Settings > Pipelines & CI/CD Settings in the Zerops Dashboard and connect your repository. For production, use a trigger on new tags. This keeps deployments intentional and tied to a specific version. You can also add a regex filter, such as `^v[0-9]+\.[0-9]+\.[0-9]+$`, if you want to allow only semantic version tags. Zerops GUI: Triggers Alternatively, add `zcli push` to your existing CI/CD pipeline if you want full control over when deployments happen. Learn more about pipeline triggers: https://docs.zerops.io/features/pipeline ### 3. Deploy to production Create and push a new Git tag to deploy a specific version of your app: ```bash git tag -a v1.0.0 -m "Release version 1.0.0" git push origin v1.0.0 ``` > [!TIP] > Open the pipeline detail in the Zerops Dashboard to check the build progress and verify that all steps finish successfully. ### 4. Configure autoscaling Review the autoscaling settings for your runtime services and databases in Service Settings > Automatic Scaling Configuration in the Zerops Dashboard. Zerops GUI: Autoscaling configuration The most important settings are: ```yaml verticalAutoscaling: minRam: 1 minFreeRamGB: 0.5 minFreeRamPercent: 20 ``` > [!CAUTION] > Pay attention to `minFreeRamGB`. This value tells Zerops when to scale RAM vertically. Adjust it based on your app’s real memory needs. RAM scales up immediately, while CPU scales after two consecutive measurements below the threshold. > [!TIP] > Run a quick stress test with a tool like hey before real users arrive. This helps you see how your app behaves under load and tune the autoscaling settings. ### 5. Set up your domain To send real traffic to your app, configure public HTTP access in Service Settings > Public Access & Internal Ports in the Zerops Dashboard. Add your custom domain and point your DNS records to the Zerops IPs shown in the dashboard: Zerops GUI: Public access and custom domain ```text Type Name Content TTL A example.com Auto AAAA example.com Auto ``` For wildcard domains, add a CNAME record for SSL validation. Check the public access documentation: https://docs.zerops.io/features/access > [!TIP] > When changing DNS records for production, start with a low TTL value. Make sure SSL certificates are active before you disable the fallback Zerops subdomain. Once everything works, you can disable the Zerops subdomain so all traffic goes through your custom domain. --- ### 🎉 You are good to go! Your application is live in production and the core setup is complete. The following sections are optional. They cover extra production features such as log forwarding, backups, and diagnostic access. You can stop here and come back later when you need them. --- ### 6. Set up log forwarding (Optional) To send logs to an external service, go to Project Settings > Log Forwarding & Logs Overview in the Zerops Dashboard. You can forward logs to services like Better Stack, Papertrail, or your own self-hosted solution. Learn more about log forwarding: https://docs.zerops.io/references/logging ### 7. Configure database backups (Optional) Manage automated encrypted backups in Service Settings > Backups in the Zerops Dashboard. By default, backups run daily between 00:00 and 01:00 UTC. Before a major deployment, create a manual protected backup: ```bash zcli backup create --tags pre-deploy,protected ``` Read the backup documentation for more options: https://docs.zerops.io/features/backup ### 8. Set up diagnostic access (Optional) Use zCLI and VPN access when you need to inspect or maintain services directly. For runtime services: ```bash zcli vpn up ssh .zerops ``` For databases, connect through the VPN to reach the project’s private network, or set up secure direct IP access for your database admin tools. Check the VPN documentation: https://docs.zerops.io/references/cli/commands#vpn-up ## How to integrate app with Zerops ### 1. Adding `zerops.yaml` The main application configuration file you place at the root of your repository. It tells Zerops how to build, deploy, and run your application. ```yaml zerops: # Production setup: build static assets with Node.js, # serve with Nginx. Node.js is NOT present at runtime. - setup: prod build: # Build with Node.js (npm/npx); Nginx serves the output. # The build container compiles the React Router app into # static HTML/CSS/JS, then is deleted after deploy. base: nodejs@22 buildCommands: - npm ci # Inject VITE_APP_ENV at build time so the compiled JS # bundle carries the environment name. RUNTIME_APP_ENV # is the service's runtime env var, auto-prefixed by # Zerops and injected into the build shell environment. # Falls back to 'production' when unset. - VITE_APP_ENV=${RUNTIME_APP_ENV:-production} npm run build # Strip the 'build/client/' prefix so that the directory # contents become the Nginx document root directly # (build/client/index.html → /index.html, etc.). deployFiles: - build/client/~ cache: - node_modules run: # Nginx serves the compiled static assets automatically — # no start command needed; Zerops manages Nginx. base: static # Built-in SPA fallback: any path that does not match a # file is served index.html, so React Router's client-side # routing (useNavigate, , etc.) works out of the box. # Dev setup: deploy full source to a Node.js container for # SSH-based development. Zerops prepares the workspace; # the developer drives via SSH. - setup: dev build: base: nodejs@22 os: ubuntu buildCommands: # npm install (not npm ci) — dev environments may not # have a lock file yet; flexible installs are appropriate. - npm install # Deploy the entire working directory (source + deps) so # the developer has a ready workspace on SSH login. deployFiles: ./ cache: - node_modules run: # Node.js runtime — developer can run 'npm run dev' or # any React Router / Vite CLI command via SSH. base: nodejs@22 os: ubuntu # zsc noop keeps the container alive without starting a # server. The developer starts their own dev server via SSH. start: zsc noop --silent ``` ### 2. Key configuration — `react-router.config.ts` React Router v7 supports both SSR and SPA modes. For static deployment on Zerops, set `ssr: false` to enable SPA mode — no server rendering, output goes to `build/client/`. ```ts import type { Config } from "@react-router/dev/config"; export default { ssr: false, } satisfies Config; ``` ### 3. Build-time environment variables Static deployments have **no runtime process** — env vars must be injected at build time and baked into the compiled JS bundle. Zerops automatically exposes a service's runtime env vars to the build shell with a `RUNTIME_` prefix. Set `APP_ENV` on the service, and read `RUNTIME_APP_ENV` in your build command: ```yaml # In import.yaml — sets the service runtime env var envVariables: APP_ENV: production # In zerops.yaml buildCommands — injects it into the Vite build - VITE_APP_ENV=${RUNTIME_APP_ENV:-production} npm run build ``` In your app, read it as a compile-time constant: ```ts const env = import.meta.env.VITE_APP_ENV; ``` ### 🎯 What's next? **Deploy other environments** — Ready to scale? Deploy additional environments for different stages of your workflow: - [AI Agent](https://app.zerops.io/recipes/react-router-static-hello-world.md?environment=ai-agent) - [Remote (CDE)](https://app.zerops.io/recipes/react-router-static-hello-world.md?environment=remote-cde) - [Local](https://app.zerops.io/recipes/react-router-static-hello-world.md?environment=local) - [Stage](https://app.zerops.io/recipes/react-router-static-hello-world.md?environment=stage) - [Highly-available Production](https://app.zerops.io/recipes/react-router-static-hello-world.md?environment=highly-available-production) ## Knowledge Base ### Platform Reference - [Routing & Domains](https://docs.zerops.io/features/access) - [Scaling](https://docs.zerops.io/features/scaling) - [Environment Variables](https://docs.zerops.io/features/env-variables) - [CLI (zcli)](https://docs.zerops.io/references/cli) ### Service Type Reference **Static** - [Configuration](https://docs.zerops.io/static/overview#routing-configuration) - [SEO Setup](https://docs.zerops.io/static/overview#seo-with-prerender) - [Frameworks](https://docs.zerops.io/static/overview#framework-integration) --- ## Related Recipes - [React Router SSR Hello World](https://app.zerops.io/recipes/react-router-ssr-hello-world.md) - [React (Vite) Static Hello World](https://app.zerops.io/recipes/react-static-hello-world.md) - [Bun Hello World](https://app.zerops.io/recipes/bun-hello-world.md) - [Go Hello World](https://app.zerops.io/recipes/go-hello-world.md)