For information and discussion about Oolite.
https://bb.oolite.space/
The easiest solution is probably to not put theNorby wrote:The download link contain a random part (I got images/f/f3 now), which we must insert into the manifest.plist within the oxz so an instant update is needed after every upload.
download_url at all in the copy of the manifest.plist which is inside the OXZ. By the time anyone can read that file, they no longer need the download URL.
My download counter extension is now active on the sandbox wiki.maik wrote:Instead, I'd rather take it as an opportunity to understand how to build my own extension.
http://sandbox.maikschulz.de/images/3/34/Q-Bomb_Detector_1.3.m.oxz. In order to prevent this, I would have to move the upload directory outside the web server's document root. I just don't see the point, it's only a download counter after all.[/size]Unless I'm missing something here, isn't this in fact how the 1.79 OXZ Manager itself accesses the OXZs? By using a direct reference to the file URL, as supplied by the manifest.plist? See, for example, the manifest.plist for the QBD:maik wrote:You can still bypass the counter update script by accessing the file URL directly, e.g.http://sandbox.maikschulz.de/images/3/34/Q-Bomb_Detector_1.3.m.oxz. In order to prevent this, I would have to move the upload directory outside the web server's document root. I just don't see the point, it's only a download counter after all.
Code: Select all
{
identifier = "oolite.oxp.Diziet.Q-Bomb-Detector";
version = "1.3";
title = "Q-Bomb-Detector";
required_oolite_version = "1.79";
description = "Detects the launch of a Quirium Cascade Mine and sounds a siren to alert the pilot.";
file_size = 168938;
category = "Equipment";
tags = ("quirium","bomb","mine","detector");
author = "Diziet Sma";
license = "CC-BY-NC-SA 3.0";
download_url = "http://wiki.alioth.net/images/e/ee/Q-Bomb_Detector_1.3.oxz"
information_url = "http://wiki.alioth.net/index.php/Quirium_Cascade_Mine_Detector";
}
The URL would need to be e.g.Diziet Sma wrote:Unless I'm missing something here, isn't this in fact how the 1.79 OXZ Manager itself accesses the OXZs? By using a direct reference to the file URL, as supplied by the manifest.plist? See, for example, the manifest.plist for the QBD:maik wrote:You can still bypass the counter update script by accessing the file URL directly, e.g.http://sandbox.maikschulz.de/images/3/34/Q-Bomb_Detector_1.3.m.oxz. In order to prevent this, I would have to move the upload directory outside the web server's document root. I just don't see the point, it's only a download counter after all.Code: Select all
{ identifier = "oolite.oxp.Diziet.Q-Bomb-Detector"; version = "1.3"; title = "Q-Bomb-Detector"; required_oolite_version = "1.79"; description = "Detects the launch of a Quirium Cascade Mine and sounds a siren to alert the pilot."; file_size = 168938; category = "Equipment"; tags = ("quirium","bomb","mine","detector"); author = "Diziet Sma"; license = "CC-BY-NC-SA 3.0"; download_url = "http://wiki.alioth.net/images/e/ee/Q-Bomb_Detector_1.3.oxz" information_url = "http://wiki.alioth.net/index.php/Quirium_Cascade_Mine_Detector"; }
http://sandbox.maikschulz.de/img_auth.php/3/34/Q-Bomb_Detector_1.3.m.oxz. You see it when you hover over the download link created using the [[Media:Q-Bomb_Detector_1.3.oxz]] download link on the wiki. The difference is in using the php script vs. bypassing php.Ok.. as I understand it, at the moment this php script is only installed on your sandbox Wiki, not the main or backup wikis, correct?maik wrote:The URL would need to be e.g.http://sandbox.maikschulz.de/img_auth.php/3/34/Q-Bomb_Detector_1.3.m.oxz. You see it when you hover over the download link created using the[[Media:Q-Bomb_Detector_1.3.oxz]]download link on the wiki. The difference is in using the php script vs. bypassing php.
ok, I've got a brand new OXZ to upload but am at a loss how to upload the file. I am clueless on PHP.maik wrote:My download counter extension is now active on the sandbox wiki.maik wrote:Instead, I'd rather take it as an opportunity to understand how to build my own extension.
When you upload a file there, it creates an entry for it in its database. Every[*] download is piped through a script that updates the counter. I created a new parser function {{#downloads: filename}} that shows the download count or "unknown" if the file is not in its downloads database. For an example on how to use it see the source code of my user page there.
Let me know if this makes sense and give it a test please. If all is well I will move it to the proper wiki.
[*] You can still bypass the counter update script by accessing the file URL directly, e.g.http://sandbox.maikschulz.de/images/3/34/Q-Bomb_Detector_1.3.m.oxz. In order to prevent this, I would have to move the upload directory outside the web server's document root. I just don't see the point, it's only a download counter after all.[/size]