[go: up one dir, main page]

Menu

#87 Webconf cannot edit some package config files (B-uC 5.0-beta2)

Bering-uClibc 5.1.0
new
nobody
None
Packages
minor
4.3.3
defect
2021-03-07
2013-05-09
No

The following package config files are listed in webconf but cannot be edited there - it says "That is not a file listed in the configuration file list. You may only edit configuration files from the web interface." However the same config files can be edited by lrcfg:

- easysra.lrp
- iptables.lrp
- openvpnz.lrp (edits /etc/default/openvpn , but not /etc/openvpn/*.conf)

Discussion

  • KP Kirchdörfer

    KP Kirchdörfer - 2013-05-13

    There are two reasons:

    1) descriptions are missing (iptables, easyrsa) - added for upcoming version; note lrcfg doesn't need descriptions

    2) while lrcfg works well with wildcards (etc/openvpn/*), webconf doesn't.

    To summarize: webconf needs to be improved.
    Unfortunately a web-based configuration has been discussed from the start of the LEAF project more than ten yrs ago, but once a framework has been provided, nobody stepped up to maintain it :(

    I'll keep the ticket open for a while, maybe someone will look into webconf to fix the real issues.

     
  • Erich Titl

    Erich Titl - 2021-03-06

    I would not go as far as to blame webconf. It is rather the incongruity of config packages which has never been addressed proberly neither in linux nor in LEAF. A few years back I proposed that the webconf code needs to be included in the package code, e.g. someone responsible for the addition of a package would also be responsible to maintain the webconf code needed to configure that package. It was not well received.

     
  • KP Kirchdörfer

    KP Kirchdörfer - 2021-03-07

    The point is:

    Either webconf or the openvpn webconf setup misses the capability to edit "unkown" configuration files (/etc/openvpn/*.conf - can be everything) while lrpkg.conf does.

    Blaming an (openvpn) packager is no solution.

     
  • Erich Titl

    Erich Titl - 2021-03-07

    Nobody wants to blame an openvpn developer, but blaming an openvpn integrator is a legitimate possibility. After all this is then a LEAF package.

     

Log in to post a comment.