modx gitify which files should be version controlled

#Modx gitify which files should be version controlled how to
#Modx gitify which files should be version controlled software
#Modx gitify which files should be version controlled password
#Modx gitify which files should be version controlled zip
#Modx gitify which files should be version controlled download

#Modx gitify which files should be version controlled password

Remember that mysqldump will prompt you for the password after you execute this command: when you type it (or paste it), you won't see anything in the terminal window. If you use mysqldump, be sure you use a username that has SELECT and LOCK permissions on all your MODX Revolution database tables – usually it's best to simply use the same username and password that are defined in your configuration file ( /core/config/). mysqldump -u username -p your_revo_db > /path/to/backups/my_revo_db.sql You can dump your MySQL database using a GUI tool such as phpMyAdmin, or you can run the command-line mysqldump utility. The following section is MySQL specific, however you should be able to do the same with similar commands for sqlsrv. Please note that MODX can run on multiple database drivers, currently MySQL and sqlsrv. The tar.gz file should retain the old server permissions - but those may not work on the new server. Depending on the security configuration of the service this may need to be 755 or 777. Some of the folders may need to be writable.

#Modx gitify which files should be version controlled software

FTP software will almost always set the proper ownership on an uploaded file. A simpler method may be to simply look at the ownership placed on the tar.gz file when it was uploaded to the server. You will have to check the server configuration to ascertain the correct settings, or simply ask the host for the details. Make sure that the files are owned and accessible to the web server. Sometimes the group and user ownership will change when moving from one host to another.

It's better to rename or move the containing directory instead. Again, be careful about moving files in bulk: you might inadvertently forget to copy those hidden files. Once you've extracted the files, you can move the whole directory into the correct place. tar.gz file using the following commands from a command line: gunzip modx_revo_ On a UNIX style system, you can unpackage a. The idea here is that if it explodes, it's easier to clean up the mess if it's contained in its own directory. Once you arrive on the other end, it's good to put the zipped file into its own directory before you extract it.

#Modx gitify which files should be version controlled zip

On a UNIX style system, you can create a compressed file using the tar command: tar -czf /path/to/backups/modx_revo_ /path/to/modx_doc_root/Ī good mnemonic for the '-czf' option is Create Zip File. Besides, transferring hundreds of files via FTP can take a long time because each file must often undergo some sort of authentication in other words copying over a hundred 1 megabyte files takes a lot longer than copying over a single 100 megabyte file. If you simply drag and drop files from one server to another using a GUI interface, chances are good that the GUI will omit hidden files such as the vital. Packaging up your Files ¶Īny time you pack up a site and move, it's best to package the files into 'boxes' – when you move out of your apartment, you put everything into boxes the same concept is true with files: package them. This process is typically fastest when performed in the server's file manager / via SSH, as opposed to FTP. Do this by deleting all the contents contained within the core/cache folder. The safest and surest method to clear the cache is to clear it manually.

#Modx gitify which files should be version controlled download

The first benefit of this is a smaller download / upload file. Clear your Sessions: Manage -> Logout All Users.

Log into the ((getting-started/glossary), then: Manage -> Clear Cache.Log into the Manager: Clear your Cache and Sessions ¶īefore doing anything else, it would be wise to empty all of the cached content.

It takes a big potential source of confusion out of the picture during the transition. Do the reverse as your last step after everything is working at the new location (rename ht.access to. htaccess to ht.access on your site before performing any of the steps below. It's not required, but it's a very good idea to turn off Friendly URLs (FURLS) in the Manager, if you have them on, and rename. Normally, the move is to a new server, but the steps here also apply if you move your site to a new folder on your current web server.

#Modx gitify which files should be version controlled how to

In Revolution, it's more or less the same process, but there are couple extra tidbits to watch out for due to Revolution's thorough caching mechanisms and how certain server-specific data is stored in its database.įollowing is the official documentation of how to move your site to a new location. MODX Revolution is a database-driven web application, so moving it to a new server involves the typical porting over of both the database and all the site's files.