@Sparky sounds like something @fuchsiii would find cool.
Personally, I just wished for a "simpler config managment" without #cringe aka. #YAML.
/configs/$FQDN/$PATH with merely a hosts.tsv to index the $FQDNs against IPv4/IPv6/MAC & literally putting the configs in their $PATH (i.e. /etc/https/httpd.conf) as on the machine so all one needs to do is to basically #rsync from main branch onto the target machine?This would literally require zero installation on the target machine (one could rsync -av the previous config files into a new git branch to make backrolling easier!) and it would not need any stored secrets as well as allow for the people maintaining and the people controlling to he different persons!
Anyone know someone at #JetBrains to report a #PyCharm #issue to?
Basically it's a #softlocking that happens on the #snap version of #PyCharmCommunity / #PyCharmCE that makes it somehow half-forget #credentials like #GitHub, #Gitlab, #Codeberg, #BitBucket, #Gitea, #git etc. and not allowing to just delete & re-add them as the settings saving just becomes unresponsive.
$HOME/.config/PyCharmCE****/... and randomly coming back after a few days or weeks.Whether this also conflicts with #SettingsSync which should only sync #configs, not #credentials (and AFAICT doesn't!) is also a question I can't confidently answer.
#Hackers leak #configs and #VPN credentials for 15,000 #FortiGate devices
A new hacking group has leaked the configuration files, IP addresses, and VPN credentials for over 15,000 FortiGate devices for free on the dark web, exposing a great deal of sensitive technical information to other cybercriminals.
Use the appropriate solutions.
#Volumes are automatically allocated and managed on chosen storage providers.
#Configs allow you to distribute read-only configurations in complex environments, possibly with specialized tools.
#Secrets are like configs, but with extra security. It can also be integrated to secrets managers.
[2/4]