DjangoLDP reference guide

The DjangoLDP commands

$ djangoldp --help
Usage: djangoldp [OPTIONS] COMMAND [ARGS]...

  DjangoLDP CLI

  --version  Show the version and exit.
  --help     Show this message and exit.

  configure     Configure the project.
  initserver    Start a DjangoLDP server.
  install       Install project dependencies.
  runserver     Run the Django embeded webserver.
  startpackage  Start a DjangoLDP package.

The djangoldp server is built ontop of django framework. The django core commands are also available. Check python –help and the official Django documentation.

The Initserver command

This command initiate a new server folder from a template. It has the minimal option to work out of the box.

The Configure command

This is a command meant to tell the server the settings have changed and it must run some maintenance operations and data integrity check, such as the model migration of the LDP packages.

It has options to create new administrator users during the configuration process.

The Install command

This command parses the dependencies section of the configuration file and install all python distribution required by the project. It is a wrapper around the requirements.txt file.

The runserver command

This command loads the configuration and starts the LDP server. It is a wrapper around the django-admin runserver command.

The startpackage command

This a helper command working the same way the django startpackage does command. It creates a folder with a DjangoLPD package template.

The DjangoLDP configuration file

The server comes with a default settings.yml you can customize.

It contains 3 main sections:

  • dependencies: contains a list of dependencies to install with pip during the install phase

  • ldppackages: contains a list of djangoldp packages to activate

  • server: contains all the configuration required by djangoldp server

You need to restart the server after a change in configuration.

The Dependencies section

This is not mandatory as you can install all your dependencies manually. But it is convienent to have all in one file when exchanging server configurations.

The format for dependencies is the one accepted by pip. For example:

  - git+

As for any python project when you declare a dependency you have to make sure it is installed. You can use the wrapper command djangoldp install for this.

The LDP packages section

When you want to use a LDP package you need to reference it in the configuration. For example:

  - djangoldp_account

The name referenced there must be the name of the python module, the one your would use with the import statement.

Some packages may require some configuration to work properly. It is a good practice to run the djangoldp configure command after adding or upgrading a LDP package.

Here you have :

If the description of the available packages is unclear, open an issue to ask for more description.

The Server section

This section contains all parameters to the server itself. All this section is loaded as a Django configuration object to initialize the server.

see for a detail explanation of all settings

The server parameters can be changed at different levels. They are overriden in the following order:

  1. The DjangoLDP core default settings

  2. The DjangoLDP package settings

  3. The code from the extra settings module

  4. The server section of the YAML settings file

Which means a value written in the server section of settings.yml will override any parameters given by the core or the djangoldp packages.

The MIDDLEWARE and INSTALLED_APPS parameters make exception to that behavior. Those lists are extended from previous values instead of being rewritten. When duplicated entries are detected in those settings, only the first items present in the list are kept.

The extra settings module

The settings.yml server section doesn’t support dynamical configuration. When this is required, python code for configuration can also be loaded from a module along with the settings.yml.

The DjangoLDP package settings

The DjangoLDP packages support settings declaration through a special at the module’s root. This file is fetched by the djangoldp core at runtime and all parameters are loaded following the settings resolution order. (see The server section)

# cat mypkg/mypkg/