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

Docker install just links to datacats #2820

Closed
davidread opened this issue Jan 5, 2016 · 3 comments
Closed

Docker install just links to datacats #2820

davidread opened this issue Jan 5, 2016 · 3 comments
Assignees

Comments

@davidread
Copy link
Contributor

Rather than supply 'official' ckan docker images and install instructions, we should simply link to datacats one as it works and is maintained.

There are serious issues with ckan's documented docker install (e.g. #2255) due to the images being long unmaintained.

The conclusion of the discussion:
#2255 (comment)
and subsequent discussion at the tech team meeting was to simply guide people towards the datacats docker install.

@davidread davidread self-assigned this Jan 5, 2016
davidread pushed a commit that referenced this issue Jan 5, 2016
@davidread
Copy link
Contributor Author

@gamesbook said:

@davidread Thanks! Unfortunately, the datacats approach does not work either.

They've had a great track record looking after user issues. However progress has slowed recently - we'll see how your issue fares - datacats/datacats#372

@gamesbook
Copy link

@davidread It could be support is "down" over the year end period. I think this might be a Docker issue as that project is moving pretty fast.

davidread pushed a commit that referenced this issue Jan 7, 2016
… but leave the page to warn people if they get look via google.
@kmbn
Copy link
Contributor

kmbn commented Jan 22, 2019

We decided to close old issues that are not actively worked on so that we can focus our effort and attention on issues affecting the current versions of CKAN.

If this issue is still affecting the version of CKAN you're working with now, please feel free to comment or reopen the issue.

If you do reopen this issue, please update it with new details. One reason it might not have been resolved in the past is that it wasn't clear how a contributor could address the issue.

@kmbn kmbn closed this as completed Jan 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants