This template is a minimal example for an application using VueJs and Django (RestFramework). Django is pre-configured in this repository to use a Postgres database.

It's setup to have a clear separation: use Vue, Yarn, and Webpack to handle all frontend logic and asset bundling, and use Django and RestFramework to manage a Data Models, Web API, and serve static files.

While it's possible to add endpoints to serve django-rendered html responses, the intention is to use Django primarily for the backend, and have view rendering and routing and handled by Vue + Vue Router as a Single Page Application (SPA). You can delete the Vue container information in docker-compose.yml file, and simply have Django not serve the vue file if you'd like to have Django serve views or another implementation (but at that point, why would you choose this repo?)

Out of the box, Django will serve the application entry point (index.html + bundled assets) at / , data at /api/, and static files at /static/. Django admin panel is also available at /admin/ and can be extended as needed.

The application templates from Vue Cli create and Django createproject are kept as close as possible to their original state, except where a different configuration is needed for better integration of the two frameworks.

You should change the username and password of your database in docker-compose.yml (under environment variables for both db and django).

There are currently two branches. master is a template that includes a user registration and login system, and adds Creative Tim's Black Dashboard theme to the mix. It is a very good start for a project that requires a user authentication system.

The basic-no-users-no-black-dashboard branch has no user authentication system built-in, no CORS configuration, and no black dashboard theme. It is just a very basic barebones start.

If this setup is not what you are looking for, you might want look at other similar projects:

• ariera/django-vue-template
• vchaptsev/cookiecutter-django-vue

Prefer Flask? Checkout gtalarico/flask-vuejs-template

(This is a live demo of the original repo without Docker and Postgres. Todo: fix that) Live Demo

• Django
• Django Restframework
• Django Whitenoise, CDN Ready
• Vue Cli 3
• Vue Router
• Docker Compose Ready Configuration
• Postgres Database
• Vuex
• Gunicorn
• Configuration for Heroku Deployment

Before getting started you should have the following installed and running:

• Docker & Docker Compose

Docker should install everything else in their containers.

$ git clone https://github.com/iprogramstuff/docker-django-vue-postgres-template
$ cd docker-django-vue-postgres-template

Setup

$ docker-compose up --build

$ docker exec -it container-name bash

Default container names are: docker-django-vue-frontend, docker-django-vue-backend, docker-django-vue-db. You can see them by running docker container ps

The Django and Vuejs application will be served at localhost:8002.

The dual dev server setup allows you to take advantage of webpack's development server with hot module replacement. Proxy config in vue.config.js is used to route the requests back to django's Api on port 8000.

See settings.dev and vue.config.js for notes on static assets strategy.

This template implements the approach suggested by Whitenoise Django. For more details see WhiteNoise Documentation

It uses Django Whitenoise to serve all static files and Vue bundled files at /static/. While it might seem inefficient, the issue is immediately solved by adding a CDN with Cloudfront or similar. Use vue.config.js > baseUrl option to set point all your assets to the CDN, and then set your CDN's origin back to your domains /static url.

Whitenoise will serve static files to your CDN once, but then those assets are cached and served directly by the CDN.

This allows for an extremely simple setup without the need for a separate static server.

Cloudfront Setup Wiki

• Set ALLOWED_HOSTS on backend.settings.prod.py
• Set DEBUG=False, and make sure to use collectstatic and another web server to serve static content.
• Set DJANGO_SETTINGS_MODULE=backend.settings.prod and use it to load the correct settings file.