Djangonauts from in and around Denmark are meeting up for the second edition of Django Day, to be held on September 25th 2020. It will be a full day of talks, either to be experienced online -or- at our venue with safe social distancing.
Benjamin "Zags" Zagorsky presents "Rapid Prototyping in Django", a distilled set of lessons and recommendations from the projects we've done for how to build a functional Django website in 2 days and not regret it later.
Using Django to build an internal tool that helps make sense of ~5 Petabytes of Genomic data that is then made available to clinicians. It’s running across many different AWS resources using ECS Fargate.
Safely separate multiple tenants in a Django database
django-scopes
Motivation
Many of us use Django to build multi-tenant applications where every user only ever
gets access to a small, separated fraction of the data in our application, while
at the same time having some global functionality that makes separate databases per
client infeasible. While Django does a great job protecting us from building SQL
injection vulnerabilities and similar errors, Django can't protect us from logic
errors and one of the most dangerous types of security issues for multi-tenant
applications is that we leak data across tenants.
It's so easy to forget that one .filter call and it's hard to catch these errors
in both manual and automated testing, since you usually do not have a lot of clients
in your development setup. Leaving radical, database-dependent ideas
aside, there aren't many approaches available in the ecosystem to prevent these mistakes
from happening aside from rigorous code review.
feincms3 provides additional building blocks on top of django-content-editor and django-tree-queries which make building a page CMS (and also other types of CMS) simpler.
feincms3
feincms3 offers tools and building blocks which make building a CMS that
is versatile, powerful and tailor-made at the same time for each project
a reachable reality.
feincms3 offers tools and building blocks which make building a CMS that is versatile, powerful and tailor-made at the same time for each project a reachable reality.
Docker-based Message Queuing (DBMQ) is an efficient way to run the pre-built configurations on the build process of Dockerfiles. Once you have finished configuring, you will be able to create your images based on your configurations. DBMQ is very flexible with Django projects and you might stay away from troubles with creating a Dockerized Django project. After the building process, your image will be ready to get started. Use a text editor to step through your container and make changes. (the pre-installed editor is Vim)
Why DBMQ is Needed?
This system locates between the user and the Docker service. You config your requirements and let this automated system to provide them to you. You don't need to be a…
