the-paperless-project/paperless

Django runserver

Open

#329 opened on Mar 23, 2018

View on GitHub
 (8 comments) (3 reactions) (0 assignees)Python (7,803 stars) (513 forks)batch import
help wanted

Description

Thanks to #328 I noticed that the doc, docker container and the systemd service use manage.py runserver to start the paperless server.

This command is intended to be used for development and I think we should recommend user to setup their paperless in a more durable/stable/secure way (gunicorn, mod_wgi, ...)

Contributor guide

Tech stack
pythondjango
Domain
backenddevops
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic Django knowledgeDocker familiaritySystemd familiarity
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Review the current documentation, Dockerfile, and scripts/paperless webserver.service to understand the existing setup. Look at the linked PR #328 for context. Research options like gunicorn or uWSGI for production deployment. Check the comments for any proposed solutions or blockers. Then plan a migration from runserver to a production ready WSGI server, updating documentation, Docker container, and systemd service accordingly.