In this post, I'll make a quick tour over all the technological stack that underpins our Flask and React application (which is an application to manage identities, but I won't go into its specifics here). It will be a general overview, without going into the implementation details of each part, intended as a showcase for the kind of architecture that these technologies allow.

In many cases when there is a modification in a model’s instance we need execute some action. Django provides us an elegant way to handle with these situations. The signals are utilities that allow us to associate events with actions. We can develop a function that will run when a signal calls it.

Sometimes due to the needs of a project, we need to create odt documents to represent information that we have in our application. This task can be light using the Secretary library

In these lines I will try to provide an introduction to Python web frameworks, or, at least, to those frameworks I have worked with. I will try to show their most salient features and their weaknesses, from the point of view of my own experience with them, and explain the criteria I would use to choose each framework for particular projects

We everyone know what a cookie is; that small portion of data saved locally on the browser that we’ve might used it twice in development environments. But, once in production, we must know that the European Comission (EU) have strong policies about the use of cookies. To make it short, you cannot use cookies freely. A django library has the perfect solution: Django Cookielaw.

In this article we shall discuss a point to which we give little importance when we are beginning to programme our application and which, with little details, we can improve significantly. Security!