See System dependencies for base system requirements.
An alternative way to use middlewares (ie. ElasticSearch, Redis, MongoDB) is provided for getting started easily so it’s not mandatory to install those natively. See Middlewares for details.
Retrieving the sources¶
You also will need Git to fetch sources and publish your contributions.
If you use a Debian-like distribution with
apt-get, the package is named
If you prefer Homebrew (OSX), the package is named
The sources of the project are on Github:
$ git clone https://github.com/opendatateam/udata.git
$ cd udata $ docker-compose up
On the very first run it will download and install Docker images which takes a while depending of your connection.
Test your docker-compose is running successfully entering
It should output a JSON search response.
If you have no output at all for too long,
check the IPv6 possible issue.
Python and virtual environment¶
It is recommended to work within a virtualenv to ensure proper dependencies isolation. If you’re not familiar with that concept, read Python Virtual Environments - a Primer.
Alright, now you can install virtualenv and then type these commands knowing what you are doing:
$ virtualenv --python=python2.7 venv $ source venv/bin/activate $ pip install -r requirements/develop.pip $ pip install -e .
Some dependencies have an optionnal compilation support for Cython resulting in more performances (mostly XML harvesting). To enable it, you need to install Cython before all other dependencies:
$ pip install Cython $ pip install -r requirements/develop.pip $ pip install -e .
NodeJS and modules¶
NodeJS is required to build or run the frontend. Please check the .nvmrc at the root of the repository to check the exact version of NodeJS you need.
you should consider installing NVM which uses the existing
$ nvm install $ nvm use
$ npm install
Once it’s done, you should be able to run the build command for JS and CSS:
$ inv assets_build
If you plan to hack on statics (JS, CSS files), a dedicated command
inv assets_watch will watch these files and recompile (the modified part only!) on each save.
Running the project¶
As long as you have the middlewares up, you can use invoke to launch the development services (you might want to have each one runnning in a terminal):
$ inv serve # Start the development server $ inv worker # Start a worker process $ inv beat # Start a scheduler process $ inv assets_watch # Continously watch and build assets
When you have the development server running, you can open your browser to http://localhost:7000. Everything is up and running!
If not, it’s time for your first contribution to improve the documentation! But first let’s try to figure out together what went wrong on Gitter.
You need to initialize some data before pushing uData to it’s full potential:
# Initialize database, indexes... $ udata init # Optionnaly fetch and load some licenses from another udata instance $ udata licenses https://www.data.gouv.fr/api/1/datasets/licenses # Compile translations $ inv i18nc
That’s it! You’re all set to start using uData and contributing.
Most of the common tasks are scripted in the
tasks.py file (which is using invoke).
You can get the documentation related to all tasks with:
$ inv -l
# Update dependencies $ inv update # Update dependencies and migrate data $ inv update -m
It’s advised to update your dependencies when you pull upstream changes or switch branch:
# Update dependencies, migrate data, recompile translations... $ inv update -m i18nc
Now check out our advanced documentation for a focus on some specific tasks. You may want to be able to run the tests to for a backend contribution, maybe create a full theme or simply provide some fixes to the translations or the documentation.