Publish your app
Apps, plugins and extensions all publish the same way. Your files stay on GitHub; the hub checks every version and lists it.
Sign in
Sign in with your GitHub account. The hub asks only for your public profile and the organisations you belong to.
You are signed in as .
Accept the agreements
Read each one and accept it once. When one changes, you accept the new version before your next release.
Contributor Agreement
You keep your work and let the hub list it. Read it on its own page.
You accepted version .
Publisher Agreement
What you promise about the files you publish, and what the hub does when someone reports one. Read it on its own page.
You accepted version .
Link your repository
Pick who publishes: you, or an organisation you own on GitHub. The id of your listing starts with that name and a dot, like
alice.notes. The repository must be public and belong to the same person or organisation.Organisations
is linked.
is yours on GitHub.
(you)
(organisation)
Linked. is linked to
A tag on GitHub publishes
Push a tag and publish a release on GitHub with your file attached. That is all: the hub notices it, checks the file and lists it within about fifteen minutes.
git tag v1.0.0 git push origin v1.0.0 gh release create v1.0.0 alice.notes-1.0.0.wolEach version is checked on its own and gets its own signed statement. Follow it on your dashboard: checking, listed, or flagged with the reasons in plain words.
Sign your releases
A certificate puts your name on every file you publish, and WolOS confirms it on every PC, even offline. Without one, your listings show "Community".
Origin certificate
Shows who made each file and from which repository. The hub issues it by itself once you accept the agreements.
You have none yet. Ask for it below.
The hub has your request and is issuing the certificate. It shows here when it is ready.
Issued on . Your releases say "From" your name, account and repository.
Revoked on . Files signed with it are withdrawn. Make new keys and ask again.
Serial
Trusted developer certificate
For developers and organisations WolOS Hub verifies by hand. Your listings then say "Trusted developer" with your name.
Apply below once your origin certificate is issued.
The hub has your application. A person from the hub reads it and may write to you on GitHub.
Issued on .
Not given. You can apply again.
Revoked on . Your listings show your origin certificate again.
Serial
Ask for a certificate
- On your WolOS PC, open a terminal and run this. It makes your keys, locks them with a passphrase you choose, and prints a request.
wol cert request- Paste everything it printed, choose the certificate and send it.
Paste the whole request, from the first line to the last, as the command printed it.