Building and serving this works but adding the url in the dokploy templates "Base Url (optional)" doe not load templates. #30

New Issue

2025-11-22T20:29:29-06:00

GiteaMirror commented

2025-11-22 20:29:29 -06:00

Originally created by @transamericanlogisticsgroup on GitHub (Apr 14, 2025).

As the title says

Building and serving this works but adding the url in the dokploy templates "Base Url (optional)" doe not load templates.

When I type the usual https://templates.dokploy.com it loads them from there as it loads the default but not my self hosted version, which built fine and is being served just fine.

https://github.com/transamericanlogisticsgroup/dokploy-templates

any suggestions or you just have the field there but don't actually support custom template repositories??

Originally created by @transamericanlogisticsgroup on GitHub (Apr 14, 2025). As the title says Building and serving this works but adding the url in the dokploy templates "Base Url (optional)" doe not load templates. When I type the usual https://templates.dokploy.com it loads them from there as it loads the default but not my self hosted version, which built fine and is being served just fine. https://github.com/transamericanlogisticsgroup/dokploy-templates any suggestions or you just have the field there but don't actually support custom template repositories??

GiteaMirror commented

2025-11-22 20:29:29 -06:00

@michaeljnash commented on GitHub (Apr 14, 2025):

This would be a HUGE plus to be able to use our own hosted template repositories like that

@michaeljnash commented on GitHub (Apr 14, 2025): This would be a HUGE plus to be able to use our own hosted template repositories like that

GiteaMirror commented

2025-11-22 20:29:30 -06:00

@Siumauricio commented on GitHub (May 17, 2025):

You need to deploy this same project under your domain, the templates.dokploy.com domain belongs to this organisation, and it is obvious that if you make any changes to your fork those changes will not be reflected on the domain, so you need to do the configuration yourself,

I think I could make a guide to deploy it, it's not very difficult, it's a static vite react application.

@Siumauricio commented on GitHub (May 17, 2025): You need to deploy this same project under your domain, the templates.dokploy.com domain belongs to this organisation, and it is obvious that if you make any changes to your fork those changes will not be reflected on the domain, so you need to do the configuration yourself, I think I could make a guide to deploy it, it's not very difficult, it's a static vite react application.