Well, when you do a local install it's much easier to deal with when there's an issue. There's a one liner in that medium link to reset the PW when in doubt. Running updates is another one liner. I use SecureCRT for everything and script out buttons to hit when something is needed routinely which speeds things up a bit.
If you don't want to pay for a terminal client there's one built into Linux but it's not robust by any means.
SSH >> box >> CLI update pihole
This is typical flow but, these damned images/containers sometimes make things difficult to get things done. It would help if there was a simple button in PH to update things but, it's all scripted in the CLI. I suppose you could manually DL the update files from GIT and drop them into the folder and restart the VM to apply them. Maybe using something like WinSCP would allow you to login to the container to swap the updates into place.
If you don't want to pay for a terminal client there's one built into Linux but it's not robust by any means.
SSH >> box >> CLI update pihole
This is typical flow but, these damned images/containers sometimes make things difficult to get things done. It would help if there was a simple button in PH to update things but, it's all scripted in the CLI. I suppose you could manually DL the update files from GIT and drop them into the folder and restart the VM to apply them. Maybe using something like WinSCP would allow you to login to the container to swap the updates into place.