You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The gist of the idea is that you have a template that users can copy over and in that template is a symlink to some other shell script. When copying the template, we should make a symlink to that original shell script for use in the launchers.
The text was updated successfully, but these errors were encountered:
I have to admit here that I don't know if we should make a new symlink. It seems like we shouldn't because that original file isn't editable. So instead of making a symlink, we should probably copy the original file itself. That way they get the default shell script the admin wants to distribute, but since it's a real file, the user can edit it after the fact.
From discourse - https://discourse.openondemand.org/t/job-templates-allow-for-symlinkd-script-resource/3369
The gist of the idea is that you have a template that users can copy over and in that template is a symlink to some other shell script. When copying the template, we should make a symlink to that original shell script for use in the launchers.
The text was updated successfully, but these errors were encountered: