frontend issueshttps://gitlab.domainepublic.net/Neutrinet/frontend/-/issues2019-12-09T18:48:43Zhttps://gitlab.domainepublic.net/Neutrinet/frontend/-/issues/3Move Yunohost package list to a dedicated repo2019-12-09T18:48:43ZHgOMove Yunohost package list to a dedicated repoWe should separate files and scripts related to the Yunohost package list to a dedicated repo.
Code in the `frontend` repo isn't used anymore (we use the [Grav website](https://gitlab.domainepublic.net/Neutrinet/site-neutrinet-beta) now...We should separate files and scripts related to the Yunohost package list to a dedicated repo.
Code in the `frontend` repo isn't used anymore (we use the [Grav website](https://gitlab.domainepublic.net/Neutrinet/site-neutrinet-beta) now) and should probably be archived.https://gitlab.domainepublic.net/Neutrinet/frontend/-/issues/2Release Neutrinet app v0.3.0~yhn22019-12-07T17:36:17ZHgORelease Neutrinet app v0.3.0~yhn2HgOHgOhttps://gitlab.domainepublic.net/Neutrinet/frontend/-/issues/1Update Neutrinet app in our Yunohost packages list2019-12-04T17:20:33ZHgOUpdate Neutrinet app in our Yunohost packages listSince the [Neutrinet app](https://git.domainepublic.net/Neutrinet/neutrinet_ynh) v0.3.0 has just been released, we should update our Yunohost packages list.
I see that there are two packages list:
- [apps.json](./apps.json)
- [neutrine...Since the [Neutrinet app](https://git.domainepublic.net/Neutrinet/neutrinet_ynh) v0.3.0 has just been released, we should update our Yunohost packages list.
I see that there are two packages list:
- [apps.json](./apps.json)
- [neutrinet_ynh_apps.json](./neutrinet_ynh_apps.json)
Which one should be updated? Who knows? Who cares? We should probably update both.
In the future, we could just point to HEAD instead of a hash commit, but that supposes the master never contains an unstable package version. That's where we want to go, but we cannot ensure this at the moment.
Before doing the actual upgrade, @ilja and I would like to create a test package list just for testing if the upgrade works.
Finally, we should create a ReadMe explaining how to push the changes to production (or is it automatic?)