Hey guys, I've been working on the admin branch for the PiPass admin panel. We are using a SQLITE database, and the install script clones the default SQLITE db from GitHub into /opt/pipass/pipass-DB.db. /opt/pipass/ might also become the new home for configuration files.
Remember that we have the .ini functionality to save configurations between upgrades? That file would be stored in that directory, while config.php would remain where it is. This would ensure for a smooth upgrade between versions, even if we, for example, add a new directive to the config file. That's because the .ini file (thank you @yoinx ) is an addon to the configuration file, and is not required.
I just wanted to let you know on what I'm working on now. Hoping to release PiPass v1.3.5 sometime this week after I improve and test the update script.
Hey guys, I've been working on the
adminbranch for the PiPass admin panel. We are using a SQLITE database, and the install script clones the default SQLITE db from GitHub into/opt/pipass/pipass-DB.db./opt/pipass/might also become the new home for configuration files.Remember that we have the
.inifunctionality to save configurations between upgrades? That file would be stored in that directory, while config.php would remain where it is. This would ensure for a smooth upgrade between versions, even if we, for example, add a new directive to the config file. That's because the .ini file (thank you @yoinx ) is an addon to the configuration file, and is not required.I just wanted to let you know on what I'm working on now. Hoping to release PiPass v1.3.5 sometime this week after I improve and test the update script.