local config

[joergfunger]

@muh-hassani I looked into the code, not sure if we need to copy the templates to a directory. That would make work more complicated, since people would usually have their own git repo with all the relevant templates being there. Working with copies might give problems (because we actually have two files that are supposed to have the same content). Instead of collecting all templates in shared folder, I would rather have the option of adding a directory where templates could be stored. This way, people are more flexible either using a common shared structure, or use their local repo (not pyiron, but just the templates, e.g. in another git repo) and point to it.

[max-hassani]

@joergfunger, it might be not convenient, but the way pyiron works is that it has a central resources directory, in which pyiron looks for the templates directory. You can create a similar resource repository on git and have several submodules. If you want to create a large set of template script jobs, I suggest you to fork https://github.com/pyiron/pyiron-resources, and make your changes according to https://pyiron.readthedocs.io/en/latest/source/installation.html#advanced-configuration.

[joergfunger]

at least under linux we could use softlinks (not sure if pyiron works under windows anyway)?