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...
HebaruSan[m] has quit [Quit: Idle timeout reached: 10800s]
Darklight[m] has joined #spacedock
* Darklight[m] uploaded an image: Screenshot_20200710-103455.png (90KB) < https://matrix.52k.de/_matrix/media/r0/download/52k.de/cqOdVGXPKEgcvREekVEgifMq >
<Darklight[m]> Wow
<Darklight[m]> KerbalStuff has a word replace bahaha, I didn't even link to domain
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
Darklight[m] has quit [Quit: Idle timeout reached: 10800s]
VITAS[m] has joined #spacedock
<VITAS[m]> it has?
<VITAS[m]> so if you type kerbalstuff it makes spacedock out of it?
<VITAS[m]> how odd
HebaruSan[m] has joined #spacedock
<HebaruSan[m]> No, it changes it to `*** malicious site we no longer use ***` because the domain got squatted
<VITAS[m]> spacedock.com never existed
<HebaruSan[m]> Right
<VITAS[m]> at least not in my posetion
<HebaruSan[m]> I know that
Darklight[m] has joined #spacedock
<Darklight[m]> I expected it to be unlinkable but you can't even talk about it without the domain
<Darklight[m]> Anyway, home, I'm off tomorrow too
HebaruSan[m] has quit [Quit: Idle timeout reached: 10800s]
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
VITAS[m] has joined #spacedock
<VITAS[m]> off in: having time to do have some quality time?
<Darklight[m]> My last day off was really busy, I feel like being lazy tomorrow, but I might poke spacedock things if it needs it
<VITAS[m]> pokeing your gf has priority :)
Darklight[m] has quit [Quit: Client limit exceeded: 6]
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
KineticSloth8StoneBlue[m has joined #spacedock
<KineticSloth8StoneBlue[m> so does checking the CKAN box, autogenerate a version file, or do I have to provide that?
DasSkelett[m] has joined #spacedock
<DasSkelett[m]> Unfortunately neither SpaceDock nor CKAN nor AVC are smart enough to autogenerate a version file for you. That one has to be created manually.
<DasSkelett[m]> It als has to be included in the zip for CKAN to be able to use it.
<KineticSloth8StoneBlue[m> Thanx. so, where would I find docs on creating one? is that AVC?
HebaruSan[m] has joined #spacedock
<KineticSloth8StoneBlue[m> Thanx 😉
<HebaruSan[m]> That's the original, <span class="d-mention d-user">Linuxgurugamer</span> added a bunch of new properties that you probably don't need to worry about
<KineticSloth8StoneBlue[m> ok.. kewl 😉
<DasSkelett[m]> The schema is also somewhat human-readable and more up to date: https://github.com/linuxgurugamer/KSPAddonVersionChecker/blob/master/KSP-AVC.schema.json
<HebaruSan[m]> _And_ <span class="d-mention d-user">DasSkelett</span> wrote a validator for the format
<KineticSloth8StoneBlue[m> awesome 😄
<KineticSloth8StoneBlue[m> also, if its an old inactive mod already listed on CKAN, and include a new version file, is the CKAN listing autoupdated from the NETKAN SD generates?
<KineticSloth8StoneBlue[m> or do I have to do anything?
<KineticSloth8StoneBlue[m> *edit:* ~~also, if its an old inactive mod already listed on CKAN, and include a new version file, is the CKAN listing autoupdated from the NETKAN SD generates?~~ -> also, if its an old inactive mod already listed on CKAN, and I include a new version file, is the CKAN listing autoupdated from the NETKAN SD generates?
<HebaruSan[m]> It can go either way, we'll take care of that when we review SD's pull request
<KineticSloth8StoneBlue[m> gotcha 😉
<DasSkelett[m]> Well do we actually get a pull request for already indexed mods?
<KineticSloth8StoneBlue[m> probably if its a new, seperate listing?
<DasSkelett[m]> Then yes
<KineticSloth8StoneBlue[m> if the SD listing was handed over, i would assume not?
<KineticSloth8StoneBlue[m> actually, i dont even remember if there is an original SD listing for this... 🤔
<KineticSloth8StoneBlue[m> hmm.. there *is*... mebbe I'll try to contact the original dev again, and ask if he can hand over the listing...if so, i imagine I just have to pester HebaruSan to look at my own, manual CKAN PR for it?
<DasSkelett[m]> Just checked the NetKAN-Infra code, I think we even get auto-PRs for SD mods that are already indexed. We don't have a check included for that one.
<HebaruSan[m]> If it's already on SpaceDock, and you get added to that listing, and it's already listed in CKAN, then when you upload a new version for it, it should automatically be added to CKAN
<KineticSloth8StoneBlue[m> oh!.. nice
<HebaruSan[m]> It would be just like any other new release for an indexed mod
<KineticSloth8StoneBlue[m> hmmm.. does SD do PR for each mod update, or is it CKAN itself that knows to look at a mod update for a new release, if its already CKAN listed?
<KineticSloth8StoneBlue[m> based on the .version file?
<HebaruSan[m]> A PR only happens once, at the very beginning when a mod is first indexed. After that, the bot just generates .ckan files automatically and adds them to the repo
<HebaruSan[m]> For mods listed on GitHub, the bot checks every 30 minutes. For mods listed on SpaceDock, there's an extra notification mechanism to make it near-instantaneous
<KineticSloth8StoneBlue[m> kewl.. not that it matters, but this will be both github & SD