-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Supportting other distros #9
Comments
Hello Ramon, Do you think will work if i enable yum packages on debian and reinstall everything from yum repositories ? |
Hi. You can basically install https://github.com/RamonGiovane/guiptables?tab=readme-ov-file#using-the-source-code |
This is the steps i have followed to have step by step setup on Debian 12. Please publish on your next documentation. sudo apt install iptables Since iptables require root login:
|
Version 1.4 now supports access for non root users. https://github.com/RamonGiovane/guiptables/releases/tag/1.4.0 |
I've tested Cockpit on non-RHEL-like systems and it works very well.
So as long as Cockpit is running in a distro and it has iptables, I think guiptables is good to go.
The problem comes when we need to install iptables within guiptables, as RHEL-like systems use yum and other distros has different package mangers.
For this I can think in two options:
settings.json
and then the code identifies the right command to call. A release.deb
package would haveapt
configured by default, and so on...But on second tought, I don't know if it's worth the effort. There's currently no other task to package managers here besides installing
iptables
if it's not installed.That is the only code related thing I see that would impact supporting other distros.
Besides that, the really challenge would be writing the scripts to create release packages. From my experience with
.rpms
, it wasn't as easy how I thought it would be.The text was updated successfully, but these errors were encountered: