neutrinet_ynh issueshttps://gitlab.domainepublic.net/Neutrinet/neutrinet_ynh/-/issues2020-03-01T20:52:26Zhttps://gitlab.domainepublic.net/Neutrinet/neutrinet_ynh/-/issues/16Move master -> stable and develop -> unstable2020-03-01T20:52:26ZHgOMove master -> stable and develop -> unstable* [x] Create new branches (stable and unstable)
* [x] Freeze old branches (master and develop) so that nobody can merge there
* [x] Update documentation about contributing (change branch name)
* [x] On next release, change the target bra...* [x] Create new branches (stable and unstable)
* [x] Freeze old branches (master and develop) so that nobody can merge there
* [x] Update documentation about contributing (change branch name)
* [x] On next release, change the target branch in the apps list (see https://gitlab.domainepublic.net/Neutrinet/apps/issues/2)
* [x] Once everything is done, delete old branchNeutrinet v0.3.0~ynh5HgOHgOhttps://gitlab.domainepublic.net/Neutrinet/neutrinet_ynh/-/issues/15Add script to move domain/path2020-02-29T11:21:54ZIljaAdd script to move domain/pathThis is probably nothing more than changing the nginx file. Technically people can uninstall and install on the new domain/path, but having a script to move will be quicker/easier for the user.This is probably nothing more than changing the nginx file. Technically people can uninstall and install on the new domain/path, but having a script to move will be quicker/easier for the user.Neutrinet v0.3.0~ynh5HgOHgOhttps://gitlab.domainepublic.net/Neutrinet/neutrinet_ynh/-/issues/14Add way to add list and install from Admin-interface2020-02-29T11:21:53ZIljaAdd way to add list and install from Admin-interfaceWe removed this from the readme because we couldn't add a list from the admin interface any more, but I think it just moved to somewhere else. Check it and add to readme.We removed this from the readme because we couldn't add a list from the admin interface any more, but I think it just moved to somewhere else. Check it and add to readme.Neutrinet v0.3.0~ynh5HgOHgOhttps://gitlab.domainepublic.net/Neutrinet/neutrinet_ynh/-/issues/13Improve /neutrinet webpage2020-02-29T11:21:54ZIljaImprove /neutrinet webpage1. The links are now in bold. This isn't a typical thing to do, so it's not intuitive. These should be either another colour or underlined. Since Neutrinet doesn't really have a 'main' colour, I'd use underlined instead of bold.
2. There...1. The links are now in bold. This isn't a typical thing to do, so it's not intuitive. These should be either another colour or underlined. Since Neutrinet doesn't really have a 'main' colour, I'd use underlined instead of bold.
2. There is Javascript loaded which isn't used. It looks like this was part of a framework-like thing together with the css. The Javascript should be removed.
3. Add a translations for Dutch. The prefered way is probably to have a second page for Dutch and a link on the pages to switch from fr to nl. The default an remain fr.
* If this proves too difficult, maybe it can be easier to have both translations on one page (but let's try to not go this way).
* If this doesn't prove to be difficult enough, we can also see if we can have nginx load the nl/fr page in case nl/fr preference is detected from the browser. Fr should still be default.Neutrinet v0.3.0~ynh5IljaIljahttps://gitlab.domainepublic.net/Neutrinet/neutrinet_ynh/-/issues/10Use Yunohost progress bar2020-02-29T11:21:53ZHgOUse Yunohost progress barThat'd be very cool to use the Yunohost helper `ynh_script_progression` that displays a progress bar during the install / upgrade :smiley_cat:
If we go for it, we'll have to update the min requirements to Yunohost v3.5.0 in the `manife...That'd be very cool to use the Yunohost helper `ynh_script_progression` that displays a progress bar during the install / upgrade :smiley_cat:
If we go for it, we'll have to update the min requirements to Yunohost v3.5.0 in the `manifest.json`Neutrinet v0.3.0~ynh5HgOHgO