I've always liked to keep a current backup on my local storage. I haven't been able to find any facility for downloading the Cloud backups. Is there such a feature?
-
- 32 Posts
If such a feature would be implemented. I would really like to see it like an export feature as well.
So it would be just like a zip-file which you can download, and which contains two folders with root files and a db-export.
That way installing it on a new server is even easier instead of having to do this manually.
I haven't tried it yet myself, but I'm told that Vapor packages work on any Revo installation, not just the Cloud. I would still like to be able to keep a copy of the backup locally.
https://modxcloud.com/userguide/how-tos/import-sites-with-vapor.html
That's what I meant
I just linked to the Vapor page as a reference, as well as the location for downloading the Vapor script.
-
- 384 Posts
I like this idea too. Sometimes clients have hosting commitments and dependencies which prevent them from moving to the cloud.
...
-
- 202 Posts
I'd like this push button feature as well. But that means I'd have to go read again about moving a MODX install to a new server. Ick! The Cloud saves time, but makes me lazy. ;-)
-
- 338 Posts
I too would like to vote for a facility for downloading the Cloud backups for local storage.
Mike
-
- 572 Posts
I'd like to put my vote forward for this functionality too. I'm only using the Cloud for development so it would be incredibly useful to have a 'one-click' zip function for uploading to an external host.
www.9thwave.co.uk
WEB | DESIGN | PRINT
I have just been thinking about starting to develop on MODX cloud, but most of the time anticipate that I would have to move the site to another non-cloud server for production. Wondering if this is even possible, considering that it appears MODX cloud sites are different in certain aspects than MODX sites that are installed on another host. For instance, MODX cloud sites do not use an .htaccess file...
So would be interested to know what the process is for moving a site off the cloud and onto another server, and if there are inherently any more headaches involved than when building on a non-cloud dev server and then moving.
[ed. note: lucy last edited this post 11 years, 2 months ago.]