The idea would be to have two package lists:

• A unstable package list, where we could test the release of an app
• A stable package list, when we are sure the app is ready

I think we could couple this with Gitlab CI:

1. We have a unstable branch, where we update the neutrinet_ynh_apps.json
2. This triggers a pipeline which builds the apps.unstable.json and copies this file to the server
3. Once everything is okay, we merge the unstable branch into stable
4. This triggers a pipeline which builds the apps.stable.json, etc.

On the website, we would have the following:

• apps.neutrinet.be/stable
• apps.neutrinet.be/unstable
• neutrinet.be/apps.json -> 302 apps.neutrinet.be/stable

I'm still not sure if this would be feasible. We still need to setup a Gitlab runner to be able to run pipelines, but I'm still unsure how all this would connect to the Neutrinet web server.