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...
DasSkelett[m]1 has joined #spacedock
<DasSkelett[m]1> Well, found out the production game id for KSP:
<DasSkelett[m]1> Added "redo hardcoded stuff that shouldn't be hardcoded" to my TODO list...
<DasSkelett[m]1> Just doing what I can to help.
<DasSkelett[m]1> And this one is definitely something we should get fixed before KSP2 releases (although we have a lot of time until then now).
<DasSkelett[m]1> (Assuming there will be a place for CKAN and SpaceDock in KSP2)
<DasSkelett[m]1> We'd still have to remove all that hardcoded stuff (except you are planning to give KSP2 also an id of 3102...
<DasSkelett[m]1> We'd still have to remove all that hardcoded stuff (except you are planning to give KSP2 also an id of 3102...)
<DasSkelett[m]1> I like the Bootstrap 4 cards, they easily allow displaying more data on each card.
<DasSkelett[m]1> 💯 / 💯
<DasSkelett[m]1> Yes! All in for that name!
<DasSkelett[m]1> Frontend / template stuff is instant (Flask reloads it as soon as it detects a file change), backend needs longer (and a manual restart currently unfortunately)
<DasSkelett[m]1> I have no idea. I haven't been involved in that, and honestly don't really know how it's working. That's why I didn't take a look at it yet.
<DasSkelett[m]1> I have a password change feature mostly ready (I only want to add a link to the already existing password reset page if a user forgot his old password), should we include it in this alpha->beta batch? Or the next round?
<DasSkelett[m]1> In the "Your password has been changed" email, should I link to all the support channels, or only to the support mail for "if this wasn't you" ?
<DasSkelett[m]1> okay
Darklight[m] has joined #spacedock
<Darklight[m]> As in different db
<Darklight[m]> And just pull the gunicorn workers back on the main instance
<Darklight[m]> More that multigame support was a tad confusing and gave you a heap of problems I think
<Darklight[m]> I know ;)
<Darklight[m]> Oh I would keep he user accounts the same, good point
<Darklight[m]> I still think it would be wise to keep ksp2 a second instance
Darklight[m] has quit [Network ban]
DasSkelett[m]1 has quit [Network ban]
im52kde has quit [Network ban]
<RockyTV> I'm reviewing the pw change PR, and is it sending the new password via cleartext?
HebaruSan[m] has joined #spacedock
DasSkelett[m]1 has joined #spacedock
im52kde has joined #spacedock
HebaruSan[m] has quit [Network ban]
DasSkelett[m]1 has quit [Network ban]
im52kde has quit [Network ban]
HebaruSan[m] has joined #spacedock
DasSkelett[m]1 has joined #spacedock
<DasSkelett[m]1> Why delete it? Just archiving is fine.
<DasSkelett[m]1> There's always the possibility that we need it again.
<DasSkelett[m]1> Thanks for the link <span class="d-mention d-user">HebaruSan</span>.
<DasSkelett[m]1> As long as our password rules stay `5 <= password_length <= 256` I don't think it's worth adding a new dependency.
<DasSkelett[m]1> If we want to add more rules we can use it of course, but I don't want to do this without previous discussion with you all.
Darklight[m] has joined #spacedock
<Darklight[m]> Because this is the only python thing I've ever written I think and I don't want to acknowledge that I used python, because when someone talks about python I usually reply with
<Darklight[m]> hiss
<Darklight[m]> 😛
<Darklight[m]> (I'm kidding, but yeah it's all good)
Darklight[m] has quit [Network ban]
DasSkelett[m]1 has quit [Network ban]
HebaruSan[m] has quit [Network ban]
im52kde has joined #spacedock
HebaruSan[m] has joined #spacedock
HebaruSan[m] has quit [Network ban]
im52kde has quit [Network ban]