Someone tell me the diference between using MODX Cloud and just using MAMP Pro

Could some tell me like 5 or 10 differences (if there are any) from using MODX Cloud vs just Using MAMP Pro to Develop locally. They seem the same to me.

Big Hangup I have on MODX Cloud are the same ones I have on MODX...
(Don't get me wrong MODX is by far the best CMS I have used, but setting up, updating, and migrating sites requires you to be a MySql Master. It's so simple as a Designer and front end developer to create dynamic sites for clients through MODX's amazing templating system, but doing anything past that requires development skills far beyond what is required for the initial build out.)

So could someone please tell me how it's different and how it would actually make my life easier to develop MODX sites. (not a challenge, genuinely want to know

-Jesse

P.S. I love MODX and hope it takes over the world

Well if your issues are upgrading and migrating then MODX cloud will do both of these in a single click with snapshots you can make a copy of your full site and start a new one or share with any other MODX cloud user and MODX updates are a one click thing on cloud.

Signup for a free lab account and play around with it you might like it.

Quote from: benmarte at Apr 19, 2013, 01:10 AM

Well if your issues are upgrading and migrating then MODX cloud will do both of these in a single click with snapshots you can make a copy of your full site and start a new one or share with any other MODX cloud user and MODX updates are a one click thing on cloud.

Signup for a free lab account and play around with it you might like it.

benmarte,

First - I like cms-tricks.com, cool info on there.
Second - I opened an account a played a little with it. It didn't seem as friendly to deploy your cloud snapshot into a live site as some would make it seem. When I say ease of use for the end user I mean something similar to http://ithemes.com/purchase/backupbuddy/ for wordpress. Click, upload, extract kind of deal.

About the only real advantage to using Cloud for dev is you can show it to your clients or anybody else (for help, for example), which you usually can't with a localhost installation. And if you have a team working on the site, of course.

As far as moving a dev site to a prod site, you can use Vapor on any installation. Make a Vapor package of your dev site, and use it to migrate to any other installation. It would be nice if we could figure out where the php binary is so that it could be done via SSH, but a newly developed site shouldn't be too big to work via HTTP.

Just follow the first half of the Vapor instructions on your dev site, then download the package from core/packages and put it in your new installation's core/packages and install via Package Manager like any other package.

https://modxcloud.com/userguide/how-tos/import-sites-with-vapor.html

Quote from: sottwell at Apr 19, 2013, 03:46 AM

About the only real advantage to using Cloud for dev is you can show it to your clients or anybody else (for help, for example), which you usually can't with a localhost installation. And if you have a team working on the site, of course.

As far as moving a dev site to a prod site, you can use Vapor on any installation. Make a Vapor package of your dev site, and use it to migrate to any other installation. It would be nice if we could figure out where the php binary is so that it could be done via SSH, but a newly developed site shouldn't be too big to work via HTTP.

Just follow the first half of the Vapor instructions on your dev site, then download the package from core/packages and put it in your new installation's core/packages and install via Package Manager like any other package.

https://modxcloud.com/userguide/how-tos/import-sites-with-vapor.html

You can't use vapor from the Cloud to a remote live server though can you?
The only way i've found to transfer from the Cloud to live is to export the sql using phpMyAdmin in the Cloud, install Modx on the live server and then import the sql.
[ed. note: 9thwave last edited this post 11 years ago.]

Yes, you can use Vapor on Cloud installations. I do it all the time. The only problem is not being able to access the PHP directly in SSH, so you're restricted to the HTML method of running the Vapor script.

Hi Sottwell...don't want to hijack the first post but just want to find out how you do this which may also be used to the person asking about Cloud benefits.
I tried it once by ftp'ing the zipped Vapor package (from Cloud) in the core/packages directory (on live server) but it just constantly seemed to time out and i was asked to add my login details over and over but without the zip fully unpacking. In the end I had to give up.
Is this the way you would do it?

That is the way I do it. I just put the zipped Vapor package (from the Cloud installation's core/packages) into my new site's core/packages, then install it from Package Manager like any other package. The only trouble I've ever had was if the Cloud site was too big to get packaged in the first place via HTTP.

Quote from: sottwell at Apr 19, 2013, 03:11 PM

That is the way I do it. I just put the zipped Vapor package (from the Cloud installation's core/packages) into my new site's core/packages, then install it from Package Manager like any other package. The only trouble I've ever had was if the Cloud site was too big to get packaged in the first place via HTTP.

OK thanks. So maybe the fact I get repeatedly asked for a username and password when i try to install via Package Management could be due to the server not allowing large zip files to be unpacked?
Maybe this is another thread.

You will get logged out, since the database is being replaced. I don't recall it being all that many times, though; I'll have to do it again and make notes.