Bruno mention on IRC we should consider using dynaconf [0]. I think it solves exactly the problems we have so I rewrote the epic [1] to outline its usage.
[0]: https://dynaconf.readthedocs.io/en/latest/guides/django.html#settings-files [1]: https://pulp.plan.io/issues/3981 -Brian On Thu, Sep 6, 2018 at 12:37 PM, Brian Bouterse <bbout...@redhat.com> wrote: > Recently I discovered Pulp3 only works with Redis on localhost [0]. The > resolution is that our users will have to create a separate settings file > that is Python for connecting to non localhost. :( > > Besides this issue, there are various other issues caused by the settings > file format for Pulp3 being yaml. I've collected them into this epic [1]. > It also includes a proposal to switch the settings file usage to a normal > Django settings file format. > > [0]: https://pulp.plan.io/issues/3980 > [1]: https://pulp.plan.io/issues/3981 > > I'd like to get input on this decision soon so we can resolve these > issues. Please send feedback and any -1s by Thursday Sept 13th or leave > them on the epic [1]. > > Thank you! > Brian > >
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev