Wappler Version : 3.8.2 Operating System : mac Server Model: node Database Type: Hosting Type: Expected behavior When switching to an existing project, the local node server should be loaded only if that is the previously active target. Actual behavior Local node is started when active target …

How is your remote target defined? What are its settings?

[Screen Shot 2021-03-10 at 9.19.56 AM]

Why do you have multiple development targets? You really should have just one. We will be hard limiting that soon. As a lot of problems come when people develop on multiple targets and mixup the file synching and databases

I suppose that is fair, I can adjust. The reason is that for a lot of work, local is simply faster with file save changes. The remote is to see things as they would be in production, and for some features (like functionality based on different domain names) it is impossible on local.

Yes, I understand the development workflow. :slight_smile: Like I said, I can adjust. If you remove the option to have multiple development targets, I can setup a hosts file pointing to localhost and go that route to work on the multi-tenant custom domain work I have. There is also ngrok, etc. if…

[image] George: We will be hard limiting that soon. As a lot of problems come when people develop on multiple targets and mixup the file synching and databases Please don't do that. We often work on three targets - local dev, remote dev, and remote production. Local dev, as Ken pointed out…

This was resolved quite few Wappler updates ago, please check again and let us know if it is still a problem.

Wappler Community

Local server loaded on project switch, when active target is remote

Wappler General Bugs