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....oh a nut!
<RockyTV> there's a bunch of stuff on the current SpaceDock code that I don't even remember
aradapilot has quit [Ping timeout: 190 seconds]
oeuf has joined #spacedock
egg has quit [*.net *.split]
Havasushaun has joined #spacedock
Havasushaun has quit [Client Quit]
<RockyTV> did the autodeploy work?
AllisTauri[m] has joined #spacedock
<AllisTauri[m]> not yet, I'm struggling with it
<AllisTauri[m]> it happens that running a daemonized process from within a daemonized celery worker is not a trivial thing...
aradapilot has joined #spacedock
aradapilot has quit [Remote host closed the connection]
aradapilot has joined #spacedock
AllisTauri[m] has quit [Quit: Idle timeout reached: 10800s]
AllisTauri[m] has joined #spacedock
<AllisTauri[m]> And we're in business!
<AllisTauri[m]> The gitlab hook works. The only remaining thing is to set up the secret in the repo. But I can already trigger the update with a proper API request.
<AllisTauri[m]> * And we're in business!
<AllisTauri[m]> The github hook works. The only remaining thing is to set up the secret in the repo. But I can already trigger the update with a proper API request.
Shuudoushi has joined #spacedock
DasSkelett[m] has joined #spacedock
<DasSkelett[m]> Nice!
<RockyTV> noice
VITAS[m] has joined #spacedock
<VITAS[m]> no ice!
<DasSkelett[m]> What do you guys think about displaying the rendered api.md (which needs some work of course) under `/api` ?
<AllisTauri[m]> It's not that different from pointing to the file at github. If we want to make a step forward, it's better to invest into adoption of some framework that autogenerate API specs and documentation from docstrings; so that the source code became the source of documentation as well.
<AllisTauri[m]> There's a few specifically design for REST APIs
<AllisTauri[m]> Some even can find discrepancies between docs and code
<DasSkelett[m]> Well there would be a lot right now ^^
<AllisTauri[m]> Indeed. But it would be easier to write correct descriptions in doc strings right next to enter point code than to go back and forth between it and the .md, spending time on formatting
<DasSkelett[m]> I'm in for that, improves code doc on the same time.
<DasSkelett[m]> Can these frameworks (/ one of them) also output raw text readable in a console?
<DasSkelett[m]> Roughly something like http://wttr.in/:help, which you can just curl and read.
<AllisTauri[m]> I guess that is configurable
<AllisTauri[m]> This
<AllisTauri[m]> Or even this
<RockyTV> doxygen?
<AllisTauri[m]> Doxygen and Sphinx both provide static compilation of html documentation, suitable for documentation libraries, but much less so for REST API
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
DasSkelett[m] has quit [Quit: Idle timeout reached: 10800s]
AllisTauri[m] has quit [Quit: Idle timeout reached: 10800s]