DasSkelett[m] has quit [Quit: Idle timeout reached: 10800s]
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
HebaruSan[m] has quit [Quit: Idle timeout reached: 10800s]
Darklight[m] has quit [Quit: Idle timeout reached: 10800s]
VITAS[m] has joined #spacedock
<VITAS[m]>
so any important keys leaked?
Darklight[m] has joined #spacedock
<Darklight[m]>
I'm going to go with no because I didn't find it anywhere in authorized keys on any chrislinux or chrisserver account so I'm going to go with "no"
<Darklight[m]>
I'm going to go with no because I didn't find it anywhere in authorized keys on any chrislinux or chrisserver account
<Darklight[m]>
But it is kinda amusing, I checked spacedock because .bash_history would be exposed if apache was set up to serve from /var/www, but it isn't so you're good there
<VITAS[m]>
k
<Darklight[m]>
If there was a path to ~darklight/.ssh I would have rekeyed though
<Darklight[m]>
I've had my key for a loooooooong time now
<Darklight[m]>
I think this is my only 1024 length key though, the default. I create 4096 keys these days since I learned about the option. Maybe I should rekey shrug
<VITAS[m]>
so you should
<VITAS[m]>
4096 is minimum these days
<Darklight[m]>
Would is be more wise using ecdsa 521?
<Darklight[m]>
Oh it was a 2048
<Darklight[m]>
Eh I'll go ed25519 instead as it's not the NIST curve
<VITAS[m]>
good idea :)
<Darklight[m]>
Err, I just found a key I don't recognise on root@dmp3. But given the way it is named I assume that was one of your setup keys?
<VITAS[m]>
might be ansible
<VITAS[m]>
to run updates
<Darklight[m]>
spacedock also has it on the root account, it's proxmox I think
<Darklight[m]>
I was just checking I didn't have a key on root, I don't
<VITAS[m]>
ansible i told you
<VITAS[m]>
proxmox doesnt do ssh
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
Darklight[m] has quit [Quit: Idle timeout reached: 10800s]
HebaruSan[m] has joined #spacedock
<HebaruSan[m]>
<span class="d-mention d-user">DasSkelett</span>, good spot with `./generate_revision.sh`. Did you already know about that script, or was there some way to find it?
DasSkelett[m] has joined #spacedock
<DasSkelett[m]>
I already knew about it, I used it for all my previous PRs containing db schema migrations.
<HebaruSan[m]>
FAILED: No config file 'alembic.ini' found, or file has no '[alembic]' section
<HebaruSan[m]>
Should I get that from alpha/beta?
<DasSkelett[m]>
Oh yeah, alembic needs a running database. The script itself starts the docker database container.
<DasSkelett[m]>
You could do it on alpha (although you shouldn't use the script there because we don't run Docker, instead a manual `alembic revision --autogenerate -m \"$(date +%Y_%m_%d-%H_%M_%S)\" && chmod g+rw alembic/versions/*`
<DasSkelett[m]>
Or I just paste the one I already created.