If you have no monitor or keyboard access to your Orange Pi 5 then you will need to use the serial console connection approach. See this wiki page on the serial console.
As the Orange Pi 5 is not listed in the ARM page on systems that users have installed IPFire on, it may or may not work. However the best way is going to be to try it and see.
Installation of an OS on a HW board means, you have to use the basic user interface. Other interfaces are defined and configured by the installation.
The basic interfaces are
serial, low demands and well developed over many years
keyboard/video/mouse, well known through the ‘standard’ desktop systems
raspbian-install or armbian-install do a basic configuration of the OS image on the SD card. This is running on some other system with some other OS.
To achieve this with IPFire, a bunch of installer programs would have to be supplied and maintained.
The IPFire install process adapts more to the small dev team. The team can focus on development of the OS.
Each system has some sort of console and boot loader ( supplied by the BIOS or board support package ). Using only these is an easy and reliable way to install the OS.
But you are free to develop some tools to adapt the images for your needs. If the solution is safe and interesting for other users, you can upload it by the known ways for development ( to be found in the wiki ).
I would be nice if you can fix something so the IP fire os is installed on nvme drive and the boot loader on spi flash so we don’t need a crappy sd card.
You may want to take a look at FireMyPi on github. My brother and I built it to configure headless IPFire installations for our family network on the Raspberry Pi. It uses udev to automatically configure red0 and green0 based on the drivers used for the Pi onboard nic and common nic dongles so running setup is not needed. I’m not sure what chipset for the nic the Orange Pi’s use so you may need to tweak that part of the code for the Orange Pi, but we use it to build custom IPFire core images and burn them to micro sd to boot our Raspberry Pi’s which are all headless.
Yeah, as @bbitsch mentioned, on the github page, it shows the un-rendered html, you would need to download the html and drop it into your browser. There is a release on the repo page that has everything in it. If you download that and look in the doc directory the manual is there.
Regards,
Stephen
Edit: Actually you want to have the whole doc directory to load the admin guide from because there is also a css there that is needed for the page to render correctly.
FireMyPi does just what you want, I think.
Configuration of the OS outside the target HW. Maybe it is not as comfortable as you dream of. But doing these steps separate gives you more knowledge of what you do.
IMO, you’ll not find a windows ‘clicking’ solution.
BTW, people are screaming for ARM firewalls because they think the ARM architecture is less used than Intel/AMD ( by bad guys ) and Raspberry Pi is just a board for low money. That’s all.