as well with shell in order to be able to run duniter with systemd
So, the configuration get saved in (/home/yunohost.app/duniter) $datadir
with which the service will run with
The consequence of this was at least a broken BMA access due to the
absense of configuration
Run Duniter with 'duniter' user to apply the configuration
to get the config file with correct permissions, using
"ynh_exec_as duniter", an equivalent of su - duniter -c "$cmd"
Upgrade from the state before the refactoring
from 1.8.1~ynh0 to 1.8.2~ynh1
Move Duniter home directory to the YunoHost App path
Check if the destination exists, meaning it’s not running < 1.8.1~ynh1
then run the datadir move
Package_check: Add upgrade check from commit before the refactoring
Requires YnH v4.1 which implements this new permission system
Use ynh_permission_create helper
Set Duniter admin interface accessible to the selected admin
BMA is set as accessible to visitors by default
Remove / −> /webui redirection, since this change adds a tile to the admin
Remove deprecated permission system settings
Re-enable the web admin since it is protected again
Rename f() name
- install, upgrade: protect the path and grant access to admin user.
- upgrade: forget to comment unused sed.
- Update readme: add information about webadmin on root path.
- Disable set -u because of unbounding variable on $nginx_conf
- Retrieve domain and path arguments
- Remove trailling "/" on path var
- Grant access to /duniter path on the SSO
- [fix] do not move in /twp directory. Manage Debian package from current directory.
- [enh] add 'set -eu' in install and update scripts. Remove it from remove script.
