Good morning Fedi friends!

[elena@aseachange.com]

Update:

I sent the toot with a link to my self-hosting guide (installing NextCloud via YunoHost) three hours ago… and I haven’t received any scoldings / complaints by sysadmins yet (about potentially idiotic things I could have written). I consider my morning a success 🤪

#YunoHost #NextCloud #MySoCalledSudoLife #SelfHosting

[patpro@social.patpro.net]

@elena It’s friday, every SysAdmin is really busy preventing Devs from putting new thing in production before leaving for the week end.

[nathan@ublog.hurel.me]

@elena@aseachange.com btw I've recently added [anubis](anubis.techaro.lol) in front of my nextcloud instance. Did you try it ?

[elena@aseachange.com]

@patpro 😂​😂​😂​💀​

[elena@aseachange.com]

@nathan ooooh amazing! And no, I haven't tried it yet... looking into it now

[patpro@social.patpro.net]

@elena Joke aside, I’ve read about half of it and see nothing to compjain about as a SysAdmin ;)
One thing that could make it even better: I’m a huge fan of documentations that explain why before how. I think it would be a great addition if you could add 2 or 3 lines at the beginning of each steps to tell your reader why she’ll have to follow those steps.
See for example step 1, you dive into the how right from the start and it’s only after 5 sub-steps and 5 corresponding screen captures that you explicit the why «When the process completes, your new subdomain - which you will use for NextCloud - should appear in your "Domains" list.»
It would benefit the reader to know why she clicks and where it goes, before actually starting. Also, it helps planning ahead: «should I start now if I can’t even decide for a subdomain? (because I want to talk about it with family, because I want to sleep on it, whatever)».

Great job anyway, it’s great and helpful as it is.

[elena@aseachange.com]

@patpro thank you for the note ! Super helpful and I wish I had thought of it before, sigh. I will definitely keep this in mind for future tutorials

[nathan@ublog.hurel.me]

@elena@aseachange.com sorry for changing your afternoon plans 😅
I can share my config rules to not break mobile apps if you need to, when you have it ready

[en3py@onlyarts.social]

@elena @patpro I miss the good old days where howtos were commonly written. Personally, I love the format and clarity of the guide... for a "newbie guide", it is pretty high standard.

I would suggest a future update with some security tips: like adding fail2ban to your web server configuration (and lookups with 400 error codes). If you need the scripts and the why-hows, feel free to drop a line: happy to share.

[elena@aseachange.com]

@en3py @patpro thank you Sebastian. I will write about security in the next installment. As a heads-up, upon installation, YunoHost automatically sets up Fail2Ban in the background and removes root access!

One time I couldn't figure out how I couldn't get onto a test VPS with Terminal... I reset/changed passwords 3 times... and then I remembered YunoHost disables that functionality to strengthen security right off the bat

[elena@aseachange.com]

@nathan sadly it's a little too advanced for me. I need an Anubis for dummies guide, LOL