#APACHE APP CHEF INSTALL#
#APACHE APP CHEF CODE#
#APACHE APP CHEF DOWNLOAD#

The first thing to show you is the recipes directory, where I have a few new recipes.

#APACHE APP CHEF CODE#

However there’s a lot more code to write for this, so I’ve written it offline, and I’ll go through it with you step by step. In the previous lessons I typed out the recipes in real time.

So that’s a high level overview of what needs to happen. And Apache knows where to expect them based on the configuration file that I’ll deploy as a template. If you’re not familiar with it you might want to check out the Introduction to Continuous Deliver course that’s a part of the Intro to DevOps learning path.Īfter the application has it’s dependencies installed, I can then copy the files over to a directory where Apache expects them. If you’re already familiar with continuous delivery as a concept, then you know what I’m talking about. It’s a better practice to have it built as a part of the continuous delivery process. It’s worth mentioning, that I don’t recommend building your application on the server where it’ll reside. Once the code is downloaded it needs to have its dependencies installed.

#APACHE APP CHEF DOWNLOAD#

With those packages installed I can use git to download the source code for the app from Github. The first is Git, so that I can download the application code, the second is a Python package manager called pip, and the last is an Apache module that allows Apache to run a Python app, and that’s called mod-WSGI. The application expects a database named “appdata” and a MySQL user named “appuser.” Then I need to create a database and database user for the application code. The first is to have the Apache web server installed. In order get this LAMP application installed, I have a few requirements. I want to be able to deploy this entire application on any node that is managed by Chef. When I add records, they’re stored in the database, and the displayed in a list when the page is loaded. While it’s not beautiful, it’s a basic web application, with a MySQL database. Here’s a look at the LAMP application that I’m trying to install. In this lesson there’s quite a bit of work to do in order to finish up the application deployment process. In the previous lesson I made the default recipe a bit more generic, so that it would run on multiple Linux platforms. Welcome back! I hope by now you’re starting to feel comfortable with the way that Chef operates, at least conceptually. We will work with Berkshelf to download cookbooks to make sure they are the most recent versions.Īfter all this, we will execute the kitchen destroy command to clean up VMs that are not of use to us at this time.įinally, we will perform a recap of the lesson. We will introduce you to the Chef Supermarket, a community that creates and shares their cookbooks. You will view the recipes directory including ones for installing apache, for installing MySQL, and for installing the application. We will then copy the files to a directory where Apache expects them.

#APACHE APP CHEF INSTALL#

You will use git to download the app source code from Github, and install its dependencies.

Finally, we will install a few packages: Git, a Python package manager called pip, and mod-WSGI, which is an Apache module to run a Python app. Next, we will create a database and database user for the application code. We will verify that we have Apache web server installed, and then install MySQL. The end goal is to deploy this entire application on any node that is managed by Chef.

In this lesson, we will finish up the application deployment process in Chef.

Apache app chef