It sounds like you need to copy the file /blog/index.php to /index.php and modify a line in the new copy you create: require(‘./wp-blog-header.php’); to require(‘./wordpress/wp-blog-header.php’); Here is a complete guide to moving WordPress into a separate folder: http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory
I always run queries in phpmyadmin http://www.phpmyadmin.net or adminer http://www.adminer.org/: UPDATE wp_options SET option_value = replace(option_value, ‘http://www.olddomain.com/’, ‘http://www.newdomain.com/’) WHERE option_name=”home” OR option_name=”siteurl”; UPDATE wp_posts SET guid = replace(guid, ‘http://www.olddomain.com/’,’http://www.newdomain.com/’); UPDATE wp_posts SET post_content = replace(post_content, ‘http://www.olddomain.com/’, ‘http://www.newdomain.com/’); Yes, some will say to never change the GUID, but changing the domain gives you no choice. Your … Read more
512MB should be fine, especially if you just started building your site. I’ve ran single WP installs on DigitalOcean droplets with 512MB of RAM without any issues in the past, also on NginX. Obviously, server stability also greatly depends on how NginX, MySQL etc have been configured (ie. not to consume too much memory and … Read more
$whitelist = array(‘127.0.0.1’); if(!in_array($_SERVER[‘REMOTE_ADDR’], $whitelist)){ // not valid } For more info on how it works. https://stackoverflow.com/questions/1634782/what-is-the-most-accurate-way-to-retrieve-a-users-correct-ip-address-in-php
In general – Yes. Make sure that the file and directory permissions are appropriate. In case the URL of your website changes, you would have to do a find/replace. Read more about it in the links below. Also, ‘update permalinks’ once you have access to the Dashboard. References: Codex: Moving WordPress Codex: Changing File Permissions … Read more
It’s not difficult. You need to transfer files to the new server. Create a blank database and keep it’s name, user_name (this user must have all privileges of this newly created database) and password. Edit config.php file on new server with the these new details. Read: WordPress Codex for transferring site
It could be anything: A slow and un-optimized MySQL server A theme not suited for big databases A faulty plugin combination … You can make sure that it’s not a plugin or theme issue by disabling all plugins and using a built in theme (I like Twenty Twelve). What else you can do to find … Read more
Yes, that should be enough if you don’t install poorly written plugins or themes. You should use PHP 5.5 and its built-in OPcache and a multisite setup for more sites. This will reduce load time and the resources you need for the sites.
To add to Peter’s comment, it is very much depending on the technology you use which in turn might depend on the software architecture. If you can create a condition in which you can serve cached pages 99% of the time (by using caching plugins or varnish in front of your site) then you will … Read more
It appears this was actually a firewall issue, not a permissions issue. Opening up a certain range of IP addresses on UFW via the Wordfence support article fixed the issue. The backupwordpress plugin seemed to work correctly once the DNS was resolved fully as well.