aynish/grasp
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

add info on unrestricted extension

Browse source
This commit is contained in:
Dmitrii Gerasimov 2019-01-16 22:35:50 +00:00 committed by GitHub
parent 7db7cc5cb1
commit 6c017818ab
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
README.md
View file

@ -16,6 +16,9 @@ No third party dependencies! Just `python 3.6`.
That's it! If you're using custom port make sure it's same as in the extension settings (default is `12212`). That's it! If you're using custom port make sure it's same as in the extension settings (default is `12212`).
## Using arbitrary endpoint instead of localhost
If you want to run the server remotely, you need extra permissions. Chrome store requires some extra checks when publishing if you do that, so I figured it's better to have localhost only by default. You can use unrestricted extension instead and connect to the remote host. Ssee `grasp-anyhost` packages [here](https://github.com/karlicoss/grasp/releases), or 'Building' section if you'd rather build it yourself. Don't forget to set the endpoint in extension settings!
# Motivation # Motivation
Why use org-capture? Well, it's hard to explain, maybe some other time... However if you do know you want to use it instead/alongside your browser bookmarks, by default Why use org-capture? Well, it's hard to explain, maybe some other time... However if you do know you want to use it instead/alongside your browser bookmarks, by default
you don't have much choice and have to copy everything manually. For an average Org Mode user it's a torture. you don't have much choice and have to copy everything manually. For an average Org Mode user it's a torture.
@ -45,7 +48,7 @@ You're gonna need `npm` for building extension.
After that you can find the extension in `build` directory and 'Load unpacked** if necessary. There is also Flow and Eslint set up. After that you can find the extension in `build` directory and 'Load unpacked** if necessary. There is also Flow and Eslint set up.
## Unrestricted url ## Unrestricted url
If you want to run server remotely, you need extra permissions. Chrome store requires some extra checks when publishing if you do that, so I figured it's better to have localhost only by default. If you do need unresticted url permissions, build the extensions like that: `ANY_URL=yes npm run build`. Then don't forget to set the endpoint in extension settings. If you do need unresticted url permissions, build the extensions like that: `ANY_URL=yes npm run build`.
# Permissions used # Permissions used
* `storage` for settings * `storage` for settings