Just curoius to know if there is any plan to revamp the IPFire GUI, thanks.
That is the aim for IPFire 3 but progress on that is slow because the Core Devs team on IPFire is quite small and important issues have to keep being worked on with IPFire 2.
“UNOFFICIAL MODIFICATIONS, USE AT YOUR RESPONSIBILITY!!!”
Hi. May be this help you.
I use “houseofdreams” theme.
Regards.
I think it needs to be mentioned that you should always be very wary of installing unknown files into your Firewall.
@roberto , I think you should also mention the problems you experienced with the graphs and the changes you had to make to the provided files to get them to display properly.
https://community.ipfire.org/t/theme-for-ipfire/2687
It is true. You have to be careful about it. Looking at the code (I’m not an expert) it looked reliable. It would be necessary to add “UNOFFICIAL MODIFICATIONS, USE AT YOUR RESPONSIBILITY!!!”.
The graphics, the solution was simple, adding that code at the end.
Thanks for the note Adolf .
Greetings.
Yes, I also think that the user interface is quite outdated and needs an overhaul…
I’d like to give this thread a little bump as I just received the “December is Party Season!” newsletter with 2024 announcements.
You guys do a really good job from the technical/security perspective. But the GUI/web interface needs an urgent make over. Other projects look more like they are from this decade. IPFire is still lagging behind. Have a look at Proxmox, Unraid, OpenWRT, TrueNAS, pfSense etc.
Can this perhaps be crowdfunded? In general, donating to a specific cause might not be a bad idea for many community members.
The WUI for IPFire-2.x will not get re-worked, except to fix bug or security issues. Some new functions, such as the IP Blocklist have been added.
The main focus is on IPFire-3.x
The work this year has been on getting the IPFire-3.x Pakfire build system working.
We now have a build system that is working, although there are some bugs being worked on with regard to the jail aspect of the build as this periodically ends up stopping a build.
You can see the work done on the pakfire build system by looking at the commits raised.
https://git.ipfire.org/?p=pakfire.git;a=shortlog
In terms of the IPFire-3.x build you can see the commits done for this so far
https://git.ipfire.org/?p=ipfire-3.x.git;a=shortlog;h=refs/heads/master
When the pakfire builder major bugs have been dealt with then the next step will be to start working on the Network structure of IPFire-3.x, which has been indicated to be an easier job than the creation of the build system was.