Local to remote migration: Where is 'manager/includes/config.inc.php' ?

Hi Folks

I am still a newbie to MODX but I've made more than a start on Bob Ray's book.
I'm simply attempting to move my local site to a remote server,
but I'm coming up with conflicting (probably variations, more likely) tuts on the subject.
I've looked at the official MODX site doc and I would prefer something that sidesteps Terminal at this stage if at all possible.
With that in mind, I've been trying to follow the article linked from Bob's site (http://bobsguides.com) where the instruction talks about making a copy of "manager/includes/config.inc.php".
I realise this is an article from 2010, but firstly I don't have an 'includes' folder in the manager folder,
and secondly although I see a config file in the manager root it is named 'config.core.php'.
I'm kinda a little confused (and the truth be known, a little trepidatious) but is this the file being referred to?
I was also wondering if this article is still accurate or perhaps can anyone point me towards something that is (and, if possible, remaining as layman-like in its tone).
This is not a project-critical issue, but rather a learning one.

I'm using:
MODX 2.3.3
MAMP (latest (3.0.7.3))
PHP (5.5.18)
MySQL (5.5.38)
Chrome: Std and Canary (latest versions)
Mac OX (Lion-10.7.5)

Any guidance would be much appreciated
Kind Regards
Chris Ray

You need to make sure you're reading instructions for Revolution (2.x.x), not Evolution (1.x.x).

There are three config.core.php files, one in the site root, one in the connectors directory and one in the manager directory. All they do is point to where the core directory is, so you can move the core or change its name. The config.inc.php for Revo is in core/config/config.inc.php.

http://rtfm.modx.com/revolution/2.x/administering-your-site/moving-your-site-to-a-new-server

The easiest way to move a site is to install Vapor (you can install it from the MODX extras repository using the Manager installer), then run the vapor.php script from your browser. See https://modxcloud.com/userguide/using-modx-cloud/importing-and-exporting-modx-websites/import-sites-with-vapor.html#http starting with step 4 after installing Vapor using the Installer.

Then install a new copy of MODX on the new server. Log in to its Manager, and use the Installer to upload and install the package.zip file you created with Vapor.

You can use the install.php script to quickly and easily install the new copy of MODX. https://github.com/sottwell/installer

Hi Susan
Thanks very much for your reply.
Ok, I've tried following your suggestion to use Vapor.
And after much gnashing of teeth I've managed to clone my site remotely…
the only problem I have (I say only…) is that my 'Files' branch of the resources tree remains empty.
I've tried clearing all and sundry and there are no log errors.
Should I be manually amending any config files do you think.

Again, any help would be mightily appreciated
Kind Regards
Chris

Try manually deleting all files in the core/cache directory if you haven't done so already.

If that doesn't help, it could be a permission issue (easy to test by making yourself a sudo user), but more likely it's a misconfigured Media Source. Go to Media -> Media Sources. Right-click on the file system and select "Update Media Source". The correct Base Path is often empty, but you may have something there from the local install.

There's nothing in the config files that affects Media Sources specifically. If any of the settings were wrong, the Manager likely wouldn't work properly so it's very unlikely that the problem is in the config files.

Hi Bob

I started from scratch with the whole process just in case I was not following instructions to the letter.
The outcome is the same. The site is there, the assets are there (obviously), but the 'Files' branch remains empty.
I had already tried deleting the core/cache.
I've also tried down the road of your suggestion of a potentially misconfigured Media Source.
However when I right-click on the word 'Filesystem',
the only three options I get are 'Create Directory', 'Create File' and 'Upload Files'.
Might the absence of an 'Update Media Source' option be indicative of some other cause of the glitch?
Though that said, that particular option doesn't show in my local site either (which, as far as I'm aware, is functioning correctly).
I haven't as yet looked into the permissions as the possible cause.

Many Thanks
Chris

Many apologies…I was looking at the wrong 'Filesystem' label.
So anyway I followed the suggestion...

Right-click on the file system and select "Update Media Source". The correct Base Path is often empty, but you may have something there from the local install

I changed the 'basePath' to reflect my files location and lo and behold the 'Files' branch is re-populated.
However my index.php and .htaccess files are still missing…
Any ideas?

I appreciate the patience shown
Chris

In the root of your site you should see the index.php file.

assets (directory)
config.core.php
connectors (directory)
core (directory)
ht.access
index.php
manager (directory)

The manager's index.php file is in /manager/index.php

The ht.access file may not be there if it has been renamed to .htaccess I always make a copy of it rather than renaming it. If you don't see the .htaccess file, then rename the ht.access file to .htaccess.

Yes, I see that structure in my FTP client (Cyberduck)
but it's not showing in my remote MODX manager.

Ok, this is what I'm doing.
My root folder has the same name both locally and remotely.

Local site:
turning off Furl's
renaming .htaccess to ht.access
running Vapour

Remote site:
Installing brand new MODX instance (using install.php and selecting most recent Std Version)
Manager > Extras: uploading and installing the zipped file created by Vapor.
Renaming 'ht.access' to '.htaccess'
Turning Furl's back on.
Changing 'basePath' in 'Media Source: Filesystem' to '/assets'

(Manager/.htaccess contains only "RewriteEngine Off")

and this is what results (please see attachment).

Many apologies. I try, but this side of things really doesn't come easy to me.
Thanking You once more
[ed. note: geordiechris last edited this post 11 years, 3 months ago.]

That really should be

and it should be set for both path and URL.

If you set the base path to your "assets" directory, then you'll only see what's in the "assets" directory. If you leave it empty, then you will see everything in the installation.