How to setup a MODX development site?

Yes, I got that far.
Vapor is installed on the live MODX website and I ran the vapor.php to make a package.
I then FTPed (the webhost has no SSH) the Vapor package to my local computer, but then there's no way of importing the Vapor package to the local test MODX website.

Unforuntately, Vapor is only for importing to MODX cloud users.

Yes, I'm now working on the Moving Your Site to a New Server, or to Root from Subfolder.

Yes, Vapor did its job, however now I can't import the package into the local MODX website.
Yes, I'm now trying http://rtfm.modx.com/revolution/2.x/administering-your-site/moving-your-site-to-a-new-server

Vapor works just as well importing the package into any new MODX installation, not just on the MODX Cloud. It's just a package, like any other package. You can either put it directly in the core/packages directory and use "Search Locally for Packages", or upload it directly from your computer using "Upload a Package", although it can be too big to upload for some system configurations. In any case, as long as you get it to your core/packages directory, you can just install it like any package.

Oh, well that's good to know.
I now have a Vapor package FTPed down from the live MODX website to my local computer Desktop.
I also FTPed the entire live MODX website's /public/www directory.

So, I'm now trying to move the Vapor package (and then the www directory) into some location where this bitnami MODX install has MODX running.
I guess I have to research now where bitnami has installed thid /core/packages directory, as a $ grep -r search didn't show where the directory is.

Also, would Transport or Siphon be better than Vapor, or should I stick with Vapor. (I'm just shopping around, so just hoping for some feedback now on these 3 tools).
The process seems to be closer to being finalised though, leaving 2 final jobs...editing the website's slide carousel which is surprisingly good at hiding where the code is...and setting up some type of git repository control for the editing of the MODX website.

I'm trying this https://github.com/modxcms/teleport Inject a Snapshot into a MODX Site to teleport the Vapor snapshot into whereever the location is of the bitnami MODX site, which I still don't know.

Put the Vapor package in your new core/packages directory. Then in the Package Management, click the arrow on the right side of the Download Packages button, and select Search Locally for Packages. It will find your package, and make it available in the Package Manager for installation.

If you don't know where you installed the Bitnami MODX stack, then I can't help you with that. It installs wherever you told it to install.

Vapor and Teleport are two different things, they don't work together.

Ok,
Teleport put to the side for now.

Vapor snapshot www.domain.com-150314.1558.23-2.3.3-pl, I'm trying to move into the local bitnami MODX website localhost/modx/manager, from my computer's Desktop.

Bitnami MODX website seems to have a different directory structure to the live MODX website's structure /public/www.

So,
Vapor snapshot www.domain.com-150314.1558.23-2.3.3-pl moved from Desktop to the local bitnami MODX website path /opt/modx-2.3.3pl-0/apps/modx/core/packages.

Browser > localhost/modx/manager/ > Dashboard GUI > I'm searching for installing this Vapor snapshot package, however the GUI shows nothing about packages, so I navigated here:
Browser > localhost/modx/manager/ > Dashboard GUI > Extras > Installer > Download Extras arrow > Search locally for Packages > MODX will now search your core/packages directory for any valid packages: Yes > No data to display.

The MODX dashboard doesn't find the Vapor snapshot www.domain.com-150314.1558.23-2.3.3-pl?
I suspect the Vapor snapshot is not a compatible package format. What is the appropriate MODX package format? [ed. note: eiger3970 last edited this post 11 years, 7 months ago.]

The package should be named something like domain.com-150125.1754.00-2.3.3-dev.transport.zip

After a successful run, you should find that file, as well as the corresponding unzipped directory, in the core/packages directory. The installer needs the transport.zip file.

Ok, thank you for clearing that up.
It seems the remote(live) MODX website Vapor creates a www.domain.com-150314.1558.23-2.3.3-pl file in /public/www/core/packages, but not a www.domain.com-150314.1558.23-2.3.3-pl.transport.zip file.

There are other files like core.transport.zip and more, but not the www.domain.com-150314.1558.23-2.3.3-pl.transport.zip?

I FTPed the file www.domain.com-150314.1558.23-2.3.3-pl to my local computer /opt/modx-2.3.3pl-0/apps/modx/core/packages and zipped and renamed the file to www.domain.com-150314.1558.23-2.3.3-pl.transport.zip.

The local MODX now uploaded the file, but installing caused error:


Looks like the two functions extractTo() and close() aren't built with the manual zip I made.
This was my zip command:

Guess I have to figure out how to fix that?
Perhaps the Vapor bit should be zipping into the /public/www/core/packages? [ed. note: eiger3970 last edited this post 11 years, 7 months ago.]

The other zip files in /public/www/core/packages are:
core.transport.zip
formit-2.2.0-pl.transport.zip
getfeed-1.0.0-pl.transport.zip
getresourcefield-1.0.3-pl.transport.zip
getresources-1.6.0-pl.transport.zip
getresources-1.6.1-pl.transport.zip
tinymce-4.3.3-pl.transport.zip
wayfinder-2.3.3-pl.transport.zip.