fbaiodias / ipfs-chrome-station Goto Github PK

:dizzy: Chrome extension that let's you access IPFS urls seamlessly from your local IPFS node, and take a look at its stats

Home Page: https://chrome.google.com/webstore/detail/ipfs-station/kckhgoigikkadogfdiojcblegfhdnjei

License: MIT License

JavaScript 78.41% CSS 20.19% HTML 1.40%

ipfs-chrome-station's Introduction

ipfs-chrome-station

Chrome extension that let's you access IPFS urls seamlessly from your local IPFS node, and take a look at its stats.

Based on react-chrome-extension-boilerplate, ipfs-station and ipfs-firefox-addon (if you're using Firefox, make sure to check it out).

Demo

Features

Icon with badge that shows if the node is running, and how many peers are connected to it
Clicking on the icon opens popup menu with useful operations:
- See stats of the IPFS node
- Toggle redirection to the IPFS node
- Open IPFS node WebUI
- Open extension options (more about this bellow)
- Additionally, on pages loaded from IPFS:
  - Copy canonical IPFS address
  - Copy shareable URL to resource at a default public gateway (https://ipfs.io)
  - Pin/unpin IPFS Resource
When redirection is on, requests to https?://*/(ipfs|ipns)/$RESOURCE are replaced with http://localhost:8080/(ipfs|ipns)/$RESOURCE
Options menu that let's you customize several parameters:
- IPFS node host
- IPFS node port
- IPFS node API port
- API stats polling interval
- Toggle redirection

Installation

# git clone ...

npm install

Development

Run script

# build files to './dev'
# start webpack dev server
npm run dev

Go to chrome://extensions/ and check Developer Mode box
Click Load unpacked extension... and select the dev folder

Build

# build files to './build'
npm run build

Compress ZIP file

# compress build folder to build.zip
npm run compress

LICENSE

MIT

ipfs-chrome-station's People

Contributors

Stargazers

Watchers

Forkers

sbepstein shaunyudin packetlost kryptohaus mateon1 alexxnica labeanc compliment jayd2446 tojin12341za hudsonkavin stevenans66 ben-haim

ipfs-chrome-station's Issues

"WEBUI" link pointing to the wrong place

My ipfs gateway is running on a raspberry pi, so I enter the pi's ip address 1.2.3.4 in the extension configuration.

The plugin works as expected, but for one thing... the WEBUI link in the extension overlay window is hardcoded to http://localhost:5001/webui.

The expected url should be http://1.2.3.4:5001/webui

Thanks for making this plugin.

Extension broken with 0.4.5-pre1

In 0.4.5, the format of the /api/v0/swarm/peers endpoint changes, so the extension shows that the daemon is offline regardless of its status.

Problem running ipfs station

I tried running ipfs config --json API.HTTPHeaders '{"Access-Control-Allow-Origin": ["*"]}'
It returns
Error: Unknown Command "API.HTTPHeaders"
ipfs daemon running ok
I can get to my config file via -
https://ipfs.io/
What do I do from there to up date the config file ?

ipfs:// and ipns://

https?://*/(ipfs|ipns)/$RESOURCE are replaced with http://localhost:8080/(ipfs|ipns)/$RESOURCE

Would be sweet if ipns://$RESOURCE andipfs://$HASH got redirected too. 🤔

Option to disable the peer count

Taken from a review on the webstore:

I would love to have the option to turn off the peer count though, or to change the color because this blue is a bit too spectacular.

make sure you have CORS enabled

On windows7 x64 runipfs daemon 0.4.9-rc2
Chrome addon shows me picture

Oh snap, it looks like your node is not running yet.

Please start it by running ipfs daemon on your terminal.

Also, please make sure you have CORS enabled, by running 
ipfs config --json API.HTTPHeaders '{"Access-Control-Allow-Origin": ["*"]}'

Report a problem

and seems like not work.
It works some time ago –
don't now when it ended. I try to run command from message – it returns error

C:\>ipfs config --json API.HTTPHeaders '{"Access-Control-Allow-Origin": ["*"]}'
Error: Unknown Command "API.HTTPHeaders"

Allow specifying full URLs for webui/api/gateway, not just ports

I have a regular webserver set up as a HTTPS reverse proxy in front of my IPFS gateway. It'd be nice if the extension could be told to use that, to avoid mixed-content problems on regular HTTPS sites.

Add options page

Add an options page like ipfs-firefox-addon's one that let's you edit:

Documentation: https://developer.chrome.com/extensions/optionsV2

Required for #2

Un detallito en la descripción

Hola... de antemano te aviso que no es "issue". El caso es que estaba mirando el proyecto y me ha chocado un "let's you" (lo tienes en el título del proyecto, en el About y al inicio del README.md en la parte que pone "Chrome extension that let's you access IPFS urls seamlessly from your local IPFS node, and take a look at its stats." y luego en el README.md más abajo donde pone "Options menu that let's you customize several parameters"). Hasta donde yo llego en inglés tengo entendido que "let's" es contracción de "let us" ("us" de nosotros)... así que me ha descuadrado al completo cuando lo he visto. Quería avisarte de esto por si no hubieras echado cuenta. Un saludo.

PD: ¿Vas a portarlo a Firefox?

[email protected] does not satisfy its siblings' peerDependencies

$ npm install
npm WARN peerDependencies The peer dependency react@^0.13 || 0.14.0-beta1 included from react-file-drop will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency 
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN optional dep failed, continuing [email protected]
npm WARN optional dep failed, continuing [email protected]

[snip]

npm ERR! Linux 3.19.0-34-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v4.2.2
npm ERR! npm  v2.14.7
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package [email protected] does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer [email protected] wants react@^0.14.2
npm ERR! peerinvalid Peer [email protected] wants react@^0.14.2
npm ERR! peerinvalid Peer [email protected] wants react@^0.13 || 0.14.0-beta1
npm ERR! peerinvalid Peer [email protected] wants react@^0.14.0
npm ERR! peerinvalid Peer [email protected] wants react@>=0.13.2 || ^0.14.0-rc1

CORS enabled but IPFS station still says that node is not running

my daemon is set to listen on 8082 and 5001, so I set ports accordingly in settings.

Feature Parity with Firefox Extension

Hey @xicombd nice extension -- wondering if you want to reach feature parity with @lidel's https://github.com/lidel/ipfs-firefox-addon/ ?

It would be nice to control the daemon from the extension too, but doubt it can launch processes. Perhaps we can create (a) a micro service that is always on and starts + stops ipfs and listens to commands over http, (b) an installer to install everything (ipfs, microservice, + extension) nicely.

Pin IPFS Resource
Copy canonical IPFS address
Copy shareable URL to resource at a default public gateway