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

Install without swift_credentials.sh ? #206

Open
biocyberman opened this issue Mar 1, 2017 · 3 comments
Open

Install without swift_credentials.sh ? #206

biocyberman opened this issue Mar 1, 2017 · 3 comments

Comments

@biocyberman
Copy link

biocyberman commented Mar 1, 2017

This is based on version v2.4.1
Cpipe looks like an attractive tools for clinical gene panel sequencing so I want to try it out. But Cpipe is currently tied to swift_credentials.sh. This makes the program unusable to an outsider. So, I would like to suggest:

  1. Give description of what swift_credentials.sh is trying to achieve. If it is to give access to some prebuilt resources, then describe the resource and the process to generate them.
  2. Make swift_credentials.sh optional when running install.sh.
@biocyberman
Copy link
Author

It seems like version 2.2.0_public would do the job. My next question is how far version 2.2.0_public is behind the v2.4.1? And would it help if I try to merge/take the updates from v2.4.1 onto 2.2.0_public?

@multimeric
Copy link

Hi @biocyberman, glad to see your interest in Cpipe.

You are correct that Cpipe 2.4.0 and 2.4.1 are not installable without the credentials. Those releases are for internal use only at the moment, for licensing reasons.

As you've noticed, 2.2 does not have this issue, although I would strongly recommend release 2.3 instead. Both of these releases are notoriously difficult to install, but it is possible for anyone to use them.

However, we intend to have version 2.5 released by the end of March which will be usable by the public, with a much improved installer (and numerous other features). However this is not a confirmed deadline and it might be released later.

@biocyberman
Copy link
Author

biocyberman commented Mar 2, 2017

Look forward to version 2.5. And I am more interested in running this with a Docker container.

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

2 participants