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

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

Doesn't the vapor documentation say that vapor wont work on more complex MODX projects. It not being guaranteed after you've put that much work into it is sketchy to say the least.

Now there is "Teleport", but I have yet to figure out how to work it.

https://github.com/modxcms/teleport