Sharing your extension
To share an extension, you need somewhere to host it.
If you only want to use your own extensions in your own projects and distribute them with the packager, you do not need to host or submit anything. The packager always bundles and runs extensions unsandboxed as part of the exported project.
Sandboxed extensions
A sandboxed extension can be hosted anywhere that serves static files over HTTPS. GitHub Pages is a common choice. Note that GitHub's raw.githubusercontent.com links do not work as extension URLs; use GitHub Pages (or another static host) instead.
Once it is at a public HTTPS URL, load it in the editor with "Add Extension", "Custom Extension", and the URL, or auto-load it with ?extension=<url>.
Unsandboxed extensions
An unsandboxed extension only runs unsandboxed automatically from a trusted origin (see the trusted prefixes on the unsandboxed page). Since you do not control those gallery domains, the practical options are:
- Host it yourself and let users opt in. Serve it at any public HTTPS URL as above. When someone loads that URL, Bilup loads it sandboxed unless they explicitly choose to trust it, so document that step for your users.
- Get it into the Bilup extension gallery. The gallery lives at extensions.bilup.org; extensions served from that origin run unsandboxed automatically. Follow the submission instructions on the gallery site itself.