Fix in-db configuration in dev environment

Previously, in-db configuration only worked when warnings_as_errors was disabled because re-compiling scrubbers on application restart created a warning about module conflicts. This patch fixes that by enabling ignore_module_conflict option of the compiler at runtime, and enables warnings_as_errors in prod since there is no reason to keep it disabled anymore.

I think we should keep warnings_as_errors disabled in prod because otherwise pleroma could just stop working over a mere warning (like new ones added in a elixir/erlang version update).

added 1 commit

• b8cf4928 - Fix in-db configuration in dev environment

Compare with previous version

added 1 commit

• e6ccc255 - Fix in-db configuration in dev environment

Compare with previous version

enabled an automatic merge when the pipeline for e6ccc255 succeeds

resolved all threads

canceled the automatic merge

merged

mentioned in commit 63798e89