Skip to content
LibreHQ core: code to manage the various LibreHQ services.
Branch: master
Clone or download
frankduncan Merge pull request #31 from OpenTechStrategies/user-federation
LibreHQ-ize mediawiki login/logout links.
Latest commit 0800b51 Mar 16, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
wikis Protecting against bad username in authorizeduser. Mar 16, 2019
.gitignore Update ansible to work on aws localhost Feb 18, 2019 Revise 'Outstanding Questions' in Feb 17, 2019
Pipfile.lock Encrypt passwords with bcrypt. Mar 13, 2019


This is a placeholder description that should be filled out.


LibreHQ offers various services that are organized as separate Python modules and use separate databases. Currently these are:

  • wikis: a wiki hosting and generation tool


LibreHQ uses ansible to install. Please see in the ansible directory.


LibreHQ uses pipenv to manage its back end dependencies and handle running the server.

$ FLASK_APP=librehq pipenv run flask run

Starting a mock mail server

LibreHQ sends out email to port 1025 for certain actions, which can be listened to using a standalone python invocation:

$ python -m smtpd -n -c DebuggingServer localhost:1025

This is required in order to use certain parts of the site, and not having it running may result in errors.

Using the application

Part of the ansible setup is to install apache files with port forwarding. While you can probably access the application via http://localhost:5000, make sure to test by using http://__YOUR_LIBREHQ_HOSTNAME__.

The reason for this is that the other services not part of core librehq will use that address, meaning it's useful error prevention to ensure that it's all set up and working correctly.

Test csv2wiki data

There are files in testdata that you can use to populate a wiki using the csv2wiki tool via the interface (Populate wiki with csv data).

Extra tasks

If you have installed from ansible, and are just using the app without development, you can stop here.

For developers that may need to update the database, regenerate the html/js files, and do active work on the site, more information and useful commands follow.

Back End: Running migrations

While the ansible playbook will take care of running the migrations, you may need to run them manually at times, and can do so with:

FLASK_APP=librehq pipenv run flask db upgrade

Front End: Dependencies

LibreHQ uses npm to manage front end dependencies such as Vue.js. While the playbook will handle installation of everything, you will need to regenerate the client at times as you work:

$ npm run build

This command generates HTML, JavaScript, and CSS files for each page, and puts them where Flask can find them. So it needs to be done before booting the application (described below).

For front end development that doesn't involve the back end, you can also just do the "compile and hot-reload for development" command:

$ npm run serve

Then point your browser to URLs that include the .html extension, like http://localhost:8080/client/dashboard.html. We use "/client/" here to allow you to run both the npm server, and the python server simultaneously and via a proxy pass configuration like the following, use them together:

  ProxyPass /client/
  ProxyPassReverse /client/
  ProxyPass /
  ProxyPassReverse /

With this setup, going to <servername>/client/wikis.html will load the wiki data from the python server, allowing you to dynamically test your frontend code and backend code simultaneously

You can’t perform that action at this time.