Copy service in new remote server
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?
I do understand that changing a service's remote server once the service has been created is probably the wrong thing to do, as it gives the illusion that dokploy will take care of copying the whole app (including data and configuration, networks, volumes...) which is not true and might never happen.
However, it would be very useful to at least be able to, when copying a service, be able to select in which remote server we want to deploy it.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
No response
Will you send a PR to implement it?
No
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
The issue names no files, tests, or implementation entry point. Start by tracing the existing service-copy flow and how a service's remote server is selected; define the supported behavior and verify that copying can target a chosen remote server without implying data or configuration migration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100