rabeweb/website
9
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix rsync paths in workflow for deployment to Development and Production environments.
All checks were successful
Build and Deploy Hugo Site / build_and_deploy (push) Successful in 1m42s
Details

Browse source
This commit is contained in:
Andreas Hnida 2024-04-17 23:55:59 +02:00
commit 46286d4a81
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
.gitea/workflows/pipeline-test.yaml
View file

@ -70,13 +70,13 @@ jobs:
- name: Deploy to Development - name: Deploy to Development
if: env.myEnv_env == 'development' if: env.myEnv_env == 'development'
run: | run: |
rsync -avz --delete /public/ verua.info@verua.info:/preview.verua.info/ rsync -avz --delete ./public/ verua.info@verua.info:/preview.verua.info/
env: env:
RSYNC_RSH: 'ssh -p 2121 -o StrictHostKeyChecking=no' RSYNC_RSH: 'ssh -p 2121 -o StrictHostKeyChecking=no'
- name: Deploy to Production - name: Deploy to Production
if: env.myEnv_env == 'production' if: env.myEnv_env == 'production'
run: | run: |
rsync -avz --delete /public/ verua.info@verua.info:/httpdocs/ rsync -avz --delete ./public/ verua.info@verua.info:/httpdocs/
env: env:
RSYNC_RSH: 'ssh -p 2121 -o StrictHostKeyChecking=no' RSYNC_RSH: 'ssh -p 2121 -o StrictHostKeyChecking=no'