fuck secrets I want my IP visible for debugging

This commit is contained in:
Kim 2023-10-30 08:46:26 +01:00
parent 8788ae4d50
commit ea66b50b04
1 changed files with 5 additions and 5 deletions

View File

@ -22,9 +22,9 @@ jobs:
npm --prefix ${{ gitea.workspace }}/typescript/frontend-marios2 install npm --prefix ${{ gitea.workspace }}/typescript/frontend-marios2 install
npm --prefix ${{ gitea.workspace }}/typescript/frontend-marios2 run build npm --prefix ${{ gitea.workspace }}/typescript/frontend-marios2 run build
- run: cd ${{ gitea.workspace }} - run: cd ${{ gitea.workspace }}
- run: scp -vo StrictHostKeyChecking=no -r ./csharp/App/Backend/bin/Release/net6.0/linux-x64/publish/ ubuntu@${{ secrets.STAGING_SSH_HOST }}:~/backend - run: scp -vo StrictHostKeyChecking=no -r ./csharp/App/Backend/bin/Release/net6.0/linux-x64/publish/ ubuntu@$91.92.154.141:~/backend
- run: scp -vo StrictHostKeyChecking=no -r ./typescript/frontend-marios2/* ubuntu@${{ secrets.STAGING_SSH_HOST }}:~/frontend/ - run: scp -vo StrictHostKeyChecking=no -r ./typescript/frontend-marios2/* ubuntu@$91.92.154.141:~/frontend/
- run: ssh -vo StrictHostKeyChecking=no staging 'sudo systemctl restart backend' - run: ssh -vo StrictHostKeyChecking=no ubuntu@91.92.154.141 'sudo systemctl restart backend'
- run: ssh -vo StrictHostKeyChecking=no staging 'sudo cp -rf ~/frontend/build/* /var/www/html/monitor.innov.energy/html/' - run: ssh -vo StrictHostKeyChecking=no ubuntu@91.92.154.141 'sudo cp -rf ~/frontend/build/* /var/www/html/monitor.innov.energy/html/'
- run: ssh -vo StrictHostKeyChecking=no staging 'sudo npm install -g serve' - run: ssh -vo StrictHostKeyChecking=no ubuntu@91.92.154.141 'sudo npm install -g serve'
- run: echo " This job's status is ${{ job.status }}." - run: echo " This job's status is ${{ job.status }}."