Francesco Cataldo

So I've tried to add some code in settings.py... to allow method in the server ngix and to fix that error: `Refused to display in a frame because it set...

@cobia So I think the problem is in build_min.js because gettext is undefined... and that's become django doesn't have any gettext associated (I think...)

It can be used the function on `UniqueTogetherValidator,` `enforce_required_fields` to avoid the keyerror: ```python def enforce_required_fields(self, attrs, serializer): """ The `UniqueTogetherValidator` always forces an implied 'required' state on the fields...

Follow the instructions by @hetvi01 Example: app_label -> `example` `your_project.your_application.apps.py` ```python from django.apps import AppConfig class ExampleConfig(AppConfig): default_auto_field = "django.db.models.BigAutoField" name = "example" verbose_name = "Examples" def ready(self) -> None:...

If you manually install the `electron21` package, could you install bruno? ```shell sudo pacman -Syu electron21 ```

great solution, instead of `CharField`, i'll be use a `FilePathField` from django docs [FilePathField](https://docs.djangoproject.com/en/4.2/ref/models/fields/#filepathfield) 

> > great solution, instead of `CharField`, i'll be use a `FilePathField` > > from django docs [FilePathField](https://docs.djangoproject.com/en/4.2/ref/models/fields/#filepathfield)  > > Good catch ! Didn't think of it, but sure...

@fabiocaccamo the users would do a migration command, cause new field features..

@fabiocaccamo why should there be conflicts?

@fabiocaccamo but if you customize the path setting, should not run `makemigrations`, is a features of `FilePathField`. We can add a callable to dynamically return the path for the new...