Overview
This chapter provides detailed deployment steps to help you successfully publish your project to the Makers platform. Whether you are a beginner or an experienced developer, this guide covers all stages from environment configuration to actual deployment. By following these instructions, you will be able to efficiently manage project deployment and ensure its stability and availability in the production environment.
Note:
For any new deployment, Makers automatically creates a new and unique URL. You can use this URL to preview the latest changes to your project.
Deployment Lifecycle
The deployment lifecycle includes stages from development to production:
Local development: You can write code based on your own development habit. It is advisable to pull the latest env file every time before development to ensure use of the latest environment variable.
Submit and push: After task completion, you can push code to the connected Git repository's development branch. Each push will automatically trigger a deployment.
Preview: After a successful deployment, M assigns a corresponding domain to that deployment. You can generate an access link valid for three hours by clicking the "Preview" button.
Production: After completing the development cycle, you will eventually merge or commit changes to the production branch (typically main). Makers will then execute the build and deployment process again. Upon completion, a deployment domain is automatically assigned to your deployment, including any custom domains you have added.
Expired: When successful deployment records exceed three, Makers retains the build artifacts of the three most recent deployments in chronological order and marks other successful deployment records as expired. Concurrently, a 401 status code is returned for expired deployments. You can use the redeploy feature to create a new deployment with the same configuration, thereby restoring access to the expired deployment.
