prep: Making way for the planned 'Dashboard' page and correcting Twitch bot scope, corrected.
This commit is contained in:
@@ -80,3 +80,20 @@ This is the process you will follow *every time* you want to add a new feature o
|
|||||||
* Fill it out, describe your changes, and submit it for review.
|
* Fill it out, describe your changes, and submit it for review.
|
||||||
|
|
||||||
A project lead will then review your code, and once approved, it will be merged into the `main` branch and deployed to the staging server for final testing.
|
A project lead will then review your code, and once approved, it will be merged into the `main` branch and deployed to the staging server for final testing.
|
||||||
|
|
||||||
|
|
||||||
|
🚀 Automatic Deployment (The Webhook)
|
||||||
|
|
||||||
|
We have set up an automated "hotline" that connects our code storage (Gitea) to our live server.
|
||||||
|
|
||||||
|
Here's how it works:
|
||||||
|
|
||||||
|
**Code is Saved**: A developer saves new code to our Gitea project.
|
||||||
|
|
||||||
|
**Gitea Calls the Server**: Gitea immediately "calls" a special, secret address on our server.
|
||||||
|
|
||||||
|
**Server Verifies the Call**: A "listener" program on the server answers and checks a secret password to make sure the call is genuinely from Gitea and not an impostor.
|
||||||
|
|
||||||
|
**Server Updates Itself**: Once verified, the listener automatically runs our deploy.sh script. This script fetches all the new code and restarts the application.
|
||||||
|
|
||||||
|
The result: The server is always running the latest version of the code, and no one has to log in to update it manually. It's completely automatic.
|
||||||
Reference in New Issue
Block a user