Local to remote moves simpler than documentation?

Is there any reason that, as in the documentation when relocating servers if there has been no change that the /manager folder need be migrated?

The way I see it, and the way I did it today was to:

1. dump db with drop statements.
2. transfer:
/assets/templates
/assets/files
/assets/plugins
/assets/modules
/assets/files
/assets/...anthing else that might be there not in the install
/manager/includes/config.inc.php /I question this on also since it is setup for the new db not the old
/ht.access or .htaccess
/index.php
/index.ajax.php

3. via db tool import sql file from dump.

4. change configs.
5. check site. done.

It seems crazy that we need to upload the manager folder (unless there are core hacks). It also seems crazy to move stuff that is already there from the install. TinyMCE has 1000s of files and makes moves painful.

Let me hear your POV.

Cheers,

jay

Hmmm, I think you are assuming that it is already installed on the target.  Copying the manager, etc. is because it isn’t there to begin with.

However, your way is also valid, and I dare say, simpler in most respects.  I also agree copying the config file would be pointless in your approach. Just add a step before everything else that says install a clean MODx distribution on the target. The only negative is your way would require uploading some things twice, once as part of the clean install and once from the install you are moving it from.

Oh absolutely with a fresh install on the remote server.

I haven’t transferred a site in a while and I didn’t realize how convoluted the documented procedure was but I’d like to revise both my workflow (and the instructions on the site and wiki).

I agree that the config.inc.php file is redundent. I realized it after I edited uploaded the localhost version and had to just change the original to match the remote server db settings. It was a small waste of time.

So really the process could be reduced to:

For moving site dev’d on local host to fresh install on remote server:
1. dump db with drop statements.
2. transfer:
/assets/templates
/assets/files
/assets/snippets
/assets/plugins
/assets/modules
/assets/files
/assets/...anthing else that might be there not in the install
/ht.access or .htaccess

3. via db tool import sql file from dump.

4. edit remote /manager/inlcudes/config.inc.php
5. check site. done.

On a related note: Do you think it would be hard to create a Site Move Packager that could back up the db, select assets folders and grab the .htaccess files output to zip or tar for upload, extract and install?

I usually upload the zip file and extract the MODx files on the remote server. Then I will transfer only the files that are related to the project, dump and import the database, then run the installer in update mode (careful not to overwrite any snippet hacks) to complete the setup. This works well with fresh installs, but transferring a complete site, modx and all, from local to remote may have other issues as well with the cache, htaccess, resource paths, and so on. I think that the documentation is directed towards this scenario where there are more chances for problems.

You *may* need to pay attention to the contents of the manager folder. Custom manager themes, for example, might be in there.

Just on this,

I’ve recently transferred a modx site from a local sever to a live host and have had no end of problems.

I resorted to doing fresh installs then transferring the relevant assets folders, and importing the db pretty much the same as smashingred says.

I do have one recurring problem, when I change my resource path and file manager paths from C:/wamp/www/mysite/ to the live site url, I lose the File manager tab in Configuration and have no files under Resources/File Manager.

Which is really weird as you wouldn’t think it would work in the first place with a local C:/ path

And of course once the File Manager tab is gone, I can’t go back and edit it in the Configuration settings.

The rest of the site still works ok

Obviously I’m doing something wrong somewhere, any tips would be appreciated.

3. via db tool import sql file from dump.

but first copy from system_settings the information in rb_base_dir and filemanager_path!
and paste back.

Okay, I don’t want people to think that this is a one size fits all set of instructions. I am not looking at wiping the existing instructions from the face of the earth. What I am aiming for is a quick set of instructions for simple move and then the full set for those who don’t meet the criteria.

In many cases people will have only modified elements of the some contents of the assets folder, the db and the htaccess file. In this case you will need to upload everything you’ve changed. If you don’t recall what you’ve changed, then upload the whole site.

That is a good point about the FileManager Path and the rb_base_dir which gets overwritten on sql install. Maybe a packager could omit this change.

Certainly if you are editing the /manager folder you should be uploading it.

If you have any more hints, tips or suggestions about your server move workflow, please let me know.

Remember that the doc. page you’re referring to is called: "How to move a site to a new server."

I think that your method should be on a different page called something like: "How to duplicate changes to your local MODx site on your remote site."

A good idea, but not for that original doc. page.

BobRay, I have read that page I don’t know how many times and I didn’t notice the fact that this was not on an already installed version of MODx on the server.

I’ll have to look at how to clear that up. I can’t for the life of me figure out why I’ve read it wrong so many times.

I still think the server move could be cleaned up. It is a regular action and could be simplified. I obviously overcomplicated it by doing an install over a new install. Why I am not sure?

Cheers all,

Jay