In the current config, the disk usage is only refreshed during
PirateBox start or via Button. With that adjustment we create a
bit more load, but the usage is refreshed better.
If a content folder is already available, the symlink pointing to
that folder is not created. This results in an issue that
upgrades from 1.1.x to 1.1.x end up in a redirect loop in the
browser.
Droopy always does the chmod operation, if the option is set.
On partitions with FAT it is not possible to execute this operation.
Droopy may ran into issue in that situation.
With that fix, the option won't be set on droopy start to prevent
any chmod operation on FAT partitions.
Fixes#154
- Per default we now collect all DNS requests even not the
one which addresses us directly (like 8.8.8.8 )
- Disables is an all Port 80 catch
Fixes: #137
The minor 1.1.0 release is transfered into 1.0.7 release
because the changes are smaller then like adding PHP as
a feature.
As it hopefully does not break any compatibility, we are
integrating this as a small bugfix release.
[New] Improved styling for droopy iframe. (not applied)
[New] Timesave script service file to run set the time during startup.
[Fix] Droopy call in init.d/piratebox failed to use the correct port.
[Fix] Timesave script behaviour fixed on full Linux systems. OpenWrt's date format is now customized during build & piratebox.conf .
* Delivered the systemd file for restoring the file during boot.
* Moved date format to piratebox.conf
* Customize the date format for OpenWrt during build of
piratebox_ws-img.tar.gz file, like other configuration files
The problem is, that the piratebox starts before resetting the
RTC to a saved timestamp. That means the shoubox-gen file
is from the year 1970. That breaks the refresh in the browser.
With the delay, we hopefully get a better timestamp and fix
that issue
Fixes#120
Matthias Strubel
Lars Bartschat
Chris L