We have moved over to slack, get your invite here (!): http://nf-core-invite.herokuapp.com and visit us https://nfcore.slack.com
Current situation is confusing
Thanks for addressing,
the "problem" with building it, is that it takes cpu, so locally is not always a possibility. and if you are working on "GDPR proof " cluster you dont have that option.
of course it is easy to get around this by having an open cluster somewhere, but that means another layer for someone to set up.
using singularity hub has been very problematic though, so not an easy solution as we originally thought
but yes, leaving it half-hanging as a solution is not ideal
@apeltzer - did we ever try building on travis? I guess it takes too long?
Could be a good thing for Travis / GitHub actions etc to automatically build the docker image, convert to singularity and then push to singularity hub perhaps.
As I think it's just the automatic builds on singularity hub which won't work.
we had that discussion before if i remember correctly
so i voted for an own registry
yes, I remember you said sth like that
which I agree in principle
:)
can discuss some ideas
I am more cautious of maintenance effort for self-hosted systems
thats what bothers me more
thanks for sharing Paolo!
BTW have you moved to slack ?
you can join using this link http://nf-core-invite.herokuapp.com
yup
-.-
