- Added a step to change the working directory to the unzip directory before executing PM2 commands for the nuxt4-demo application.
- This adjustment ensures that the application starts in the correct context, improving the reliability of the deployment process.
- Simplified the PM2 command handling in the .drone.yml file by removing unnecessary subshells and directly executing commands.
- This change enhances the clarity and efficiency of the deployment process for the nuxt4-demo application.
- Introduced a new debug step in the .drone.yml file to output the current PATH, user, and locations of Node.js and PM2.
- This addition aims to assist in troubleshooting deployment issues by providing visibility into the environment configuration during the CI/CD process.
- Set the HOME environment variable to /root to prevent path expansion issues for npm and bun.
- Replaced the previous PM2 command handling with direct commands to streamline the application lifecycle management for nuxt4-demo.
- Sourced nvm to ensure the correct Node.js version is used during deployment.
These changes enhance the reliability of the deployment process by improving environment configuration and command execution.
- Replaced direct PM2 commands with a function to check for PM2 or npx availability, enhancing error handling and flexibility.
- Updated the deployment script in .drone.yml to set the PATH correctly, ensuring that npm global binaries are accessible.
- This refactor streamlines the application lifecycle management for the nuxt4-demo, improving the robustness of the deployment process.
- Added new environment variables in .drone.yml for database and media management, improving security and flexibility during deployment.
- Included PM2 commands to manage the application lifecycle, ensuring proper start, stop, and delete operations for the nuxt4-demo application.
- Updated package.json to streamline the database copy command by removing unnecessary file operations.
These changes enhance the deployment process by improving environment management and application control.
- Updated the .drone.yml file to include GIT_SSH_HOST and GIT_SSH_PORT variables for improved SSH handling.
- Refined the SSH key scanning and command execution to ensure compatibility with the specified remote host and port.
- These changes enhance the reliability of the deployment process by ensuring proper SSH configuration and host verification.
- Changed the GIT_REMOTE URL in the .drone.yml file to use a new SSH format for improved access to the repository.
- This update ensures that the deployment process can connect to the correct remote repository, enhancing the reliability of the CI/CD pipeline.
These changes refine the deployment configuration, ensuring proper repository access during the deployment process.
- Changed the trigger branch from 'deploy' to 'test' in the .drone.yml configuration.
- This adjustment aligns the pipeline with the new testing strategy, ensuring that the CI/CD process is initiated on the correct branch.
These changes enhance the deployment workflow by refining the branch trigger for testing purposes.
- 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.
npmrun