Astro
Deploy your Astro Site to Azion
Deploy your Astro Site to Azion
You can deploy your Astro project on Azion, a platform for frontend developers to collaborate and deploy static (JAMstack) and SSR websites.
Prerequisites
To get started, you will need:
- An Azion account. If you don’t have one, you can sign up for a free account.
- Your app code stored in a GitHub repository.
- Azion CLI installed for faster project setup and deployment.
How to Deploy through Azion Console Dashboard
To start building, follow these steps:
How to Deploy a Static Site Using the Azion CLI
Install the Azion CLI:
- Download and install the Azion CLI for easier management and deployment.
:::caution The Azion CLI does not currently support native Windows environments. However, you can use it on Windows through the Windows Subsystem for Linux (WSL). Follow the WSL installation guide to set up a Linux environment on your Windows machine. :::
Authenticate the CLI:
- Run the following command to authenticate your CLI with your Azion account.
azion loginSet Up Your Application:
- Use the following commands to initialize and configure your project:
azion initBuild Your Astro Project:
- Run your build command locally:
azion buildDeploy Your Static Files:
- Deploy your static files using the Azion CLI:
azion deploy
This guide provides an overview of deploying static applications.
Enabling Local Development Using Azion CLI
For the preview to work, you must execute the following command:
azion dev
Once you've initialized the local development server, the application goes through the build process.
Building your Edge Application. This process may take a few minutes
Running build step command:
...
Then, when the build is complete, the access to the application is prompted:
[Azion Bundler] [Server] › ✔ success Function running on port http://localhost:3000
Troubleshooting
Node.js runtime APIs
A project using an NPM package fails to build with an error message such as [Error] Could not resolve "XXXX. The package "XXXX" wasn't found on the file system but is built into node.:
This means that a package or import you are using is not compatible with Azion’s runtime APIs.
If you are directly importing a Node.js runtime API, please refer to the Azion Node.js compatibility for further steps on how to resolve this.
If you are importing a package that imports a Node.js runtime API, check with the author of the package to see if they support the node:* import syntax. If they do not, you may need to find an alternative package.