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
This should be far less involved compared to migrating the modules from the Modules repo. We do have a separate coder/templates repo, but that was never made public. The Registry also pulls all its current templates from coder/coder as well. This setup means that we would be able to dump all current templates into the Hub's /coder user subdirectory and call it a day. It's probably worth asking which templates are the most up-to-date between coder/coder and coder/templates, but that would be the main source of ambiguity.
For better or worse, the templates don't currently have any tests in place, so that makes migrating them even easier.
The text was updated successfully, but these errors were encountered:
This is part of #530.
This should be far less involved compared to migrating the modules from the Modules repo. We do have a separate
coder/templates
repo, but that was never made public. The Registry also pulls all its current templates fromcoder/coder
as well. This setup means that we would be able to dump all current templates into the Hub's/coder
user subdirectory and call it a day. It's probably worth asking which templates are the most up-to-date betweencoder/coder
andcoder/templates
, but that would be the main source of ambiguity.For better or worse, the templates don't currently have any tests in place, so that makes migrating them even easier.
The text was updated successfully, but these errors were encountered: