many difficulties and oddities

[atesin]

hi... i like the idea of this application, of being modular, unlike ddclient that i was lont time using it.. i have big hopes with this

however sometimes is a nightmare to configure... i recently moved to a debian server (raspberry pi actually), have to reinstall everything, and make DDNS to work is essential for me

---

however i had troubles from the beginning, until i like the approach of one configuration section for each service/account... i think it would be more practical/natural/flexible to have one configuration section for each DOMAIN

what happens if somebody has 2 domains in same ddns service?, or if someone updates some domain with some ip and its subdomain with another?, or if those domains in same ddns service have different user accounts (i.e. for different customers)?? ... that is what i had to write a plugin with non-standard .netrc syntax

---

so i migrated my both config files from my old fedora machine to this debian one (raspberrypy)... but a message appears saying my WHOLE ddupdate.conf file is skipped because lack of [update] section :/ ... so nothing happens except the default 'dry-run' update... so i added the [update] label, but now just discards my other sections, etc

---

speaking about .netrc ... i never heard that file before, but according what i searched, is an ancient and poor documented file used to store credentials to ease REMOTE FTP connections, i guess nobody uses that file nowadays, for me it sounds like having a text file listing remote hosts (yes, the hosts file, in times prior to DNS system)

why NOT to make the same other applications do?, to have its OWN custom/exclusive/non-shared path/name/format file? ... for example, mysql have its own my.cnf file, apache has its own httpd.conf, so nginx with nginx.conf (with different format), php has php.ini file that is exclusive and only read by php, samba has smb.conf file, ssh has just sshd_config, and so on

---

another problem i faced were the $XDG_CONFIG_HOME and similar environment variables that threw me errors when i first ran ddupdate-config.... i found that those variables are related to X11/Xorg, but what happens if somebody has just text console with no graphical interface?, or even has a headless server with no monitor attached at all? (like me!)

i was unable to make work ddupdate from debian package, i found is pretty outdated anyway and seems $XDG-* vars were fixed, so i removed it and installed ddupdate from pip

then i was reading man ddupdate about files and configurations, and saw that ddupdate first reads $XDG_CONFIG_HOME/ddupdate.conf if variable is defined (with visible file, prone to being accidentally modified/deleted), but if not it falls to ~/.config/ddupdate.conf (should be if actual file exists instead if variable is defined)

so ... what if somebody wants to use another custom path like /opt/profiles/singleuser/ddupdate.config or /mnt/portable2go/ddupdate.ini ? .... after all i think MOST of machines where ddupdate runs are single user boxes (routers, nas, embedded, home servers, small business, etc) .... (can -c <path> option be used in harcoded conf file, a la include?)

---

ddupdate seem installed ok, man pages are displayed, etc... but when i run ddupdate --help this happens

root@elemental:~ # ddupdate --help
-bash: /usr/bin/ddupdate: No existe el fichero o el directorio

things start turn even weirder...

root@elemental:~ # which ddupdate
/usr/local/bin/ddupdate

root@elemental:~ # ls -lF /usr/local/bin/ddupdate*
-rwxr-xr-x 1 root root 341 oct  4 00:16 /usr/local/bin/ddupdate*
-rwxr-xr-x 1 root root 412 oct  4 00:16 /usr/local/bin/ddupdate-config*
-rwxr-xr-x 1 root root 376 oct  4 00:16 /usr/local/bin/ddupdate_netrc_to_keyring*

root@elemental:~ # echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

i made symbolic links in /bin/, but now ddupdate floods my console with large and tangled python error messages... and ddupdate-config also complains me something about keyring package... dunno

why the heck am i unable to run ddupdate fresh installed, and have to make ever more complicated manual researches and fixes everytime???

i am tired