I have live website running on MODx Revolution 2.1.3pl. Some days back I had to restore my entire site from backup. This messed up some file ownerships (for packages installed and images uploaded etc.) because in my server PHP runs as 'nobody' user which is different from my cPanel user.
Now I can't change much things on the server(like installing suPHP because its a shared server) and I don't know which all files are created by PHP, I decided to wipe the site clean and perform a clean install. My site has a large number of already published resources which is impossible to be posted into the new site individually.
Is there any way that I can transfer those resources to the new installation?
Why don't you create a mysql dump of your old site (with phpmyadmin or the like) and import this into a new database, which you use to run your new site from?
I've not tried it myself but provisioner seems to do (or at least claim to) what you need.
Related
I am a new web developer. I have been using Joomla with a 3rd party template, developing it on a local MAMP server. The template is sort of unstable and breaks easily. I would like to Backup my work on a daily basis.
I'm assuming all the files and the database need to be backed-up? Is there a best practice for this?
Thanks very much!
Using Akeeba Backup (https://www.akeebabackup.com/products/akeeba-backup.html) is indeed a good idea. You can schedule a command line task to run every day and create a backup of this site. To restore such a backup you can use Akeeba Kickstart (https://www.akeebabackup.com/products/akeeba-kickstart.html). Very easy, very comfortable.
But this only works if you don't break your Joomla! installation! Your question implies something like this. To do a manual backup you can simply zip the folder which contains your Joomla installation and create a database dump. You can do both every day using command line script.
Creating the dump: https://dev.mysql.com/doc/refman/5.7/en/mysqldump-sql-format.html
Using GIT might work as well. Instead of zipping your folder you simply commit it to your git repository. Don't forget to add the database dump to your repo as well.
https://techjoomla.com/developers-blogs/joomla-development/deploying-joomla-projects-using-git.html
http://joomlaablog.blogspot.de/2010/11/how-to-track-your-joomla-project-with.html
The best and easy method is to get it done through Akeeba Backup https://www.akeebabackup.com/download.html. Install this component at the backend. Run it and take a backup whenever you want. It takes backup of files and database both. You can even download and extract it to run it in another web server. To extract Akeeba you can use their software Akeeba Extract. This is all free.
Thank you everyone in advance... ^^;
My manager asked me to migrate the installed OpenAM (already used) to another machine (newly obtained).
I tried to migrate it by file level.
(.openamcfg folder, openam folder, tomcat whole folder, ...)
But, after file migration... first access to /openam, it showed initial page(wizard) again. (no using installed configurations)
So, I should do first step. (amadmin password setting, and so on...)
Hmm... Is there any solution for pre-installed OpenAm instance migration?
If No, I can tell her there's no migration way.
Migrating the files should be enough, however you must make sure that :
The .openamcfg folder is in Tomcat's home folder
The file inside the .openamcfg folder contains a valid path to the openam folder
The .openamcfg and openam folders can be read/write by the user who runs the Tomcat service
The webapp context (the part of the URL after the server's IP address, typically /openam) stays the same
Also, when you copy the files, you must first properly stop the Tomcat service, especially if you use OpenAM's embedded datastore.
I'd like to do some changes to a modx revo install through a staging subdomain, with a separate database. What's the easiest way of doing this? I've been battling with this for two days.
I'm trying a new install now and replacing content, components and database content
I end up moving/duplicating MODX sites between live and staging subdomains several times per week. Here's how I do it.
MySQL
Create a new blank staging database
Make sure you MySQL user can access the new databse
Export/Backup your live database
Import the backup to your new/staging database
Files
Download the matching version of MODX from http://modx.com/download/previous-releases/ because you'll need the /setup/ directory (hopefully you didn't leave that on your server previously).
Copy the entire content of the 'public_html or 'www' folder over to the staging subdomain folder. Don't forget the .htaccess file which is sometimes hidden.
Upload the setup folder to your staging location on your server just like it would be found in a clean MODX install.
Update the three config.core.php files from the top directory, /connectors/, and /manager/ to update the "MODX_CORE_PATH" to the correct directory for staging.
Update the 'core/config/config.inc.php' file. You'll need to update the database details and every instance of your directory structure to match the new staging location.
Run Setup
Run by going to staging.domain.com/setup
If you get ant errors during setup it probably means that you missed something that needed updating in one of the inc.php files.
It's actually very similar to moving the site from one server to another except duplicating to a subdomain on the same server instead. MODX has instructions for moving to a new server at http://rtfm.modx.com/revolution/2.x/administering-your-site/moving-your-site-to-a-new-server
There is another method to solve this problem.
Create new database & user for your sub site.
There is nice github repo. There you can find MODX install script which runs via cli. You'll get a new installed version of MODX in the end.
Install Vapor package from official repo to your old site. Then run vapor script from it via cli. It creates a new package with your whole site dump (You should check dependencies for xpdo objects in this script. For ex. you can copy all the stuff except users or anything else).
After all copy new package to core/packages at new site and install it.
Dump is ready :)
I've installed Bitnami Redmine 2.5.0 stack onto a fresh new Ubuntu 12.0.4 VM. I've imported the old Redmine 1.2.1 db into a new db and finished the job with rake db:migrate RAILS_ENV=production.
Now I can login into the upgraded Redmine with my old user account.
After copying the old svn repo into the new VM I couldn't see the repos. I've checked the project repo settings and found out that the old repo URL file:///home/svn was not the same on the new VM. The new VM's home path is home/user/ which changes the svn path into file:///home/user/svn. The URL box is grayed out when I try to edit the repo settings on the projects. My user on Redmine is an administrator.
Is there a practical way to globally change this path on Redmine (or SVN or Apache ???) or should I change the path settings on Linux? I want to change it globally because we have nearly 130 projects, so it isn't practical to edit the URLs one by one. I'm very inexperienced in Linux and mostly google my problems or ask my coworkers. So please guide me accordingly in simple terms.
I suggest moving your repositories to the same path as on the old machine, this will save you a lot of time and headache.
Redmine is configured to access the repository locally on filesystem (i.e. it does not access Apache HTTP Server); it's not clear how your Apache HTTP Server is configured in regards of the repository located in /home/user/svn. You may need to adjust Apache's configuration (httpd.conf) file to point to the changed repository path.
I was able to change 50+ repositories in one go by executing a simple SQL update query which replaced a part of the url field in the repositories table.
You may have to restart redmine for the changes to take effect (not sure about that).
I have 2 magento files in one server(linux) , one is live and other one is for testing. Both have different url. The testing magento is just setup by coping the live files and database. But I found out the testing magento will effect the live magento (for example I plugin the new template into testing magento , the live magento css and desgin will run also). Any idea about it?
Make sure that you have updated the URL in all of the config files AND the database. The easiest way to do this is to dump the database of the new site, find and replace the url of the original install with the new one then re-import it.
If you've been consistent with not hard coding links or images in CMS pages then the URL should only appear in these places:
http://www.magentocommerce.com/wiki/1_-_installation_and_configuration/update_site_url_in_core_config_data
You should use one magento on one server. Just create multiple stores in one. and redirect each store you what you want. www.example.com -> store 1; www.example1.com -> store 2 and so on. Magento works faster if you do that way. i have experience with multiple magento on one server. after more people start to use your store then server will start to lag or magento will start to work a lot slower.
this is happening because you have copied the database and files due to which in local.xml and in database table core_config there is information related to your live files, instead you should setup again the TESTING copy, just follow this steps.
take the backup of file local.xml from location /app/etc and after backup delete this file
Now after doing that just access the testing domain, now your setup for testing copy will start.
this will create new configuration information for testing copy