Oolite Website Domain & Fixing the Expansions Manager

[timer]

Today I tried to transfer the storage of the main manifest file (catalog) to GitHub, but I could not (

Placing data in the only-static branch (CloudFlare Pages) leads to a forced request via the https protocol, which is not supported by the game manager.
Placing it in the only-media branch (GitHub Pages allow http protocol) leads to the inability to configure the addons subdomain to access GitHub Pages resources. CloudFlare's Free Plan does not allow such manipulations (

As a result, now I see only one solution - rename the media subdomain to addons and reconfigure getting site static from it. This will make possible to get the required address http://addons.oolite.space/api/1.0/overview which will allow access to the catalog placed in GitHub.

[hiran]

Today I tried to transfer the storage of the main manifest file (catalog) to GitHub, but I could not (

Placing data in the only-static branch (CloudFlare Pages) leads to a forced request via the https protocol, which is not supported by the game manager.
Placing it in the only-media branch (GitHub Pages allow http protocol) leads to the inability to configure the addons subdomain to access GitHub Pages resources. CloudFlare's Free Plan does not allow such manipulations (

As a result, now I see only one solution - rename the media subdomain to addons and reconfigure getting site static from it. This will make possible to get the required address http://addons.oolite.space/api/1.0/overview which will allow access to the catalog placed in GitHub.

Just for my curiosity: Why do we differentiate media and static? After all both of them are hosted in the same git repository, and both of them need to be pushed whenever an update happens. So what is different from having all of it in one branch and push that to Github pages, which then still can be referenced from Cloudflare?

[another_commander]

Today I tried to transfer the storage of the main manifest file (catalog) to GitHub, but I could not (

Placing data in the only-static branch (CloudFlare Pages) leads to a forced request via the https protocol, which is not supported by the game manager.

HTTPS support for the in-game manager is entirely dependent on whether the gnustep-base library has been compiled with TLS support or not. Both Windows and Linux ports support https just fine (well, Linux supported it fine until 1.90, don't know what is happening after that).

Make sure that your gnustep-base library has TLS support. Search for strings like gnutls_init in the binary to find out. If TLS is built into the library, you support https.

Also, did you use the correct download link to get the catalog file? You need the link to the raw contents, anything else will fail. I just tried it myself and downloaded the index successfully from github by putting the below in my .GNUstepDefaults:

Code: Select all

"oxz-index-url" = "https://raw.githubusercontent.com/OoliteProject/oolite-web/only-static/root/api/1.0/overview";

[timer]

Today I tried to transfer the storage of the main manifest file (catalog) to GitHub, but I could not (

Placing data in the only-static branch (CloudFlare Pages) leads to a forced request via the https protocol, which is not supported by the game manager.

HTTPS support for the in-game manager is entirely dependent on whether the gnustep-base library has been compiled with TLS support or not. Both Windows and Linux ports support https just fine (well, Linux supported it fine until 1.90, don't know what is happening after that).

Make sure that your gnustep-base library has TLS support. Search for strings like gnutls_init in the binary to find out. If TLS is built into the library, you support https.

Also, did you use the correct download link to get the catalog file? You need the link to the raw contents, anything else will fail. I just tried it myself and downloaded the index successfully from github by putting the below in my .GNUstepDefaults:

Code: Select all

"oxz-index-url" = "https://raw.githubusercontent.com/OoliteProject/oolite-web/only-static/root/api/1.0/overview";

oh... I just got this (when set https)

Code: Select all

11:58:10.400 [oxz.manager.error]: Error downloading file: A TLS fatal alert has been received.
most often due to the remote end not expecting TLS/SSL

[timer]

Just for my curiosity: Why do we differentiate media and static? After all both of them are hosted in the same git repository, and both of them need to be pushed whenever an update happens. So what is different from having all of it in one branch and push that to Github pages, which then still can be referenced from Cloudflare?

After the first deployment in CF, I split the repository - deploy more than a hundred megabytes after changing one line of the config is not pleasure... It must be remembered that we are deploying different parts of the project to different systems - media in GitHub Pages (we want free access and storage for media), code in CloudFlare Pages. Megabytes of media files does not apply to our code at all. Not possible set the same subdomain names for GH Pages and CF Pages.

The code should be separate - it takes less than a megabyte, and pictures and data are more than a hundred (and this volume will grow).

IMHO, it was necessary to create a two new separate repo for site (and move all code files there) and repo for media (images+news+articles etc.), then (for example) it would be possible to give rights on media repo other participants to upload beautiful screenshots,news,articles etc. that will automatically be activated on the site.

[hiran]

HTTPS support for the in-game manager is entirely dependent on whether the gnustep-base library has been compiled with TLS support or not. Both Windows and Linux ports support https just fine (well, Linux supported it fine until 1.90, don't know what is happening after that).

Make sure that your gnustep-base library has TLS support. Search for strings like gnutls_init in the binary to find out. If TLS is built into the library, you support https.

I think we should not move compilation dependencies onto a site admin. Let us rather check if the (pre)releases we create (and that is currently through Github Actions) build it sufficiently or not.

[Nite Owl]

Is it just me or is the website (http://oolite.space/) no longer updating the Latest Expansion Releases? This is referencing the list along the lower right hand side of the site. Fortunately there are alternatives to finding the latest and greatest new uploads if one knows how to find them but such knowledge is generally limited to those of us who have been around the Eight for a time. New players would tend to rely on the aforementioned list. Please advise.

[timer]

Is it just me or is the website (http://oolite.space/) no longer updating the Latest Expansion Releases?

Ohh :(
Plz see this post for details.
On OXP page info is actual.

[Nite Owl]

Thank You Timer for all of your efforts in keeping the Home Page going.

The OXP page is what has been used by me to keep up to date with the Latest Releases. As a bit of an Oolite veteran that maneuver was obvious to me but may not be so obvious to our newer members. Have every confidence that you will get it to all work out in the end.

[timer]

Good news!

Subdomain media renamed to addons - now http://addons.oolite.space/api/1.0/overview serving from GitHub! Not from my VPS.
Now my VPS doing only one job - check origin http://addons.oolite.org/api/1.0/overview and if it changed - upload it to GitHub.

And just now I updated site code - now Latest OXP News takes from oxp.json data file and we can see last 5 updated OXP on main page!

P.S.: I remind you that the manifest editor lives here: http://old.oolite.space/admin/

[hiran]

Good news!

Subdomain media renamed to addons - now http://addons.oolite.space/api/1.0/overview serving from GitHub! Not from my VPS.
Now my VPS doing only one job - check origin http://addons.oolite.org/api/1.0/overview and if it changed - upload it to GitHub.

Mind the difference:
https://addons.oolite.space/api/1.0/overview
https://addons.oolite.space/api/1.0/overview/

[phkb]

Subdomain media renamed to addons - now http://addons.oolite.space/api/1.0/overview serving from GitHub! Not from my VPS.
Now my VPS doing only one job - check origin http://addons.oolite.org/api/1.0/overview and if it changed - upload it to GitHub.

Is this the reason why the expansion manager was unable to download the OXP list until I removed the "ü" from one of the expansions?

Also, it would be good to get the link updated for the manifest editor on the OXP list page. Clicking on it currently says "Work in progress".

[timer]

Mind the difference:
https://addons.oolite.space/api/1.0/overview
https://addons.oolite.space/api/1.0/overview/

yep - it maybe a problem... url without slash - "give me this file", url with trailing slash is mean "show index file of directory"

What is the default option in the config file? If second - it is problem :(

[timer]

Is this the reason why the expansion manager was unable to download the OXP list until I removed the "ü" from one of the expansions?

I don't know what happened, but now the origin server is delivering a file with a corrupted UTF-8 character. Yesterday I checked it many times, downloading the file manually - one byte FC instead of two bytes C3 BC. Now I have installed post-processing that corrects the symbol.

Also, it would be good to get the link updated for the manifest editor on the OXP list page. Clicking on it currently says "Work in progress".

done

[phkb]

I don't know what happened, but now the origin server is delivering a file with a corrupted UTF-8 character. Yesterday I checked it many times, downloading the file manually - one byte FC instead of two bytes C3 BC. Now I have installed post-processing that corrects the symbol.

Well, I've put the "ü" character back into the OXP description where it was before. I guess we'll see what happens!