TW
postgres.int :: /etc/postgres/.../pg_hba.conf is ansible managed ... so i need to update ansible files to not lose my changes (nsupdate_info db host rule).
https://docs.djangoproject.com/en/2.0/releases/2.0/#foreign-key-constraints-are-now-enabled-on-sqlite https://stackoverflow.com/questions/54163537/django-db-utils-integrityerror-foreign-key-constraint-failed-while-executing-li is it that? currently host is in BAD_HOSTS to not crash the process all the time.
we support quite some languages now, but translations need more work: some translations of nsupdate.info might be incomplete, some might need proofreading and quality improvements. Translations should be checked practically...
i noticed that there are multiple machines out there, which seem to update 1 identical dyndns Host with their private IP address (of `10.233.*.*`). as this is a whole set...
some bad dyndns clients just retry again and again in case of e.g. authentication errors. as we count auth errors in the Host record, this writes to the DB all...
while a lot of our maint scripts have `database is locked` issue, the `fault --reset-client --reset-server` i used ran for a longer time without itself running into a lock issue....
current is 4.1.3, we currently use 3.3.7 (last 3.x). http://getbootstrap.com/docs/4.1/migration/
see other projects (e.g. borgbackup). plus: - how to deal with django migrations? - how to deal with translations?
i received an email about the still miserable (?) ipv6 support of ddclient. in the sample config we show after adding a host, we have some section about ipv6 (for...
Currently, when adding a related host, the ns record won't be created immediately, but only after first dyndns update of the primary host (which can take a while when primary...