VITAS changed the topic of #spacedock to: Problems?: https://github.com/KSP-SpaceDock/SpaceDock/issues | Matrix/Riot Chat: https://im.52k.de +spacedock:52k.de Feel free to ask for help, we only bite a little bit! | If you want to help, please check https://github.com/KSP-SpaceDock/SpaceDock-Backend/issues/5 :) | <VITAS> inet users have the attentionspan of a squirrel...
Aarn[m] has joined #spacedock
<Aarn[m]> o/
VITAS[m] has joined #spacedock
<VITAS[m]> hi
Aarn[m] has quit [Quit: Idle timeout reached: 10800s]
DasSkelett[m] has joined #spacedock
<DasSkelett[m]> Beta is for some reason getting OOM-killed to hell
<DasSkelett[m]> Got the redirection problem solved, had to change the `cdn-domain` config.
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
<DasSkelett[m]> And the OOM problem was what that we start 8 gunicorn services each with 6 worker threads simultaneously. 515 MB are not enough for this.
<DasSkelett[m]> I changed it back again as I did before to only start one gunicorn instance.
<DasSkelett[m]> This change should be pushed to GitHub because the service files are git-tracked, but the problem is when this commit is merged to master, prod will run on less workers too.
VITAS[m] has joined #spacedock
<VITAS[m]> i think alpha and beta dont need as many workers
<VITAS[m]> but i can also increase memory if needed
<DasSkelett[m]> I'd prefer lowering the worker count, although I don't know how we should track this in git without accidentally trashing master/prod.
<DasSkelett[m]> I'm going to ping Darklight if he has an idea.
<VITAS[m]> yes do that and all changes are only made to alpha at this point
<VITAS[m]> would be nice to be able to define the worker count in the config
egg has joined #spacedock
oeuf has quit [Ping timeout: 190 seconds]
<DasSkelett[m]> I think I have an idea how we could solve this with the config.ini. I might use Alpha as a testing ground
<VITAS[m]> its all yours :)
<DasSkelett[m]> Got something working, but it feels a bit ugly. I'll try to get Dakrlight have a look and maybe beautify it a little.
<VITAS[m]> or he rips everything out and jsut calls it beautiful :>
<DasSkelett[m]> Fine with me
<VITAS[m]> not fine with me but i cant place demands if i want him to fix it
DasSkelett[m] has quit [Quit: Idle timeout reached: 10800s]
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
DasSkelett[m] has joined #spacedock
<DasSkelett[m]> I arranged it a bit differently, feels better now.
VITAS[m] has joined #spacedock
<VITAS[m]> top
<RockyTV> DasSkelett[m], regarding download/latest
<RockyTV> you don't need to check if the version name is latest
<RockyTV> just check in the route if versionid is latest and download the latest version even though the zip might be named latest
<RockyTV> sort by last updated
<DasSkelett[m]> Well yes, that's how /download will handle it. It will ask the database for mod releases where `ModVersion.id == mod.default_version_id`.
<DasSkelett[m]> However, while not technically necessary, we should still prevent people from uploading releases with the version number `latest`, because this release could never be downloaded in the future.
<DasSkelett[m]> Well yes, that's how /download would handle it. It will ask the database for mod releases where `ModVersion.id == mod.default_version_id`.
<DasSkelett[m]> However, while not technically necessary, we should still prevent people from uploading releases with the version number `latest`, because this release could never be downloaded in the future.
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]