**Tags:** "Hello World" Examples · Astro # Astro Static Hello World A minimal [Astro](https://astro.build) application deployed as a static site on [Zerops](https://zerops.io) — compiled with Node.js at build time, served by Nginx at runtime, with ready-made configurations for every stage of the development lifecycle. ### Available Environments - [AI Agent](https://app.zerops.io/recipes/astro-static-hello-world.md?environment=ai-agent) - [Remote (CDE)](https://app.zerops.io/recipes/astro-static-hello-world.md?environment=remote-cde) - [Local](https://app.zerops.io/recipes/astro-static-hello-world.md?environment=local) - [Stage](https://app.zerops.io/recipes/astro-static-hello-world.md?environment=stage) - **Small Production** ← current - [Highly-available Production](https://app.zerops.io/recipes/astro-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/astro-static-hello-world-app](https://github.com/zerops-recipe-apps/astro-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 # astro-static-hello-world — Small Production environment # # Production-ready setup optimized for moderate throughput. # Two containers run at all times — requests are distributed by # the project balancer, and deploys are zero-downtime: new # containers start before old ones are removed from rotation. project: name: astro-static-hello-world-small-prod services: - hostname: app type: static zeropsSetup: prod # Zerops pulls source code and zerops.yaml from this public repo # and runs the build/deploy pipeline automatically on import. buildFromGit: https://github.com/zerops-recipe-apps/astro-static-hello-world-app enableSubdomainAccess: true # Always run at least 2 containers for availability and load # distribution. The project balancer routes traffic across them. minContainers: 2 maxContainers: 10 # Zerops autoscales RAM within these bounds. minFreeRamGB # reserves headroom for Nginx worker processes and traffic # spikes — without it, sustained load can cause OOM restarts. verticalAutoscaling: minRam: 0.25 minFreeRamGB: 0.125 envVariables: # APP_ENV is exposed as RUNTIME_APP_ENV in the build shell, # allowing the framework to bake the environment name into the # compiled output at build time. APP_ENV: production ``` --- ## 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/astro-static-hello-world.md?environment=small-production&guideFlow=template) or [Integrate Flow](https://app.zerops.io/recipes/astro-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/astro-static-hello-world-app](https://github.com/zerops-recipe-apps/astro-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 # The 'prod' setup builds optimized static assets for Nginx serving. # The 'dev' setup deploys full source code for live development. zerops: - setup: prod build: # Build with Node.js (npm/npx), serve with Nginx. # The build container compiles Astro source into static HTML/ # CSS/JS — Node.js is NOT present at runtime. base: nodejs@22 buildCommands: - npm ci # PUBLIC_APP_ENV is baked into the static output at build # time — there is no runtime process to read env vars later. # RUNTIME_APP_ENV is the 'APP_ENV' service env var, injected # by Zerops with a RUNTIME_ prefix into the build shell so # each environment gets its own label in the compiled output. - PUBLIC_APP_ENV=${RUNTIME_APP_ENV:-production} npm run build # Strip the 'dist/' prefix — contents become the Nginx root, # so dist/index.html is served as /index.html. deployFiles: - dist/~ cache: - node_modules run: # Nginx serves the compiled output — no Node.js at runtime. base: static # Zerops Static includes built-in SPA fallback: unmatched # routes serve /index.html, supporting client-side routing # without custom run.routing configuration. - setup: dev build: base: nodejs@22 os: ubuntu # npm install (not ci) — dev environment may lack a lock file # or a developer may have added packages without committing. buildCommands: - npm install # Deploy full source + node_modules so the developer can SSH # in and start the Astro dev server immediately. deployFiles: ./ cache: - node_modules run: # Node.js runtime so the developer has npm and the Astro CLI # available via SSH. The dev setup does NOT use 'static' here. base: nodejs@22 os: ubuntu # Keep the container alive without starting a server. # Developer SSHs in and runs 'npm run dev' to start Astro's # dev server with HMR on the port of their choice. start: zsc noop --silent ``` ### 2. Build-time environment variables Astro uses the `PUBLIC_*` prefix to expose variables to the build. In Zerops, set `APP_ENV` as a service environment variable — it becomes `RUNTIME_APP_ENV` in the build shell: ```astro --- const appEnv = import.meta.env.PUBLIC_APP_ENV ?? 'development'; --- ``` This is the fundamental pattern for static deployments: all configuration must be injected **at build time**, because there is no runtime process to read environment variables after the build. ### 🎯 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/astro-static-hello-world.md?environment=ai-agent) - [Remote (CDE)](https://app.zerops.io/recipes/astro-static-hello-world.md?environment=remote-cde) - [Local](https://app.zerops.io/recipes/astro-static-hello-world.md?environment=local) - [Stage](https://app.zerops.io/recipes/astro-static-hello-world.md?environment=stage) - [Highly-available Production](https://app.zerops.io/recipes/astro-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 - [Astro SSR Hello World](https://app.zerops.io/recipes/astro-ssr-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) - [Zerops showcase](https://app.zerops.io/recipes/zerops-showcase.md)