https://github.com/JokerQyou/snextensions
A set of open source extensions for StandardNotes you can self-host.
https://github.com/JokerQyou/snextensions
extension sn-extensions standard-file standard-notes standardnotes
Last synced: about 1 month ago
JSON representation
A set of open source extensions for StandardNotes you can self-host.
- Host: GitHub
- URL: https://github.com/JokerQyou/snextensions
- Owner: JokerQyou
- Archived: true
- Created: 2019-08-03T13:39:26.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2023-03-01T04:52:50.000Z (about 2 years ago)
- Last Synced: 2024-02-14T21:26:07.349Z (over 1 year ago)
- Topics: extension, sn-extensions, standard-file, standard-notes, standardnotes
- Language: Python
- Homepage: https://snext.netlify.app/index.json
- Size: 69.3 KB
- Stars: 65
- Watchers: 8
- Forks: 35
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# snextensions
[](https://app.netlify.com/sites/snext/deploys)
A set of open source extensions for StandardNotes.
# Usage
Paste `https://snext.netlify.app/index.json` into `Extended Code` in StandardNotes.
# Notice
**2023-03-01 Update**
I've not used StandardNotes for a long time, so it's impractical for me to keep an eye for all the extension updates.
For this reason I'm archiving this repository. You can still use the code as is, or fork and modify to suit your own needs.
Happy hacking!
Previously (last year) the URL was `https://snext.netlify.com/index.json`.
But early this year Netlify decided to change the domain used by hosted apps.
If you've been experiencing empty editor UI, there's a chance that you're using
the old URL. Netlify is taking care of redirections but they are missing some
headers. You should migrate to the new URL.
These steps are required to migrate:
- Look for the "Repository" options in the "Extensions" menu (on the bottom)
- Delete the repository
- Uninstall all installed themes and editors
- Re-enter the new URL into `Extended Code`
- Re-install all the themes and editors you use
# Contribution
If you'd like an extension to be included in this repository, feel free to open an issue.
# Self-hosting
## With Netlify
In case if you'd like to host your own site other than using ours, you can do so with Netlify:
- Fork this repository;
- Create a Netlify account if you don't have one already;
- In Netlify app, Use "New site from Git" to create a site from your forked GitHub repository;
- Wait for the build to finish;
- After that you can use `YOUR_SITE_URL/index.json` as an `Extended Code`;
- Optionally you can set a human-readable site name (a subdomain of `netlify.app`) from the `Site settings` page.
**Notice: You need to manually trigger a new deploy via Netlify web UI after changing the site name.**
## 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.7` with `pip`, as well as `Git`;
- Make sure Python 3.7 can be called directly via `python` from the shell;
- Make sure Git is installed and can be called directly via `git` from the shell;
- `pip install -r requirements.txt` to install required Python libraries;
- 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/`.
- Verify that:
- the `public` directory is generated;
- there should be `public/index.json` containing information of all extensions;
- all extensions should exists in `public` as sub-directories;
- Host the `public` directory 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:
```nginx
add_header 'Access-Control-Allow-Origin' '*';
add_header 'Access-Control-Allow-Headers' 'content-type';
```