Hi all,
The way I've always worked, developers run `makemigrations` locally, and
commit migration files to the repo.
However, a suggestion has recently come my way that a better strategy is to
only commit model changes to the repo (leaving the migrations directory
gitignored), and then run `ma
On Tuesday, August 6, 2013 3:42:01 PM UTC+1, Jacob Kaplan-Moss wrote:
>
> We plan to take steps to address BREACH in Django itself, but in the
> meantime we recommend that all users of Django understand this
> vulnerability and take action if appropriate.
>
>
Would randomizing the CSRF token on
2 matches
Mail list logo