The version available here http://community.opscode.com/cookbooks/magento does not contain latest fixes in the github. Can you release a new version, please?

Summary:

• Moved MySQL setup to it's own recipe. Setup is designed to allow for adding other backends (ie Percona)
• Moved nginx to recipe, added apache2 recipe. Defining the web server to setup is controlled by the attribute node[:magento][:webserver], default is nginx
• Added attributes for defining the site name, naming your self-signed cert, added a database attribute (mysql is the only currently valid option)
• Added library to handle generation of self signed certs for use with web server
• Added test suite to .kitchen.yml to test with apache2

This gives the ability for a user to specify different timeouts for send_timeout and proxy_read_timeout. This is useful for situations where memcached or redis is involved and the cache needs to be manually rebuilt. The attribute values set are the default nginx values.

Included commits from PR#3

• Installs current version of community
• Fix for nginx_site due to change here
• Bumped php-fpm cookbook version to match new method for setting up pools
• Updated Vagrant file to use newer version of centos and use ominbus to install newer version of chef

Fix for https://github.com/yevgenko/cookbook-php-fpm version 0.6.3

• New format of pool configuration addded, PLEASE REVIEW
• Fixed nginx template for new datastruct.

adds simple kitchen testsupport to magento cookbook

• installs magento::default into a virtualbox
• sets forwarding network ports 80 and 443 to 808x and `844x`` on host machine
• sets mysql passwortds to test

Update:

• sets set_unless[:magento][:db][:password] = "magento" in kitchen.yml

Hi,

When using this cookbook without data sample and I navigate to the URL to complete Magento installation, the wizard installation is not showing.

If I modify the file local.xml as explained in below URL, I am able to install magento as usual visiting the page.

http://www.samundra.com.np/solved-failed-error-magento-is-already-installed/439

I got some chef errors during vagrant up/provision. It seems ther have been some updates to the latest versions of mysql and php-fpm cookbooks which are incompatible with this cook book.

I updated the dependency versions for this cook book to use the older versions of mysql and pnp-fpm to make it work.

Hi, I have running magento cookbook for ubuntu14.04,it shows apc error that get resolved Again shows libmysql package not found,so remove that for this platform,since no need libmysql for this platform.When again running it shows failure in restarting a php5-fpm service.when i ping that ip in browser it shows magento page but with mcrypt php missing error.So i enable phpenmod mcrypt and restart a php5-fpm service.Working fine.So now my query is "where to add this phpenmod mcrypt in a cookbook? Shall i add in definition of a magento cookbook.

Thanks, inhu

When attempting to run this recipe on Ubuntu 14.04, I encountered an error regarding the location of the apc.ini file. The recipe installs PHP 5.5 (with which I do not believe Magento is even technically compatible). Part of the issue seems to be that PHP 5.5 uses the new Zend OpCache and APC is now replaced by APCu in the package php-apc. Thus, the location /etc/php5/conf.d being used in the recipe does not exist: https://github.com/yevgenko/cookbook-magento/blob/master/recipes/default.rb#L23. The error was: No such file or directory - /etc/php5/conf.d.

I think the possible fix here might be either specifying that PHP is installed with a specific version (that is less than 5.5) or fixing the portion of the recipe that deals with APC to search in the correct location, which appears to be /etc/php5/fpm/conf.d/20-apcu.ini. Any thoughts on this?

Hi,

When using this cookbook with nginx as the web server, I encountered the following error:

==> magento: ================================================================================
==> magento: Error executing action `create` on resource 'template[/etc/nginx/sites-available/default]'
==> magento: ================================================================================
==> magento: 
==> magento: 
==> magento: Chef::Exceptions::FileNotFound
==> magento: ------------------------------
==> magento: Cookbook 'nginx' (2.7.4) does not contain a file at any of these locations:
==> magento:   templates/centos-6.5/nginx-site.erb
==> magento:   templates/centos/nginx-site.erb
==> magento:   templates/default/nginx-site.erb

This is because the template defined on line 26 of the _web_nginx recipe is duplicating the template already defined within the nginx recipe at "#{node['nginx']['dir']}/sites-available/default" which installs the nginx default site, later to be deleted by this recipe.

When a template is defined twice, the second definition inherits attributes from the first, including it seems the cookbook - meaning that when the magento recipe attempts to write this file from its own template, chef looks in the nginx cookbook for the file.

A simple fix is adding cookbook "magento" to the template definition in _web_nginx. This forces chef to look for the resource in the magento recipe.

I wasn't sure whether it would be something you'd want to include, or look at a different solution such as not installing the nginx default site in the first place... but thought I'd document since I'd figured it out. I can submit a PR with the change if you like.