Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expand KSP-AVC support #286

Closed
pjf opened this issue Nov 8, 2014 · 3 comments
Closed

Expand KSP-AVC support #286

pjf opened this issue Nov 8, 2014 · 3 comments
Labels
Enhancement Netkan Issues affecting the netkan data ★☆☆

Comments

@pjf
Copy link
Member

pjf commented Nov 8, 2014

Right now we have very rudimentary support for AVC. It would be great if given a KSP-AVC URL we could use that for detecting new releases.

This would be a $kref, rather than a $vref field.

@pjf pjf added Netkan Issues affecting the netkan data Enhancement ★☆☆ labels Nov 8, 2014
@Ippo343
Copy link
Contributor

Ippo343 commented Dec 27, 2014

This issue was moved to KSP-CKAN/CKAN-netkan#5

@pjf
Copy link
Member Author

pjf commented May 31, 2015

re-opening after repo merge

@pjf pjf reopened this May 31, 2015
@HebaruSan
Copy link
Member

ExtraPlanetary Launchpads is an informative case study of how this could be useful. @taniwha hosts the downloads at taniwha.org rather than the usual hosting services. Currently this means that when a new version is released, the mod's netkan has to be updated manually (see KSP-CKAN/NetKAN#5978).

The downloads include a KSP-AVC file, which has a "URL" property pointing to the latest KSP-AVC file hosted on taniwha.org.

The KSP-AVC spec includes a "DOWNLOAD" property.

DOWNLOAD - Optional
Web address where the latest version can be downloaded.
This is only used from the remote version file.

If this property was populated in EPL's version file, and if CKAN was updated to support it, then that ought to be enough to get new versions into CKAN automatically:

  1. The NetKAN-bot downloads the currently indexed version
  2. The NetKAN-bot checks the included KSP-AVC file
  3. The NetKAN-bot checks the "URL" property of the included KSP-AVC file
  4. The NetKAN-bot downloads the remote KSP-AVC file
  5. The NetKAN-bot checks the "DOWNLOAD" property of the remote KSP-AVC file
  6. If it's different from the URL downloaded in step 1, then we have a new release; restart the process at step 1 using that URL

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Netkan Issues affecting the netkan data ★☆☆
Projects
None yet
Development

No branches or pull requests

4 participants