<DasSkelett[m]>
Both times me and Darklight asked whether to automate database upgrades the answer was no. So yes, you have to execute point 4.
<DasSkelett[m]>
I think we should stick to Alembic. Ansible for db upgrades sounds... interesting.
bt_dang[m] has joined #spacedock
<bt_dang[m]>
can someone message me a good spacex mod pack
<DasSkelett[m]>
Search through SpaceDock or the forums, search for "SpaceX" in Add-On Releases.
<bt_dang[m]>
ok
<VITAS[m]>
yes i dont want to mess with deployment jobs allready done better by the framework itself
<VITAS[m]>
but deployment on the upepr levels could be done by ansible
<VITAS[m]>
it can configure proxmox, make adjustments or even have templates for ini files and set up the db server
<VITAS[m]>
all that is constantly tested and you can run ansible scripts (by design) as often as you want without destroying stuff (it simply will detect that theres nothing to be done)
<VITAS[m]>
the best of all is: you can share those scripts and run them from one central machine. ansible will ssh into each host and do its thing
<VITAS[m]>
the structure is host groups -> hosts and they are assigned to roles -> tasks
<VITAS[m]>
btw imagine what could be done if external triggers run ansible scripts
<VITAS[m]>
e.g. some cronjob
<DasSkelett[m]>
Well, what could be done, for example? What do you have in mind that we could and should automate?
<VITAS[m]>
im automating the deployment process on prod atm
<VITAS[m]>
it will generate the config.ini, stops services, checks it out of github, tests if its running afterwards and makes that host live
<VITAS[m]>
apart fromt hat: it can automate all tasks you do by hand on a shell
<VITAS[m]>
including deploying thw whole host and setting it up
<VITAS[m]>
my imidiate idea is to minimize errors and downtime by automating the prod deployment of new code versions
<VITAS[m]>
i also use ansible to req and deploy new letsencrypt certs
<VITAS[m]>
on all of my services
bt_dang[m] has quit [Quit: Client limit exceeded: 6]
<VITAS[m]>
currently looking trough config.ini
<VITAS[m]>
can i add more sections?
<VITAS[m]>
or does it need recoding stuff?
<VITAS[m]>
we have meta and dev
<VITAS[m]>
i would do ones for each group of settings
<VITAS[m]>
e.g. email
<VITAS[m]>
makes its better readable and would help me autosetting stuff
<VITAS[m]>
i guess renaming indiviudual keys is a lot of work (their naming could be streamlined too)
<VITAS[m]>
also: theres prod exception mails. DasSkelett HebaruSan Darklight are you interested in having those? i could set up a mailinglist or distribution for it
<VITAS[m]>
whats the difference between tls and smtp-tls in the config?
<VITAS[m]>
i rememebr having problems with getting mails out but the naming isnt clear to me
DasSkelett[m] has quit [Quit: Client limit exceeded: 6]
Darklight[m] has joined #spacedock
<Darklight[m]>
Probably have to source dive for that one and document it
<Darklight[m]>
Probably have to source dive for that one and document it
<Darklight[m]>
I am not at home but around-ish
<VITAS[m]>
hmm we could just run it and see if its working
<VITAS[m]>
from what i gather it ignores the sections and goes by key
<VITAS[m]>
i want to clean upo config.ini a bit and also make config.example match reality and vice versa
<VITAS[m]>
no rush
DasSkelett[m] has joined #spacedock
<DasSkelett[m]>
Not sure if we make use of the sections in any way, would also have to look at the source.
<DasSkelett[m]>
Currently taking a tour with my cycle, while you recover from your last one @VITAS :P
<VITAS[m]>
cool where and how far?
<VITAS[m]>
im done recovering
<VITAS[m]>
i only fear that the beach is crowded
<DasSkelett[m]>
Not as far as you, and with my parents. 30km yesterday, will be about the same today.
<VITAS[m]>
so overnight or went back home?
<VITAS[m]>
my mum said when i cycled 100km dont do that again
<VITAS[m]>
so i didnt :D
<DasSkelett[m]>
No, back home again. Each day in another direction.
<VITAS[m]>
dont forgett your hammok :P
<DasSkelett[m]>
Haha, so you did 150km ?
<VITAS[m]>
yes
<VITAS[m]>
she says that i shouldnt to so intense sessions all the sudden
<VITAS[m]>
she might be right that my body isnt used to it
<VITAS[m]>
im just bored when i stay at one location for to long
<DasSkelett[m]>
Yeah, she might have a point. But still better than doing nothing.
<VITAS[m]>
se has but now 80km are no problem anymore
<VITAS[m]>
i dont want to do more than 150 atm it took me all day and i nealry fell of the bike
<VITAS[m]>
more from mental exaustion than physical one
<VITAS[m]>
always concentrating
<Darklight[m]>
I think documentation on the option would be fine but shrug
<VITAS[m]>
feel free to edit the pad
<VITAS[m]>
i need sections to better address individual options
DasSkelett[m] has quit [Quit: Client limit exceeded: 6]
Darklight[m] has quit [Quit: Idle timeout reached: 10800s]
HebaruSan[m] has joined #spacedock
<HebaruSan[m]>
So what is the correct command to downgrade in alembic? My local `./start-server.sh` instance is stuck on my modpack fixes branch and I'd like to start something else.
<HebaruSan[m]>
Thanks!! That is going into a permanent text file
<DasSkelett[m]>
We could also include a downgrade command in `./spacedock`, but it would still need to be executed in the backend container, so doesn't change much in regards of complexity.
<HebaruSan[m]>
Yeah seems fine as is as long as there's no need to automate it in a real process
<HebaruSan[m]>
... aaand that worked, thanks again
<DasSkelett[m]>
Could still make sense though I think, to at least keep all the often used commands in one place.
<DasSkelett[m]>
Could still make sense though I think, to at least keep all the often used commands in one place.
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
HebaruSan[m] has quit [Quit: Client limit exceeded: 6]
DasSkelett[m] has quit [Quit: Client limit exceeded: 6]
<DasSkelett[m]>
The upgrade from master _should_ work fine, at least it does for me.
<Darklight[m]>
Hrmmm, it didn't spit out the error into the log, weird
<Darklight[m]>
Forgot the pip install requirements line
<Darklight[m]>
``ModuleNotFoundError: No module named 'packaging'`` It was this
<Darklight[m]>
Hrmm it's still not going in the log
<Darklight[m]>
Oh because it's probably printing to stder, I handle the alembic command in a special way because I am using the return code
<DasSkelett[m]>
Do you want to add the script to the repo and symlink to it? This way we could update it when for example we add a new route that could need testing.
<Darklight[m]>
It's a bit of a mess and also has password in it but I could probably fix that 😛
<Darklight[m]>
Ok I've made the alembic error show up at least, now to check if packaging is in requirements.txt...
<DasSkelett[m]>
It is 😉
<Darklight[m]>
Errrr
<Darklight[m]>
Oh I did it before switching branch, gotta read >.<
<Darklight[m]>
I'll change the script and remove my duplicate handling of alpha and beta, it's kinda "dumb" atm, and getting it to check PR's probably requires that I actually look at the data github sends me
<Darklight[m]>
Currently it just does a git fetch and checks alpha and beta if they have changed