Labdoo's main source code
PHP Shell Other
Failed to load latest commit information.
content Revert "Committing all wiki pages" Jun 26, 2016
dev Docker containers override /etc/hosts, so try to keep it always up to… Oct 9, 2014
docs - Improved documentation on how to upgrade the Linux distribution Nov 24, 2016
files Implements Labdoo Stories Dec 10, 2016
install - added registration module Jul 3, 2016
lec --- Moved rss feed icon to the footer --- Fixed teams dashboard searc… Apr 12, 2015
modules - Implemented "Allow users to add other users to conversations": http… Feb 12, 2017
themes/bootstrap1 Implements Labdoo Stories Dec 10, 2016
translations Added tar file for translation emails Feb 13, 2017
utils - Labdoo events: May 30, 2016
.gitignore Don't commit private vars by mistake. Oct 23, 2013
Dockerfile Building a docker image. Sep 24, 2014
LICENSE Initial commit Oct 20, 2013 - Implemented Labdoo watchdog to automatically restart server upon fa… Sep 13, 2015
build-labdoo.make Updated installation scripts. Added installation script for docker. Sep 9, 2014
doxygen.cfg Initial commit. Oct 20, 2013
drupal-org-core.make - Improved documentation on how to upgrade the Linux distribution Nov 24, 2016
labdoo.css Backporting changes from the branch oa. Nov 29, 2013 Implements Labdoo Stories Dec 10, 2016
labdoo.install --- Implemented Global Inventory Checks (GICs) --- fixed definition o… Oct 3, 2014
labdoo.make Implements Labdoo Stories Dec 10, 2016
labdoo.profile Upgrading Aug 10, 2014 Upgrading Aug 10, 2014


All of Labdoo’s source code is released under GPL version 3 or later.

Installation in development mode

The recommended way of installation is to build a new server from scratch, inside a chroot environment.

  • Get a copy of the project from GitHub:
    mkdir /var/chroot
    cd /var/chroot/
    git clone labdoo
  • If you intend to build the master branch, skip the following step:
    cd labdoo/
    git checkout $NAME_OF_THE_BRANCH
    cd ../
  • Modify and customize the settings:
    cp labdoo/install/ labdoo/
    vim labdoo/ # Make any necessary changes
  • Install the project inside a chroot system:
    time nohup nice labdoo/install/ labdoo/ &
    tail -f nohup.out
    less -r nohup.out

    The above process can take some time, depending on bandwidth and your computer speed. On an Intel(R) Xeon(R) CPU E5-2670 v2 @ 2.50GHz it takes about 12 minutes:

    real 11m9.292s
    user 6m31.217s
    sys  0m59.728s
  • Make sure to include the following lines in your /etc/hosts file (outside the chroot): localhost
  • Start the Labdoo social network:
    service chroot-lbd start
  • And that’s it! You can now access your Labdoo installation by opening your web browser and opening the URL Please use https protocol (instead of http) since currently the theme only works properly on https. (Notice that you will need to confirm the security exception on your browser the first time you access
  • If you need to stop Labdoo you can do: service chroot-lbd stop
  • If you need to start again Labdoo you can do: service chroot-lbd start

Installation in production mode

A development Labdoo node can be converted into a production node by following the next steps:

  • Drop (1) the server certificate, (2) the intermediate certificate (chain certificate) and (3) private key to the folders etc/ssl/certs and etc/ssl/private, respectively.
  • Modify the file /etc/apache2/sites-enabled/lbd-ssl.conf so that SSLCertificateFile, SSLCertificateChainFile and SSLCertificateKeyFile point to the certificate, chain certificate and private key, respectively.
  • Modify both /etc/apache2/sites-enabled/lbd-ssl.conf and /etc/apache2/sites-enabled/lbd.conf so that all URL and email address information points to and (or to your chosen values for these parameters), respectively.
  • If you want to disable the SSL password prompt upon restarting apache, add the following two lines to the beginning of the file /usr/share/apache2/ask-for-passphrase:
  • Modify /etc/hosts so that the localhost points to
  • Modify the file /var/www/lbd/sites/default/settings.php so that $base_url points to

Installation in a docker container

This is almost the same as the installation above, except that instead of install/ you call install/

nohup time nice labdoo/install/ labdoo/ &

Then to stop and start Labdoo you do: stop lbd and start lbd.

Building with docker

Another way is to use the command docker build to build an image and then docker run to create a container from this image:

vim labdoo/install/ build --tag=labdoo labdoo/ run -d --name=lbd -p 80:80 -p 443:443 labdoo