Support importing blueprint/templates with domain initially inactive
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
When importing templates, sometimes there are domains that can both be public or only internal.
E.g. elastic search, as mentioned here:
Generally, only the Kibana UI needs to be exposed, but the elastic search domain should also be pre-configured (with the correctly exposed port), but kept inactive, in case the user wants to enable that to.
Describe the solution you'd like
Allow templates/blueprints to specify
[[config.domains]
active = false
The functionality is already supported by https://github.com/Dokploy/dokploy/pull/4697, released in v0.30.0.
Describe alternatives you've considered
- Don't add the domain config to the template
- Add it to the template and warn users to remove it in the compose
Will you send a PR to implement it?
Maybe, need help
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the template or blueprint import path and the existing domain activation handling described in Dokploy PR #4697. Update the import behavior so a template domain with active = false remains configured but inactive, then verify this with an imported template containing such a domain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100