Feature Request for 360Deploy - Remote Dev/Testing File

[MMHinSEA]

In some situations, I would like to use the 360Deploy tool to send my dev file to the production server WITHOUT replacing the current production file. This remote 'dev' file on the production server would allow us to test solution performance on the client's server with live data without affecting the production solution. Then, if it were all OK, we'd run the migration normally, the way it works now.

The basic license appears to only permit a single database on one pair of servers (dev and prod). Would be great if there were an accommodation to push a 2nd copy of the dev file up to the prod server, - even if it had a 360Works demo file name - for performance testing.

Maybe our shop is the only one who would find this helpful--- but I suspect we're not alone in having to fine tune our dev work based on unexpected WAN gotchas. We always prefer to spot and correct those before subjecting end users to new features that are unexpectedly sluggish.

Edited February 20, 2019 by MMHinSEA

[joevmartin]

Hey MMHinSEA,

To accomplish this currently, I would duplicate my prod file on my prod server, and setup a deploy configuration that points to the duplicated file.

With a 360Deploy Express License, you can deploy a single dev solution to a single server, but as long as the dev file name does not change, the prod file name can change.  So you could set up two different configurations that use the same license key, the same dev file, and the same prod server, but different production files.

Thanks,

Joe Martin

[MMHinSEA]

OH! This is very interesting indeed. 

So do I have this straight? My Express license will permit this:

(dev server)                       (prod server)
DevFileA------------------------>ProdFileA
DevFileA------------------------>RemoteDevFileA

[joevmartin]

Yes that should work.  Before you run a deployment, be sure to duplicate your prod file on the prod server first, and according to this example, you would name it "RemoteDevFileA".  If 360Deploy does not find a prod file matching the expected prod file name, it will deploy an empty clone, which I don't think would be desired in your case.

Thanks,

Joe Martin