Static mode
Astro is a strong fit for static output. If the project does not depend on an SSR adapter or server runtime, publish it as a static site.
Astro static
Publish static output from Astro.
Astro static output usually lives in the `dist` directory. Appaloft can upload that directory from the browser or deploy it to your own server through the CLI.
Best for docs, marketing sites, content sites, and static landing pages
Before Cloud upload, confirm dist contains the entry file and asset folders
Astro projects that need an SSR adapter should use normal service deployment
Upload and replacement
Cloud quick upload is good for fast publishing and replacement; CLI is better when the site belongs on an existing server or automation path.
Post-deploy verification
After opening the URL, check pages, images, scripts, styles, RSS/sitemap, and 404 behavior.
Deployment flow
1
Build dist
Run the Astro build and confirm the dist directory exists.
2
Publish static folder
Choose dist in Appaloft, or deploy dist through the CLI.
3
Verify site
Check the homepage, content pages, assets, and error page.
Related topics
Keep following the same deploy path.
Appaloft SEO pages are organized around real deployment tasks. Each page should lead to the next useful step, not stand alone.
Static site publishing
Connect build output, browser upload, CLI deploy, and one-click buttons for static site publishing.
AI deployment
Let the agent identify project shape first, then choose the skill, CLI, static publishing, or Cloud console path.
GitHub deployment
Use GitHub Actions to connect repository events to Appaloft deployment while keeping explicit workflows.
Own server deployment
Tie the control plane, CLI, servers, rollback, and Cloud collaboration boundary into one self-hosting cluster.