Skip to content

cabaseira/standardnotes-extensions

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

108 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Standard Notes Extensions

Netlify Status

Features

  1. Updated daily (GitHub Actions using schedule)
  2. 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)

  1. Fork this repo benjaminjacobreji/standardnotes-extensions
  2. Sign-in/ Sign-up into Netlify
  3. Click on New site from Git Button.
  4. Connect to GitHub and select forked repo your-github-username/standardnotes-extensions
  5. Deploy site and wait for build to finish
  6. (Optional) Change Site name at Site settings > Change site name on Netlify
  7. After that you can use YOUR_SITE_URL/index.json as an Extended 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):

  1. Prepare your environment with Python 3.7 with pip, as well as Git;
  2. Make sure Python 3.7 can be called directly via python from the shell;
  3. Make sure Git is installed and can be called directly via git from the shell;
  4. pip install -r requirements.txt to install required Python libraries;
  5. Run the build script URL=my_url python build.py where my_url is the full URL you would later host the resource files on. E.g. if you want to access the plugins via https://example.com/index.json then replace my_url with https://example.com/.
  6. Verify that:
    1. the public directory is generated;
    2. there should be public/index.json containing information of all extensions;
    3. all extensions should exists in public as sub-directories;
  7. Host the public directory like you would do with any static resources, using nginx, caddy, etc.
  8. 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.

  1. standardnotes
  2. sn-extensions
  3. JokerQyou/snextensions
  4. iganeshk/standardnotes-extensions
  5. kylejbrk/standard-notes-open-extended

About

Standard Notes Extensions

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages

  • Python 100.0%