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.

Sign up for GitHub

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

Jump to bottom

Allow ks2ckan/netkan to operate without a KSP install. #190

Closed
pjf opened this issue Oct 28, 2014 · 0 comments · Fixed by #192
Closed

Allow ks2ckan/netkan to operate without a KSP install. #190

pjf opened this issue Oct 28, 2014 · 0 comments · Fixed by #192
Assignees
@pjf
Labels
Enhancement Netkan Issues affecting the netkan data

Comments

@pjf
Copy link
Member

pjf commented Oct 28, 2014

Right now ks2ckan/netkan assumes that we have a KSP install, although it only really uses this for its cache. That's a terrible dependency to have, as it prevents it from running on a KSP-less machine in the cloud, which is what we want it to do.

Instead, ks2ckan/netkan should:

  • Use a user-supplied cache directory if supplied.
  • Have an option (maybe on by default?) to use an existing CKAN cache.

This will make it much easier for people to submit files to be indexed, as they can just have the ks2ckan/netkan utility and some JSON, which is a low barrier to entry.

(ks2ckan is going to be renamed netkan at some point, since it handles multiple end-points now, so apologies for the confusing naming.)
@pjf pjf added Enhancement Netkan Issues affecting the netkan data ★★☆ In progress We're still working on this and removed ★★☆ labels Oct 28, 2014
@pjf pjf self-assigned this Oct 28, 2014
pjf added a commit to pjf/CKAN that referenced this issue Oct 28, 2014
@pjf
netkan no longer requires a KSP install to operate.
cac92a6 
For a cache, we now use the following:

- What the user specifies, via `--cachedir=...`
- The local CKAN cache, if we can find it.
- The tempdir for the machine.

This means that the `netkan` utility can be used on machines without KSP or the CKAN client installed.

Closes KSP-CKAN#190.
@pjf pjf mentioned this issue Oct 28, 2014
Merged
@pjf pjf added Pull request and removed In progress We're still working on this labels Oct 28, 2014
RichardLake pushed a commit to RichardLake/CKAN that referenced this issue May 30, 2015
@pjf
netkan no longer requires a KSP install to operate.
89afc3d 
For a cache, we now use the following:

- What the user specifies, via `--cachedir=...`
- The local CKAN cache, if we can find it.
- The tempdir for the machine.

This means that the `netkan` utility can be used on machines without KSP or the CKAN client installed.

Closes KSP-CKAN#190.
RichardLake pushed a commit to RichardLake/CKAN that referenced this issue May 30, 2015
@pjf
netkan no longer requires a KSP install to operate.
5314891 
For a cache, we now use the following:

- What the user specifies, via `--cachedir=...`
- The local CKAN cache, if we can find it.
- The tempdir for the machine.

This means that the `netkan` utility can be used on machines without KSP or the CKAN client installed.

Closes KSP-CKAN#190.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pjf pjf

Labels
Enhancement Netkan Issues affecting the netkan data
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

netkan no longer requires a KSP install to operate. pjf/CKAN
2 participants
@pjf @AlexanderDzhoganov