@SansGuidon said in Some struggles with Cloudron migration:
pebkac
What?
Googling . . .
PEBKAC stands for "Problem Exists Between Keyboard and Chair". It's a tech support term, often used humorously or dismissively, to indicate that a problem is caused by user error rather than a technical issue. In essence, it's attributing the problem to the user's actions or lack of understanding, rather than a software or hardware malfunction.
AHHHHH! I know the German version "Das Problem sitzt vor dem Bildschirm" litteral translation "The problem is sitting in front of the screen".
Nice one
@SansGuidon said in Some struggles with Cloudron migration:
it makes actually sense to refresh the guide reader about the network requirements
Good point! Just a "remember your Network setup!" with a link to the other doc would be enough. Right?
@SansGuidon said in Some struggles with Cloudron migration:
Also maybe not everyone is willing to rely solely on Cloudron config for the security. Hetzner gives lot more power to users and control, and Cloudron sometimes feels a bit too vague.
Let me be brutally honest with you. German mode enabled.
99% of users that use Cloudron do not have the knowledge and experience to proivde that.
What Cloudron provides is enough for the 99%.
Generally speaking, not targeted towards you.
IMO everything further is "expert mode" and the expert should know what to do.
And if the expert does not know how, he should either learn or pay.
@SansGuidon said in Some struggles with Cloudron migration:
As a power user (DevOps) and busy dad, Cloudron feels both nice or confusing/limited at times depending what I want to do
I get that
That is the gilded cage experience and to some extent necessary to keep support low.
If you are working in DevOps, I've built multiple customer solutions with Cloudron, Cloudron Gitlab, Cloudron DockerRegistry and the Gitlabrunner to fully automate, development, staging and production deployments.
It is possible, but you need a firm grasb on what Cloudron does and how it does things.
Then you can make it do some crazy things.
@SansGuidon said in Some struggles with Cloudron migration:
The mounts issues errors were for most related to network. The message must be clearer.
Error message improvment. Everyone can benifit from that.
Should there be a normal message with a button "more details" for power users like you and me?
@SansGuidon said in Some struggles with Cloudron migration:
I could use Hetzner for DNS but we have already a long term subscription with Hostinger for several domains so we are anyway still stuck a bit. Also I could argue that putting all my eggs on same provider is risky. I had an outage with Contabo in the past where both VPS and Backups location were impacted. this kind of situation is a pain in the ass.
Egg Basket, agreed. If not Hetzner, some other supported DNS provider that fits your needs so you get rid of the manuall labor? => https://docs.cloudron.io/domains/
My top picks in no order are:
https://desec.io/
Cloudflare
Hetzner
DigitalOcean
@SansGuidon said in Some struggles with Cloudron migration:
And I wanted to contribute this thread in the hope to open a debate about this and improve the overall experience.
Yes please! Always and more of that.
What ever you find that is "meh", report it in the forum. Everyone benefits.
S
