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

Consider cookiecutter for templates #20

Open
effigies opened this issue Jun 15, 2019 · 8 comments
Open

Consider cookiecutter for templates #20

effigies opened this issue Jun 15, 2019 · 8 comments

Comments

@effigies
Copy link
Member

Suggested by @jdkent on Slack ages ago.

https://cookiecutter.readthedocs.io/

@PeerHerholz
Copy link

Hi, what's the current status here?

@effigies
Copy link
Member Author

effigies commented Aug 7, 2019

You're looking at it. This is just a note. Right now there are some templates which are just pre-populated directories with at least one file in so that git will pay attention to them and setuptools will package them.

@PeerHerholz
Copy link

PeerHerholz commented Aug 8, 2019

Okay, check. What's your (and the everyone else's) opinion on this? How about a possible extension to include docker/singularity?

@satra
Copy link
Contributor

satra commented Aug 9, 2019

@PeerHerholz - what do you mean?

the intent of the recipe.yml file would be to use neurodocker to create a dockerfile/singularity file as part of the currently non-existent build option.

@PeerHerholz
Copy link

PeerHerholz commented Aug 9, 2019

I thought that, if the cookiecutter template will be used/adapted, we add could docker/singularity specific parts to that template, that is, install and build, as well as run instructions.

@satra
Copy link
Contributor

satra commented Aug 9, 2019

@PeerHerholz - i would leave this issue open till we have a full working example with all options. then we could convert it if cookiecutter seems like a nice fit. right now, there is not just the create a repo piece, but also the nfm piece.

@PeerHerholz
Copy link

@satra, ok gotcha. So the plan would be to wait till we have one or more full working examples, then evaluate which template fits best and then implement whatever that ends up being, right? I would browse the other issues to see if I can be of help somewhere else.

@satra
Copy link
Contributor

satra commented Aug 9, 2019

at this point the best help would be to do the build command and help stabilize recipe.yml - @djarecka was working on integrating testkraken with niflows.

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