standardnotes-extensions
standardnotes-extensions copied to clipboard
Standard Notes Extensions
Standard Notes Extensions
Features
- Updated daily (GitHub Actions using
schedule) - Contains Official and custom extensions
Suggest new extensions
Open a Pull Request to add new extensions.
Alternatively, open an Issue to suggest new extensions.
Usage
Option 1: Use default URL
Use https://standardnotes-extensions.netlify.app/index.json as an Extended Code in Standard-Notes.
Option 2: Fork & Use custom URL (with Netlify)
- Fork this repo benjaminjacobreji/standardnotes-extensions
- Sign-in/ Sign-up into Netlify
- Click on New site from Git Button.
- Connect to GitHub and select forked repo
your-github-username/standardnotes-extensions - Deploy site and wait for build to finish
- (Optional) Change Site name at
Site settings > Change site nameon Netlify - After that you can use
YOUR_SITE_URL/index.jsonas anExtended Code
Option 3: Fork & Use custom URL (without Netlify)
It's easy and recommended to host with Netlify. However if you insist not to use it, it is also possible (notice: the following steps work on Linux or WSL):
- Prepare your environment with
Python 3.7withpip, as well asGit; - Make sure Python 3.7 can be called directly via
pythonfrom the shell; - Make sure Git is installed and can be called directly via
gitfrom the shell; pip install -r requirements.txtto install required Python libraries;- Run the build script
URL=my_url python build.pywheremy_urlis the full URL you would later host the resource files on. E.g. if you want to access the plugins viahttps://example.com/index.jsonthen replacemy_urlwithhttps://example.com/. - Verify that:
- the
publicdirectory is generated; - there should be
public/index.jsoncontaining information of all extensions; - all extensions should exists in
publicas sub-directories;
- the
- Host the
publicdirectory like you would do with any static resources, using nginx, caddy, etc. - You need to enable CORS headers on your reverse proxy (nginx / caddy / traefik). With nginx these rules will be enough:
add_header 'Access-Control-Allow-Origin' '*'; add_header 'Access-Control-Allow-Headers' 'content-type';
Credits
Huge thanks to all these contributors and other authors.