Eishausener/fivem-resource-watcher
1
0
Fork 0
mirror of https://github.com/iLLeniumStudios/fivem-resource-watcher synced 2024-02-26 13:38:52 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update

Browse Source
This commit is contained in:
TheiLLeniumStudios
2023-02-07 11:43:35 +00:00
parent 684da378cc
commit b18f68ff42
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+2 -2
View File
@@ -10,8 +10,6 @@ fivem-resource-watcher GitHub Action allows you to restart resources automatical
- Resource filters (Coming Soon) - Resource filters (Coming Soon)
- Works both on Linux and Windows - Works both on Linux and Windows
Video Tutorial / Showcase: https://youtu.be/I_FqjKvcjxY
## Benefits ## Benefits
This allows you, as a server owner to have a Git Managed workflow for your server where you don't need to provide access to the VPS / Dedicated server or txAdmin console to your developers. They just push the changes to the git repository and they all get pulled and deployed automatically This allows you, as a server owner to have a Git Managed workflow for your server where you don't need to provide access to the VPS / Dedicated server or txAdmin console to your developers. They just push the changes to the git repository and they all get pulled and deployed automatically
@@ -27,6 +25,8 @@ This allows you, as a server owner to have a Git Managed workflow for your serve
## How to set up ## How to set up
Video Tutorial / Showcase: https://youtu.be/I_FqjKvcjxY
### Explanation ### Explanation
This action alone only does part of the automation. In order to actually make the restarts useful, we need to pull the remote changes first on the Server so that the changes are live after the restart. This doc will go through all the changes that you need to make in order to have a fully working pipeline. Your deployment workflow will look like the following after the pipeline is set up: This action alone only does part of the automation. In order to actually make the restarts useful, we need to pull the remote changes first on the Server so that the changes are live after the restart. This doc will go through all the changes that you need to make in order to have a fully working pipeline. Your deployment workflow will look like the following after the pipeline is set up: