Deployment

[catamounttechnology]

I have a fully functional site locally. Now I want to port it to a remote instance (DotNest) using the deployment feature. I haven't clear what steps I need to set in the Deployment plan, though. I tried all of them, but once I imported it in the destination, the result was broken (pages were wrong, not the same content, not the same layout, images missing...).
Aside from selecting components to export, there should be a "default" deployment features that simply replicates the source into the destination.

Also, if deploying changes to a destination can actually break the destination as occurred to me, there should be a safe rollback feature. The possibility to get a broken production site should be completely eliminated.

[hishamco]

Could you please try your case in the latest bits of OC, let us know the reproduce steps just to make sure it's not DotNest related thing

[catamounttechnology]

What does it mean "in the latest bits of OC"?

[hishamco]

Nightly build

[catamounttechnology]

When importing the package, using version 3.0.0-preview-18470

[hishamco]

Do you have a reproduced steps or minimal recipe that we can reproduce the issue

[Piedone]

As you observed under Lombiq/DotNest-Support#60, DotNest sites run OC 1.8.3. Please try exporting from such a site first.

There's this issue for an everything-export, but it's not that simple: Lombiq/Helpful-Extensions#105.