Release of our Chef Cookbooks

Release of our Chef Cookbooks

Stefan Galinski 20. April 2015 Releases

0 Kommentare // Lesezeit: 3 min.

We are always encouraged to give something back to the community. This time we released our internally used chef cookbooks for TYPO3 and Neos that we are using to setup our local Vagrant development infrastructure. They are well tested and production ready. So feel free to use them in your development projects.

What exactly is Chef?

Chef is a professional tool that helps you to setup and manage your infrastructure and helps to publish changes to your existing servers. The code that may be executed is defined in so called cookbooks that are containing all relevant code, templates and configuration for a specific purpose e.g. setting up a TYPO3 site. Our chef cookbooks are a result of several months of testing and evaluating the best solution for our special requirements. Note that they are based all upon the latest Ubuntu LTS.

What you will get ... and what not

The following sections are describing our released chef cookbooks. Feel free to fork and contribute to them or report issues in our Gitlab. Please remember that the cookbooks are for our internal needs, so don't expect that we integrate all requested features. Also it's possible that we drop and rewrite existing features without a deprecation period. Furthermore we are not releasing our whole Vagrant infrastructure code. Maybe this will happen sometimes in the future. Also note that the cookbooks may depend upon each other. However we hope that you can get some profit out of this cookbooks.

Cookbook - neos_site

The youngest of our cookbooks was created to setup a development instance for our own website. It's generic enough to be used for other Neos sites too, but you may find bugs and missing features. You can find a lot of configuration options in the attributes file that you can set in your Vagrantfile or our Chef role file.

https://gitlab.sgalinski.de/chef-cookbooks/neos_site

Cookbook - typo3_site

This cookbook is used to create a new instance that is driven by a TYPO3 CMS instance. It's used for a lot of different setups and very flexible. Like for the neos_site cookbook, you can set  several configuration options.

https://gitlab.sgalinski.de/chef-cookbooks/typo3_site

Cookbook - mailcatcher

Use the mailcatcher cookbook if you want to test mailing in your development instance without to really send them out into the wild. This is especially useful if you want to test mass mailings to thousands of users. The tool behind this nice cookbook is also called mailcatcher and a small ruby application. It's one of our favorite development tools since we are using it. :-)

https://gitlab.sgalinski.de/chef-cookbooks/mailcatcher

Cookbook - ubuntu_base

This one is very special and provides some configuration for our Ubuntu based vagrant instances. It's very probable that you want to use your configuration in your instances. Note that this cookbook also provides some requirements for the other cookbooks!

https://gitlab.sgalinski.de/chef-cookbooks/ubuntu_base

Cookbook - XDebug

You want to integrate the debugger and profiler tool xdebug in your setup? Then use this cookbook that integrates perfectly into your TYPO3 site. You can easily connect your PhpStorm with the Vagrant box.

https://gitlab.sgalinski.de/chef-cookbooks/xdebug

Cookbook - XhProf

The last cookbook integrates the profiling tool XhProf from Facebook. Try it out, you will love it! To start a performance analysis session, you must add the following two lines into your .htaccess.

php_value auto_prepend_file “/opt/xhprof/external/header.php”
php_value auto_append_file “/opt/xhprof/external/footer.php”

This allows you to run the profiler on any request by adding the following parameter to any request "?_profile=1".

https://gitlab.sgalinski.de/chef-cookbooks/xhprof


0 Kommentare

Dateien hier ablegen
Dateien hochladen
Keine Kommentare.