Merge branch 'dev' into 'main'

Moving stuff on deploy

See merge request Firq/fgosite!7
This commit is contained in:
Firq 2023-07-27 21:02:30 +00:00
commit d167acce5c
2 changed files with 59 additions and 12 deletions

View file

@ -61,11 +61,11 @@ deploy-site:
- echo "Getting artifacts"
- ls public
- echo "Stopping screen session, cleaning"
- ssh $DEPLOY_USER@$DEPLOY_HOST "screen -X -S website-firq-npx kill; rm -r -f public/*;"
- ssh $DEPLOY_USER@$DEPLOY_HOST "screen -X -S website-firq-npx kill; rm -r -f firq_dev/public/*;"
- echo "Copying to proxmox machine"
- rsync -az --stats public $DEPLOY_USER@$DEPLOY_HOST:~/.
- rsync -az --stats public/* $DEPLOY_USER@$DEPLOY_HOST:~/firq_dev/public
- echo "Restarting screen session"
- ssh $DEPLOY_USER@$DEPLOY_HOST "find maintenance public -maxdepth 1 -printf '%p\n'; screen -S website-firq-npx -dm npx serve public/ -p 9000 -c serve.json"
- ssh $DEPLOY_USER@$DEPLOY_HOST "cd firq_dev; find maintenance public -maxdepth 1 -printf '%p\n'; screen -S website-firq-npx -dm npx serve public/ -p 9000 -c serve.json"
- echo "Website is up on https://firq.dev/"
deploy-testing:
@ -80,11 +80,11 @@ deploy-testing:
- echo "Getting artifacts"
- ls public
- echo "Stopping screen session, cleaning"
- ssh $DEPLOY_USER@$DEPLOY_HOST "screen -X -S staging-firq-npx kill; rm -r -f staging/*;"
- ssh $DEPLOY_USER@$DEPLOY_HOST "screen -X -S staging-firq-npx kill; rm -r -f firq_dev/staging/*;"
- echo "Copying to proxmox machine"
- rsync -az --stats public/* $DEPLOY_USER@$DEPLOY_HOST:~/staging
- rsync -az --stats public/* $DEPLOY_USER@$DEPLOY_HOST:~/firq_dev/staging
- echo "Restarting screen session"
- ssh $DEPLOY_USER@$DEPLOY_HOST "find staging -maxdepth 1 -printf '%p\n'; screen -S staging-firq-npx -dm npx serve staging/ -p 9100 -c serve.json"
- ssh $DEPLOY_USER@$DEPLOY_HOST "cd firq_dev; find staging -maxdepth 1 -printf '%p\n'; screen -S staging-firq-npx -dm npx serve staging/ -p 9100 -c serve.json"
- echo "Staging environment is up!"
unlighthouse:
@ -119,11 +119,11 @@ unlighthouse-publish:
- echo "Getting artifacts"
- ls unlighthouse-reports
- echo "Stopping screen session, cleaning"
- ssh $DEPLOY_USER@$DEPLOY_HOST "screen -X -S unlighthouse-results kill; rm -r -f unlighthouse/*;"
- ssh $DEPLOY_USER@$DEPLOY_HOST "screen -X -S unlighthouse-results kill; rm -r -f firq_dev/unlighthouse/*;"
- echo "Copying to proxmox machine"
- rsync -az --stats unlighthouse-reports/* $DEPLOY_USER@$DEPLOY_HOST:~/unlighthouse
- rsync -az --stats unlighthouse-reports/* $DEPLOY_USER@$DEPLOY_HOST:~/firq_dev/unlighthouse
- echo "Restarting screen session"
- ssh $DEPLOY_USER@$DEPLOY_HOST "find unlighthouse -maxdepth 1 -printf '%p\n'; screen -S unlighthouse -dm npx serve unlighthouse/ -p 9101 -c serve.json"
- ssh $DEPLOY_USER@$DEPLOY_HOST "cd firq_dev; find unlighthouse -maxdepth 1 -printf '%p\n'; screen -S unlighthouse -dm npx serve unlighthouse/ -p 9101 -c serve.json"
- echo "Unlighthouse results are up!"
success_notification:
@ -181,7 +181,7 @@ redeploy-site:
- echo "Stopping screen session"
- ssh $DEPLOY_USER@$DEPLOY_HOST "screen -X -S website-firq-npx kill" || true
- echo "Restarting screen session"
- ssh $DEPLOY_USER@$DEPLOY_HOST "screen -S website-firq-npx -dm npx serve public/ -p 9000 -c serve.json"
- ssh $DEPLOY_USER@$DEPLOY_HOST "screen -S website-firq-npx -dm npx serve firq_dev/public/ -p 9000 -c serve.json"
- echo "Website is up on https://firq.dev/"
redeploy-staging:
@ -196,7 +196,7 @@ redeploy-staging:
- echo "Stopping screen session"
- ssh $DEPLOY_USER@$DEPLOY_HOST "screen -X -S staging-firq-npx kill" || true
- echo "Restarting screen session"
- ssh $DEPLOY_USER@$DEPLOY_HOST "screen -S staging-firq-npx -dm npx serve staging/ -p 9100 -c serve.json"
- ssh $DEPLOY_USER@$DEPLOY_HOST "screen -S staging-firq-npx -dm npx serve firq_dev/staging/ -p 9100 -c serve.json"
- echo "Staging environment is up!"
redeploy-unlighthouse:
@ -211,7 +211,7 @@ redeploy-unlighthouse:
- echo "Stopping screen session"
- ssh $DEPLOY_USER@$DEPLOY_HOST "screen -X -S unlighthouse-results kill" || true
- echo "Restarting screen session"
- ssh $DEPLOY_USER@$DEPLOY_HOST "screen -S unlighthouse-results -dm npx serve unlighthouse/ -p 9101 -c serve.json"
- ssh $DEPLOY_USER@$DEPLOY_HOST "screen -S unlighthouse-results -dm npx serve firq_dev/unlighthouse/ -p 9101 -c serve.json"
- echo "Staging environment is up!"
maintenance-deploy:

View file

@ -0,0 +1,47 @@
---
layout: ../../layouts/blogPost.astro
title: 'How to: TA Cernunnos'
pubDate: 2023-07-14
description: 'A handful of observations from the cernunnos fight'
author: 'Requiem & Firq'
tags: ['fgo', 'lostbelt 6', 'cernunnos']
---
## Foreword
A big thank you to Requiem who came up with most of these facts while TAing the fluffy boy. I am just here to convert this into a more vieweable format, as well as adding some of my own observations to it.
## Curse stacks
On Turn 1, Cernunnos has 3 actions. Each attacking action has a 30% chance to get a new stack of curse. If Cernunnos gains a curse stack with an attack during the first two actions, Cernunnos stops and does not perform the third action.
The important thing is that he can't have more than 10 stacks of curse. Once Cernunnos reaches 10 stacks, 3 curse stacks are released. This means the minimum amount of curses he can have by Turn 4 is 9 stacks.
Ideally, you don't leave him at 10 stacks by the end of turn 3. Otherwise, Cernunnos won't release 3 stacks, as the corresponding skill cannot be cast.
If you successfully manage to dodge the random curses gained by attacks, you can go for 2 brave chains and 2 attacks to get the minimum amount of curses for turn 4. One of his skills let him eat his own curse, it happens rarely but can save your run.
### Curse gains
* At the end of each turn 1 stack of curse is gained
* The fight starts with Cernunnos getting 7 stacks of curse
* Turn 3 five stacks of curses are gained
* Turn 4 seven more curse stacks are gained
## Fight effects
Turn 2 Cernunnos starts with casting irremovable skill and np seal. This does not affect backline party members, so if you manage to cycle supports on the first attack turn you have their full set of skills to use.
## Actions
* Turn 1: Cernunnos has three actions if no curse stack is gained by attacking, otherwise two actions
* Turn 2: Only two actions, meaning Cernunnos can attack only twice.
* Turn 3: He again has only two actions
* Turn 4: Again, only two actions
## Skill Cooldowns
On the first break Cernunnos skill seals your servants. This means on turn 2 your servant won't lose 1 cooldown on that turn.
As an example:
Let's say I used Alteras third skill turn 1. She has to wait 5 turns to reuse it and on turn 3 Vitch gives her 2 times cooldown reduction.
Ideally you would be able to reuse her third skill on turn 4 but because she gets skill sealed she can't do it.