Question 1

How do I change the linter rules in wemake-django-template?

Accepted Answer

You can modify the configuration files for `ruff` and `wemake-python-styleguide` included in the project, but this may require deep understanding of the template's structure to avoid breaking its enforced standards.

Question 2

wemake-django-template vs standard django-admin startproject: which is better for a new project?

Accepted Answer

Choose wemake-django-template if you need a production-ready foundation with built-in code quality and security tools. Use django-admin startproject for more flexibility and minimal setup, especially if you prefer to select your own tooling.

Question 3

Can I use Django REST Framework instead of django-modern-rest with this template?

Accepted Answer

No, the template is optimized for `django-modern-rest`, and swapping to Django REST Framework would require significant reconfiguration of the API layer and dependencies, as highlighted in the features list.

Question 4

How to deploy a project from this template without Docker?

Accepted Answer

While possible, it's not recommended; you'd need to extract the application code and manually set up servers, losing benefits like the pre-configured Caddy setup and containerized environments.

Question 5

What's the performance impact of using Caddy in production?

Accepted Answer

Caddy is lightweight and efficient, but the template's default configuration with HTTPS and HTTP/2 may require tuning for high-traffic scenarios, though it generally enhances security and speed.

Question 6

Is wemake-django-template good for microservices?

Accepted Answer

Yes, its Dockerized setup and modern REST API support make it suitable, but the opinionated tooling might add overhead if your microservices ecosystem uses different standards or simpler setups.

wemake-django-template

What is wemake-django-template?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions