How to use a starter site and use that to get a head start on new MODx sites.

Install the Vapor scripts in your Cloud installation, run it, get the package it creates from core/packages, put the package in your other installation's core/packages, and install it from Package Manager as usual.

Quote from: eighthday at Mar 26, 2013, 05:08 AM

just run vapor on your modx cloud account and then you can install the vapor transport package in a fresh modx install using the package manager.

I owe you a pint!

Yes... I've had great results with many installs, yet not so on others. And, we do it just like you describe (we even call it our base account).

When it works, it works great. When it doesn't, my monitor goes flying out the window again.

Then, I wonder if my problem here has to do with something I've moaned about in this thread:

https://forums.modx.com/thread/83096/permissions-and-file-ownerships---can-something-in-modx-cause-intermittent-changes-of-these-things-on-server#dis-post-458443

We still haven't installed SuExec or SuPhP on our servers so I cannot give a consumer report on whether that is the source of the problem.

On some problem installs, I've tried re-running setup but that just seems to mess things up completely.

Quote from: rx2 at Mar 25, 2013, 11:57 PM

We do as you did, export a database from what we refer to as our base install and import it into the new site's database. In addition, we upload a copy of MODX from our base install to the new site's server, changing the config files of course. Finally, we reinstall the same version of MODX as an update. Never had any issues.

Considering using the package method and importing Permissions policies and Forms customization rules independently but haven't gotten around to that approach yet.

BTW: Feeling stupid here, but what is Vapor? Is that a MODx Cloud-specific thing? [ed. note: waizen last edited this post 13 years, 6 months ago.]

Quote from: sottwell at Mar 26, 2013, 05:09 AM

Install the Vapor scripts in your Cloud installation, run it, get the package it creates from core/packages, put the package in your other installation's core/packages, and install it from Package Manager as usual.

So, with a Cloud account, I can have a 'base account' set up, take a snapshot of it and then install it on a totally different server, with a standalone MODx install?

You will need to upload the Vapor script to your Cloud installation and run it from there. https://modxcloud.com/userguide/how-tos/import-sites-with-vapor.html