Installing Build Dependencies<\/h2>\n
When you install Lemur on a bare Ubuntu OS, you will need to grab the following packages so that Lemur can correctly build its dependencies:<\/p>\n
.. code-block:: bash<\/p>\n
sudo apt-get update
sudo apt-get install nodejs nodejs-legacy python-pip python-dev python3-dev libpq-dev build-essential libssl-dev libffi-dev libsasl2-dev libldap2-dev nginx git supervisor npm postgresql<\/p>\n
The above command will install nodejs, pip, nginx , git, npm, and PostgreSQL database packages.\u00a0<\/p>\n Note: Installing the\u00a0node<\/strong> package manager may create the nodejs<\/strong> bin at \/usr\/bin\/nodejs path instead of \/usr\/bin\/node. Run the following command to create a soft link at the desired path.<\/p>\n sudo ln -s \/user\/bin\/nodejs \/usr\/bin\/node<\/p>\n Now, install virtualenv<\/strong> package using following command.<\/p>\n sudo pip install -U virtualenv<\/p>\n In this guide, Lemur will be installed in the\u00a0\/www <\/strong>directory, so you need to create that directory first:<\/p>\n sudo mkdir \/www Now, clone\u00a0Lemur\u00a0<\/strong>latest source inside the just created directory and give yourself write permission (lemur <\/strong>user\u00a0is the created in this tutorial):<\/p>\n sudo useradd lemur sudo git clone https:\/\/github.com\/Netflix\/lemur Also, create the virtual environment, activate it and enter Lemur’s directory:<\/p>\n su lemur source \/www\/lemur\/bin\/activate Activating the environment adjusts PATH <\/strong>environment variable , so that things like pip now install into the virtualenv by default.<\/p>\n After setting up the system, make sure that you are in the virtualenv to run “make release” command.<\/p>\n which python<\/p>\n And run the following command to install npm<\/strong> dependencies as well as compile static assets.<\/p>\n \u00a0make release<\/p>\n Before we run Lemur, we must create a valid configuration file for it. The Lemur command line interface comes with a simple command to get you up and running quickly. The following command will create a default configuration under “~\/.lemur\/lemur.conf.py<\/strong>” and this location can be specify by passing the config_path<\/strong> parameter to the create_config<\/strong> command.<\/p>\n \u00a0lemur create_config<\/p>\n Once created, you will need to update the configuration file with information about your environment, such as which database to talk to, where keys are stored etc.<\/p>\n vi ~\/.lemur\/lemur.conf.py<\/p>\n The SQLALCHEMY_DATABASE_URI<\/strong>\u00a0string of Postgresql <\/strong>can be broken up like this: The below given screenshot shows that following required variables are filled in the configuration file:<\/p>\n For production, a dedicated database is recommended. For this guide, I will assume postgres has been installed and is on the same machine that Lemur is installed on.<\/p>\n First, set a password for the postgres user. For this guide, we will use lemur<\/strong> as an example but you should use the database password generated by Lemur:<\/p>\n sudo -u postgres -i<\/p>\n psql Once successful, type CTRL-D to exit the Postgres shell.<\/p>\n Next, we will create our new database:<\/p>\n sudo -u postgres createdb lemur<\/p>\n Lemur provides a helpful command that will initialize your database for you. It creates a default user (lemur<\/strong>) that is used by Lemur to help associate certificates that do not currently have an owner. This is most commonly the case when Lemur has discovered certificates from a third party source. This is also a default user that can be used to administer Lemur.<\/p>\n In addition to creating a new user, Lemur also creates a few default email notifications. These notifications are based on a few configuration options such as LEMUR_SECURITY_TEAM_EMAIL<\/strong>. They basically guarantee that every certificate within Lemur will send one expiration notification to the security team.<\/p>\n Make note of the password used as this will be used during first login to the Lemur UI.<\/em><\/p>\n cd<\/span> \/www\/lemur\/lemur\u00a0<\/p>\n lemur init<\/p>\n The following snapshot shows the output of the “lemur init” command.<\/p>\n By default, Lemur runs on port 8000. Even if you change this, under normal conditions you won’t be able to bind to port 80. To get around this (and to avoid running Lemur as a privileged user, which you shouldn’t), we need setup a simple web proxy. There are many different web servers you can use for this, we like and recommend Nginx.<\/p>\n Add following lines in the configuration file “\/etc\/nginx\/sites-available\/default<\/strong>“.<\/p>\n After making these changes, restart Nginx service to apply them:<\/p>\n sudo service nginx restart<\/p>\n Lemur provides a built-in web server (powered by gunicorn and eventlet) to get you off the ground quickly. To start the web server, you simply use “lemur start<\/strong>“.<\/p>\n![\"Install](\"https:\/\/www.howtoforge.com\/images\/installation_and_usage_of_lemur_certificate_manager_on_ubuntu_platform_\/big\/required_packages1.JPG\" "\\"\\"")
<\/a><\/p>\n<\/a><\/h2>\nSetting up the build environment<\/h2>\n
cd \/www<\/p>\n<\/a><\/p>\n
sudo passwd lemur
sudo mkdir \/home\/lemur
sudo chown lemur:lemur \/home\/lemur<\/p>\n<\/a><\/p>\n
sudo chown -R lemur lemur\/<\/p>\n<\/a><\/p>\n
virtualenv -p python3 lemur<\/p>\n<\/a><\/p>\n
cd lemur<\/p>\n<\/a><\/p>\nInstalling Lemur from Source<\/h2>\n
<\/a><\/p>\n<\/a><\/h2>\nCreating Lemur configuration<\/h2>\n
<\/a><\/h2>\nUpdate Lemur configuration<\/h2>\n
“postgresql:\/\/userame:[email\u00a0protected]<\/a><database-fqdn>:<database-port>\/<database-name>”<\/p>\nLEMUR_SECURITY_TEAM_EMAIL<\/pre>\n
LEMUR_DEFAULT_COUNTRY
<\/a><\/p>\nSetup Postgres Database<\/h2>\n
<\/a><\/p>\n
postgres=# CREATE USER lemur WITH PASSWORD ‘lemur’;<\/p>\n<\/a><\/p>\n<\/a><\/p>\nInitializing Lemur Certificate Manager\u00a0<\/h2>\n
<\/a><\/p>\n<\/a><\/p>\nNGINX web server configuration for Lemur<\/h2>\n
location \/api {location \/ {<\/a><\/p>\n<\/a><\/p>\nStarting the Web Service<\/h2>\n