timer wrote: ↑Thu Oct 05, 2023 8:06 am
hiran wrote: ↑Wed Oct 04, 2023 4:02 pm
Right now I believe that
- your update mechanism is sabotaged (I did it)
How exactly was my mechanism stopped? Changes in oolite-web repo (oo-acc-cf only read rights)?
Yes, that's how I did it.
timer wrote: ↑Thu Oct 05, 2023 8:06 am
hiran wrote: ↑Wed Oct 04, 2023 4:02 pm
I read the first post (from phkb) that the old site was down and immediately went to make fixes...
But I was a little hasty with my fixes - first I stopped the cron script on the VPS, then uploaded the index.html file, and ONLY THEN carefully read all posts. By the time UPD2 was written, I already understood how index.html is now generated (in general terms).
My fix would have been completely unnecessary if the index.html file in the repo had not been empty, but on the other hand - if it had not been empty - I probably would have studied it and realized that there was no need to change it.
So, we can probably say that I didn’t do anything wrong with my hasty actions?
I do not think your action had caused any damage. What happened:
The old webserver was reconfigured to only produce an error page (likely by the provider)
Your script downloaded the index, noticed a change and forwarded the data into the repository. It was working as designed, but from this moment the expansion index was corrupted.
I sabotaged your mechanism and created an alternative. This alternative seemed to work well for a few expansions.
Then I fed in the full list, but some situation made my code run havoc. It just created the new index file, failed to write content and reported success. As a consequence, the empty file got pushed into the repository.
So it was me who emptied the index.
I did not know you were working on the same problem in parallel.
timer wrote: ↑Thu Oct 05, 2023 8:06 am
hiran wrote: ↑Wed Oct 04, 2023 4:02 pm
If you have questions just ask.
If I understand correctly, your Java code scans (GitHub Action) all manifests in the archives and generates a new “general manifest”? How often does this happen? Archives can be very large - does GitHub really download all this to extract a small manifest?
Yes, the expansions are downloaded to the build server. This happens upon every push to the repo and once per month.
To speed up subsequent runs I configured a cache. Currently the expansions sum up to 5 GB. The cache is allowed to go up to 10 GB and last for two weeks.
timer wrote: ↑Thu Oct 05, 2023 8:06 am
And one more - we need to create synchronization for oxp.json, otherwise the site will have outdated information on the OXP page. For now I can try to configure it through my VPS.
The generator can not only emit plist, it can also write json. Where in the oolite-web do you want that file?
