So far the packages does not allow that, but that’s probably possible as we do such thing with many others apps.
First I would encourage you to open an issue on the repo for this app, that way, it could be done in a future update. (Even though that app is currently waiting for a new packager)
Unfortunately, authorizing only to read paste isn’t that easy.
I don’t know that app (as I don’t use it myself), but the thing is you have to identify what are the pages that have to be private and the format of the url for a paste.
(Actually having a look on the official demo…)
As far as I can see, there’s no other pages than the root of the app and the pastes.
And all pastes start with a ‘?’
I think you should try with the app public and add
Sorry for my late reply (year end and procrastination…). I tried both.
Curiously, I couldn’t get the second option to work, but the first one (public but blocking root) seems to work just fine. So cherry-picking in your answer, here’s the working procedure:
Should I to install the package check on a yunohost or on my local system ?
Or on my small VPS (4Go / 2 x Xeon Processor 2,1 Ghz, 20 GB free space disk) with yunohost ?
J’ai installé une VM dans Virtualbox avec yunohost vierge avec un snapshot.
Comme je voudrais à terme pouvoir contribuer - tester des futurs paquets avec le process, je voudrais tester l’utilisation de package_check.
Par contre, ce n’est jamais clair sur le lieu de lancement des commandes et par qui ?
Je fais tout avec admin pour l’instant tant que je n’ai pas d’erreur…
J’ai cloné le dépot package_check et lancé le build :
Et après de nombreux tests automatique, j’obtiens :
Package linter: SUCCESS
Installation: SUCCESS
Deleting: SUCCESS
Installation in a sub path: SUCCESS
Deleting from a sub path: SUCCESS
Installation on the root: SUCCESS
Deleting from root: SUCCESS
Upgrade: SUCCESS
Installation in private mode: SUCCESS
Installation in public mode: SUCCESS
Multi-instance installations: SUCCESS
Malformed path: SUCCESS
Port already used: Not evaluated.
Backup: SUCCESS
Restore: SUCCESS
Change URL: SUCCESS
Actions and config-panel: Not evaluated.
grep: /home/admin/package_check/levels.json: Aucun fichier ou dossier de ce type
Level of this application: 7 ()
Level 1: 1
Level 2: 1
Level 3: 1
Level 4: 1
Level 5: 1
Level 6: 1
Level 7: 1
Level 8: 0
Level 9: 0
Level 10: 0
You can find the complete log of these tests in /home/admin/package_check/Complete.log
Global working time for all tests: 15 minutes, 39 seconds.
Disable iptables rules.
Disable the network bridge.
While having docs is nice, I’m afraid though that if there’s a doc here, not done by the packagers, they may never update it. Not knowing it even exist.