-
-
Notifications
You must be signed in to change notification settings - Fork 39
Best way to deploy different folders to different targets #158
Comments
When you make a package, you choose an array of files to include in that package. You can simply make two packages, one for folder A and one for folder B, with different targets. I’m assuming here you want to deploy on save (or change) – I presume it should work if you want to deploy manually as well (though I rarely use that feature, so I’m not a hundred per cent sure there):
|
Doesn't work for me. I tried it for deploying manually. If i deploy a file or folder (via shortcut, button or context menu) it always asks me to which target i want to deploy.
|
I’ve been deploying more files manually recently than I used to, and this is what I find as well. It seems when you manually deploy, it will always ask where to deploy to; the targets you set up in your settings.json are only used when the deploy action is invoked by an event listener. I don’t see anything on the wiki that looks like it might apply to manual invocation, so it looks like this may not be possible currently. |
Is there a way to deploy
folder a and subfolders to target a and
folder b and subfolders to target b
without being asked to which target i want to deploy?
The text was updated successfully, but these errors were encountered: