You have chosen to sponsor your bid up to a maximum amount of .
PLEASE ONLY BID IF YOU KNOW VARNISH / MAGENTO / MEMCACHE / NGINX INSIDE OUT AND CAN FIX STRAIGHT AWAY.
I wanted to test a VPS server (4GB) service called 'Deployment' from Rackspace.com. With this service 'Deployment' you choose how they setup the server for you, in my case it's Magento.
Look here http://www.rackspace.com/application-deployment/
So they setup the VPS for Magento (VPS Image) and install a default Magento 1.8. On there default Magento 1.8 everything works well, there default is set-up with memcache (local.xml) and Varnish.
This is my problem, via SSH I copy my current Magento 22.214.171.124 onto this Rackspace server and I get this error:
Error 503 Service Unavailable
Varnish cache server
1. So I need my Magento 126.96.36.199 working as it should on this VPS Magento Deployment server. I don't want to upgrade to 1.8 Magento yet. I want my Magento working with memcache and Varnish. The Varnish plugin is not installed also. So maybe this is the problem.
2. My current Magento 188.8.131.52 is working OK on an Apache web server just fine, so I think my .htaccess files will also need to be converted to work for Nginx.
This is how the Rackspace server is set-up.
DETAILS OF YOUR SETUP
This deployment was stood up using chef-solo. Once the deployment is up, chef will not run again, so it is safe to modify configurations.
A system user named 'magento' has been created. This user does not have a password set, so if you wish to use the account, a password will need to be set. This account is the system user for PHP-FPM, so deletion of this user will take eCommerce site down.
Nginx is used as the web server and listens on port 8080 and 443 to handle web traffic. The configuration for your site can be found in /etc/nginx/sites-enabled. There will be a default site configuration, and a seperate one for SSL traffic. Magento itself is installed in /var/www/vhosts. You will find a directory with the name of website you entered as a part of this deployment. The SSL certificates used are self signed and were generated when this deployment was created. You can replace the private key and certificate by overwriting the ones in /etc/nginx/ssl.
PHP-FPM is used to handle evaluation of all PHP-based pages. The configuration for this installation is in /etc/php5/fpm/pools/magento.conf. By default, PHP-FPM is running as the 'magento' user, listens on 127.0.0.1:9001.
Varnish is listening on port 80, and will handle all HTTP traffic. Varnish provides a caching layer to serve static content directly from memory. Anything that is not in cache will be passed onto Nginx. Varnish will greatly improve your site's performance, especially as traffic grows. We leverage the VCL provided by the Magento PageCache module. The configuration file is /etc/varnish/default.vcl.
Object and session caching are handled by Memcached. Memcache helps performance by storing data in memory for faster responses to clients. These caches help lessen the number of queries required to the database. There are two seperate instances of Memcached running to ensure session and object caching are handled seperately. The session cache is listening on 127.0.0.1:11211, and is set as a 512MB cache. The object cache is listening on 127.0.0.1:11212, and it is set as a 1.5GB cache. The configuration files are memcached_sessions.conf and memcached_backend.conf in /etc.
MySQL 5.5 is installed as the database backend. All configuration with Magento has been handled as a part of the setup. The MySQL root password is provided as a part of this deployment. If you lose or forget the password, it can also be found in /root/.my.cnf.
MySQL backups are performed nightly by Holland. Backups can be found in /var/lib/mysqlbackup.