Allow setting a default server when creating new services

What problem will this feature address?

I'm often frustrated when creating a new service in Dokploy because the server selection defaults to the "Dokploy" server. Once the service is created, it's not possible to change the server later. I sometimes forget to change it manually, which can lead to inefficiencies or running services on the wrong server.

Describe the solution you'd like

Allow users to set a default server for new services. Ideally, this could be:

• Configurable in the user settings or during initial setup.
• If no default is set, keep the current behavior of defaulting to the "Dokploy" server.

Describe alternatives you've considered

Manually selecting the correct server every time a new service is created. This works, but it's easy to forget and can cause mistakes.

Additional context

In my setup, I use two servers:

1. A smaller server where Dokploy itself is installed.
2. A larger, more powerful server where most services run.

Having the ability to set a default server would make creating new services faster, safer, and more efficient.

Will you send a PR to implement it?

No

Start by locating the new-service creation flow and the user settings or initial-setup entry points that could store a server preference. Trace how the current "Dokploy" server is selected, then define the fallback behavior and verify that newly created services use the configured default when one exists.