Add manual GitHub Actions workflow for deploying to external server #12
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a new GitHub Actions workflow (deploy.yml) that enables on-demand deployments to an external development server.
🚀 Key Features:
git pullto sync the repodocker compose downto stop old containersdocker compose build --no-cacheto rebuild imagesdocker compose up -dto start the new version🔐 Required Secrets:
The following secrets must be configured in the repository settings:
SSH_HOST: Public IP or domain of the external serverSSH_USER: SSH username (e.g., ubuntu)SSH_PRIVATE_KEY: Private SSH key with access to the server (without passphrase)🛠 Usage:
This setup avoids triggering deployment on every push and provides controlled release for development testing.