Overview
This chapter provides detailed deployment steps to help you publish your project smoothly to the Pages platform. Whether you are a beginner or an experienced developer, this guide covers various stages from environment configuration to actual deployment. Following these guidelines, you will be able to efficiently manage project deployment and ensure its stability and availability in a production environment.
Note:
For any new deployment, Pages automatically creates a new and unique URL, which you can use to preview the latest changes of the project.
Lifecycle of Deployment
The deployment lifecycle includes several stages from development to production:
Local development: You can write code based on your own development habit. It is recommended to pull the latest env file before each development to ensure use of the latest environment variables.
Submit and push: After task completion, you can push the code to the development branch of the connected Git repository. Every push will automatically trigger a deployment.
Preview: After successful deployment, Pages will assign an appropriate domain name to the deployment. You can generate an access link with a validity of three hours through the "Preview" button.
Production: After completion of the development cycle, you will eventually merge or submit changes to the production branch (typically main). Pages will re-execute the build and deployment process. Once completed, your deployment will be automatically assigned a deployment domain, including any custom domain names you added.
Expired: When the number of successful deployment records exceeds ten, Pages will retain the build artifacts of the first ten deployments in chronological order and mark other deployment records with a successful status as expired. Meanwhile, expired deployments will return a 401 status code. You can use the "Redeploy" feature to create a new deployment with the configuration of that deployment, thereby restoring access to the expired deployment.