GDAPS Frontend Support

GDAPS supports frontends for building e.g. SPA applications. ATM only Vue.js ist supported well, but PRs are welcome to add more (Angular, React?). Even PySide or Qt5 would be possible.


pip install gdaps-frontend

Add gdaps.frontend to INSTALLED_APPS, before gdaps.

The included gdaps.frontend package provides basic tools which then can be extended by other plugins, like gdaps-frontend-vue. You have to install at least one frontend plugin, e.g.

pip install gdaps-frontend-vue

GDAPS detects it automatically and makes the “vue” FRONTEND_ENGINE available.


    "FRONTEND_ENGINE": "vue",
    "FRONTEND_DIR": "frontend",

There are some keys here to configure:


The engine which is used for setting up a frontend. ATM it can only be “vue” or “pyside”. See the [gdaps-frontend-vue package](

FRONTEND_DIR (optional)

This is the directory for the frontend, relative to DJANGO_ROOT. Default is “frontend”.


This is the package manager used to init/install packages. ATM you can use “yarn” or “npm”. Default is *npm*.

Template overriding

gdaps.frontend renders a simple builtin index.html file as template.

If you need to override that template, e.g. your (Javascript?) frontend provides an own, you can do that: Just create an index.html file within your <PROJECT_NAME>/templates directory (e.g. myproject/templates). GDAPS searches for templates using Django’s methods and will use any template that is found under that template name.

Management Commands

With gdaps.frontend, you have a new management command available. Set the GDAPS["FRONTEND_ENGINE"] to your desired engine (“vue”, “pyside”), and call:

./ initfrontend

This creates a /frontend/ directory in the project root, and installs a frontend application there. The type of frontend (and installation) depends on what you have selected in GDAPS["FRONTEND_ENGINE"].

So all you have to do is:

  1. Add gdaps.frontend to INSTALLED_APPS (before gdaps)

  2. Install a frontend plugin, like pip install gdaps-frontend-vue.

  3. Execute ./ initfrontend

  4. Call ./ startplugin fooplugin

  5. Call ./ syncplugins

  6. start yarn serve in the frontend directory

  7. start Django server using ./ runserver

To remove a plugin from the frontend, just remove the backend part (remove it from INSTALLED_APPS or uninstall it using pip) and call syncplugins again. It will take care of the database models, and the uninstallation of the frontend part.


I’d like to give back what I received from many Open Source software packages, and keep this library as open as possible, and it should stay this way. GDAPS is licensed under the General Public License, version 3.