And again, cf. the Debian 11 testing thread, just keep it simple and use YunoHost’s own image and upgrade it. It’s two commands away after post-installation.
Once I have re-done all of my plans, which currently show me as having to install Debian 10 instead of Raspbian; and my GitHub workflow currently showing me as installing v22.214.171.124 instead of v126.96.36.199; then I will do the “two commands away after post-install”. Sorry, I have been trying very hard to get this right the first time, and following all of the instructions that I receive, to the letter. This is a major project for me, and not something that is going to get completed in five minutes. A lot of careful thought and planning has gone into my project. I document everything meticulously. I am on the Autism Spectrum, and this is just how I do things. “Overthinking things” is what I do best!
Understood. To summarize, regarding your RPi, there are two options, by my order of preference:
- Use YunoHost’s out-of-date 4.1 image for Raspberry Pi, perform the post install and upgrade your system. Adds around 5 minutes to your workflow.
- Use Raspbian 10 image (again, sorry for suggesting pure Debian and waste your time), and use YunoHost’s installation script (with the
curl ... | bashcommand from the documentation). Brings you directly to current 4.3.x version, but the installation script would take noticeably more time.
End result is strictly the same though.
Thanks, this Debian / Raspbian issue has sent me down a rabbit hole, and now I need to dig my way back out. I’ll probably take another day just to re-jig all of my plans, to set me back onto my original path of installing v188.8.131.52 first, which is what I had tried previously, some 14 days ago with my initial test install of YunoHost. Unfortunately, that upgrade failed rather spectacularly, which is why I was hoping to jump straight to v184.108.40.206 without having to do an upgrade.
I have re-written my first milestone for this project. The due date remains the same.
I just need to get this one last procedure documented, then I’ll be ready to prepare “the µSD-card for YunoHost v220.127.116.11”.
I still have some preparation work to do on this project. From what I understand, I won’t be able to actually start the installation of my
test environment anyway yet, until my reset request has been actioned. I am re-installing the
test-fmds.noho.st domain. I had previously set up that domain just for assessing YunoHost’s features before settling on this project plan. That installation has since been deleted.
Your detailed step-by-step may be quite helpful for a fully comprehensive documentation, thank you for that.
Rabbit hole warning ahead!
I just came across this new post on the Raspberry Pi Stack Exchange, which discusses performance of LUKS encryption using the Adiantum cipher on a Raspberry Pi 4. Also in the same thread was a link to this guide “that explains how to encrypt the SD card of a Raspberry Pi to use LUKS with Adiantum”.
This is an idea for me to pursue later, probably under a future project, such as FMDS2024.
By the way, the word Adiantum is actually taken from real-world biology, not from the fictional geology of James Cameron’s “Avatar” movie, as had been suggested in the SE thread. It seems also that I have a personal connection to Adiantum, as it is the scientific name of the native New Zealand (where I live) maidenhair fern, one specimen of which my wife and I received as a wedding present, many years ago. Sorry, that should have been prefixed with a “useless trivia” warning too, hahaha.
Thanks for that @tituspijean. Being that I’m autistic, I tend to use a very formal and well-defined vocabulary, by nature. I am pedantic and I used to be a “grammar nazi” back in the day, correcting everyone else’s mistakes. Now I just concentrate on fixing my own mistakes, which, to me, stick out like a sore thumb. If my self-documentation here or elsewhere can be recycled into documentation for the YunoHost project itself, then I’ll be very happy to help with that. Everything I post is released under the lesser of a CC0 license, or the default license of the forum / site that I am on at the time.
I’ll take up the glove
rsync is a bit off topic in the other thread, let me put it here.
What do you want to back up?
For a backup of the (whole) Debian installation on the SD-card, rsync is less suitable. For that you’d use imaging software. If the goal is ‘minimal fuss, get it backed up till Archivist/Borg is installed’, I’d shut down the server for ten minutes and
dd the whole SD-card to the project / backup directory on my workstation.
If the goal is to sync a specific part of the running Debian installation, it works quite straight forward. On your workstation:
$ mkdir -p /home/frittro/yunobackups/backup1/ # or another place of course $ rsync --progress -a -e ssh frittro@fmds:/home/ /home/frittro/yunobackups/backup1/ $
Source is on the other side of ssh, destination is in the directory on your workstation you reserved for it.
The command is very straight forward, give it a try copying something from one directory to another directory on your workstation (in that case you can still use SSH, but you can also omit the
-e ssh frittro@fmds:-part to make a local copy)
Great advice, thanks so much for that. I had been reading elsewhere that a
dd image is not a great solution, but it is what I already knew how to do. I thought
rsync would be the better solution in this case, but it seems that my initial gut reaction was the correct one this time. Thanks so much for clarifying that. I’ll go back to using
dd for now then, until I get Borg Backup installed and working.
I’ll get back into the swing of things here next week. I’m glad that I left an extra week before my first milestone is due! My attention has shifted to organising a memorial service for my mother-in-law, who passed away last year during our COVID lockdowns. Next week I’ll begin the actual YunoHost v18.104.22.168 install on the
test Raspberry Pi.
EDIT: It was a lovely afternoon today at the memorial service for Mum. I came home completely tired out (being on the Autism Spectrum, such live social interactions always tire me out), and will be taking tomorrow to recuperate. On Monday I’ll begin my installation of YunoHost, for real!
There is another holdup before I start installing YunoHost. I want to blog about my install as I go, but I also want to earn cryptocurrency from my blog posts about it, so I am creating an account on Hive, which is the new blockchain hardforked from the old Steem blockchain. I’ve hit a little snag with that part, and am just awaiting some advice from the Hive team.
EDIT: Below is a sneak preview of the title image of my first post about YunoHost, on Hive…
EDIT: My Hive account is now live! If anyone is interested, you can follow my blog there, using any HIVE blockchain viewer. I personally prefer Ecency, but any HIVE viewer will work. If you like my content, and if you have your own account on HIVE, please vote me up! It doesn’t cost you anything, but it will get me some cryptocoins for my effort. That is how HIVE works.
Okay, I have got my intro blog post created on the Hive blockchain at last. Now I can concentrate on installing YunoHost itself. I have about three days left before my first milestone is due! It is gone 4am here, so I need some sleep and then I’ll get started on installing a little later. I’m ready to go, and to blog about it as I do, and to earn a bit of crypto from my blogging effort as well.
News items like
make me shiver thinking about the banality of converting that much perfectly usable green energy into waste heat.
The Hive operation at only this plant converts as much energy as my whole family uses per year, into heat in less than 300 seconds!
That is a relief
I am so far behind on my schedule for my install project, but here is my first post on the Hive blockchain about installing YunoHost on my Raspberry Pi. This post is only about getting to the stage of putting YunoHost v22.214.171.124 onto the µSD-card so far, but it is a start. Hopefully my blog series will eventually provide complete step-by-step instructions for what I am doing with YunoHost.