- Introduced a new .drone.yml file to define the deployment pipeline, enhancing the CI/CD process.
- Updated the deployment script in package.json to reference the correct script for Gitea.
- Refined the deployment logic in the existing .drone.prod.yml and .drone.yml files to improve repository management and SSH handling.
- Enhanced environment variable management for better security and reliability during deployment.
These changes establish a more structured and efficient deployment pipeline, improving automation and security in the CI/CD workflow.
- Removed the existing Drone configuration from the root directory and added a new configuration file in the scripts directory to better organize deployment scripts.
- Updated the deployment command in package.json to copy the new Drone configuration file during the build process.
- Adjusted the trigger branch for the deployment pipeline to 'deploy-branch' to align with the new deployment strategy.
These changes improve the structure of the project and streamline the deployment process.
- Updated the deployment logic in the Drone configuration to streamline the handling of the repository directory.
- Enhanced the cloning and fetching process to ensure the correct branch is checked out while removing the existing directory if it does not contain a valid git repository.
These changes improve the reliability and efficiency of the CI/CD deployment process.
- Refactored the SSH command in the Drone configuration to use a variable for options, enhancing readability and maintainability.
- Updated the cloning and pulling logic to ensure the correct branch is used and added error handling for stopping and starting the PM2 process.
These changes streamline the deployment process and improve the robustness of the CI/CD pipeline.
- Updated the SSH command in the Drone configuration to include additional options for improved connection stability and security.
- Modified the cloning logic to use a shallow clone and added error handling for the SSH connection, ensuring a more robust deployment process.
These changes optimize the deployment workflow by enhancing SSH configurations and improving the handling of project cloning.
- Disabled the cloning step in the Drone configuration to streamline the deployment process.
- Set the HOME environment variable to /root to ensure proper SSH key handling during deployment.
These changes enhance the deployment workflow by optimizing the CI/CD pipeline configuration.
- Updated the SSH command in the Drone configuration to include host key verification options, improving security during the deployment process.
- Changed the branch for cloning and pulling from 'deploy-branch' to 'main' to align with the current deployment strategy.
These changes ensure a more secure and streamlined deployment workflow.
- Changed the trigger branch for the CI/CD pipeline in the Drone configuration to 'main' to align with the primary development workflow.
This update ensures that deployments are now triggered from the main branch, streamlining the deployment process.
- Introduced a new Drone CI/CD pipeline configuration for automated deployment on the 'deploy-branch'.
- Created a deployment script that builds the project, manages temporary directories, and handles git operations for pushing build artifacts.
- Updated the .env.example file to reflect new environment variable configurations for deployment.
- Enhanced .gitignore to include temporary distribution files.
These changes streamline the deployment process and improve project management for production releases.