I installed IPFS on both Debian Sid and Centos 6.6 (Final). When running the daemon I get:

ERROR core/serve: Path Resolve error: no link named "fontawesome-webfont.woff2" under QmWjympWW8hpP5Jgfu66ZrqTMykUBjGbFQF2XgfChau5NZ gateway_handler.go:436

It doesn't seem to affect functionality, but something is definitely amiss.

go version go1.4.2 linux/amd64
ipfs version 0.3.4

• log/tail works in the new js-ipfs-api
• To ensure we are not running out of memory the log should
  • be streamed into a ring buffer with a max of 1000 lines
  • stopped when navigating away from the log view and the ring buffer cleaned up from memory

It seems like it would be immensely cool to have a visualization of data stored in ipfs.

[Edit: To clarify, what I'm imagining is an interactive node/link visualization/browser running in a JavaScript app, either in the webui or a separate application.]

1. Does this exist already somewhere? If not, is the webui the right place to add it? I think this may ultimately want to be it's own application.
2. What kind of visualization? I lean toward graph viz (nodes and edges). Other good options include tree-shaped viz.
3. Which JS viz framework? My top 3 picks are:

• http://d3js.org/
• http://sigmajs.org/
• http://famo.us/

If we were doing graph-shaped viz, I'd lean toward Sigma, because it creates beautiful graphs pretty much out of the box, and renders to webgl (when available) for use with large data sets.

If I get time I'll hack on it a bit; meanwhile any feedback very welcome.

repro: on the webui, put an ipns path in the search bar, i.e. /ipns/ipfs.git.sexy. Then click the "Raw" button on the resulting page, it will redirect you to a gateway link that will be broken as it tries to prepend the path with /ipfs/ resulting in /ipfs/ipns/ipfs.git.sexy

we are running an ipfs gateway on a server.

i'd like to be able to run the API behind a reverse proxy so that we can add basic authentication for the node but expose the gateway to the public. also, i'd like the url to resolve without having to type the ports when i want to check the gateway.

setup: ipfs with API on 0.0.0.0:5001 nginx in front reverse proxying to ipfsc.erisbootstrap.sexy ... nginx is working properly for the gateway (see #3 ) and urls to ipfs.erisbootstrap.sexy (which is routed to the gateway port) all resolve fine.

problem: when i connect to ipfsc.erisbootstrap.sexy which is proxied to 5001, the webui loads fine but does not connect to the API properly. it is just a plain UI without any connection details. however when I connect via the IP:Port combo it resolves fine. links below:

• url i'd like to use which won't connect to the api on the node: https://ipfsc.erisbootstrap.sexy/webui
• url which i'm not keen to use which does connect to the api on the node: http://54.93.113.247:5001/webui

It would be nice to consolidate this with https://github.com/ipfs/dir-index-html and have a single source of truth for these. @jbenet what would need to happen from a technical standpoint to make that happen?

The location of node-webkit has been moved. The node-webkit-builder package needs to be updated to at least 1.0.6 (^1.0.6).

I'd like to setup a test suite for the webui, so i can reliably know merging something without running it + QA-ing it myself won't totally break everything. both:

1. with a mocked out API (jasmine or whatever we want)
2. with a live running node, so we test it end-to-end

this issue will track proposals on how to do this test suite.

/static/bootstrap/3.3.2/css/bootstrap.min.css This link should resolve in this repo

https://github.com/protocol/ipfs-webui/blob/master/html/index.html#L17

/static/bootstrap/3.3.2/js/bootstrap.min.js This link should resolve in this repo

https://github.com/protocol/ipfs-webui/blob/master/html/index.html#L28

These either need to be vendored or produced during the static step in gulp.

I'm running into all sorts of crazy errors when trying to commit anything. I just made a branch off master and I can't commit anything due to the post-commit hooks that are in place.

https://gist.githubusercontent.com/travisperson/37a498c6d5b4bc4873b4/raw/gistfile1.txt

/cc @STRML

OK, so this is probably a stupid question, but how do we bind this repo to the go-ipfs daemon? This repo does not seem to be a git submodule (or a subtree) of go-ipfs or anything.

We can install and compile go-ipfs, then initialize it and start up the daemon:

    ipfs init
   ipfs daemon

And then we look up localhost:5001 and get the older version.

I am asking here rather than via IRC so that the answer will be searchable and public.

What is the routine to checkout the newer versions?

On running make serve, and checking the files page, i get multiple errors along the line of:

Uncaught TypeError: undefined is not a function files.jsx:21

the offending line is:

pinned.Keys.sort()

This seems to be a EC6 feature, but it's not being transpiled in the build.

As a workaround i replaced the places where this was used with lodash.

@travisperson
Is there some special setup to have it transpile in the dev-env?

$ ipfs add US-Government-Still-Silent-on-American-Journalist-Murdered-for-Exposing-Turkey’s-ISIS-Ties.pdf
added QmY6sC3NmsCbZiPihyfhDiR2gijdzqN7BaYK2g7PewbYpH US-Government-Still-Silent-on-American-Journalist-Murdered-for-Exposing-Turkey’s-ISIS-Ties.pdf
$ ipfs ls QmY6sC3NmsCbZiPihyfhDiR2gijdzqN7BaYK2g7PewbYpH
QmeUkVZKQwrUdG1BndVNkq6n88yzGnGH5JBrdiVsG7Uc5i 262158 
QmVHBYN1HMasLHBMHWs1hVJFWJ3K7jNkr6f1EWSZJV27ZB 262158 
QmXCb1TaYAx8hW3KJLA3ZMneSg56iTRGewghsMHq53YqEc 262158 
QmZ6D1pzR7MJgXmjAfTJQxVAhYQqn6UYLFFtoUfyYYGDe8 262158 
QmT7FYPgR5wGesFBBDdN3sqXop9HgYaP5pn3zzKtJiQptS 262158 
QmczHBY4xExAQ1AEyoax38fC3Jh9yXTqGkgnqCfGotkrtV 262158 
QmQD1uXBz63RN8RENYBMgfZ1W7cJvZ5wx4TSFLjqFTBKZA 262158 
QmfFFPwwhTWZ6rj1wgsKo17zZ1uVi2mpNCrAz7CQ7FUgd8 143546 
$ 

Notice that I did not pin this object.

Yet, it appears in the pinned files list:
http://localhost:5001/ipfs/QmS2HL9v5YeKgQkkWMvs1EMnFtUowTEdFfSSeMT4pos1e6/#/files/pinned

PINNED FILES
Type ID Actions

QmNxYrzU7nLMERzNn8SHnJYxiQQCr5xYFGBPMoDbXX3FCV
QmPQUsvqQH5kEntM99FspUWxMUd8iJy5FCFkd2dAa3eSFv
QmQmJ55Vm9Ct6Vvhpnv2r8JBpcxNeivvcGXvVvRogb8zu2
QmTumTjvcYCAvRRwQ8sDRxh8ezmrcr88YFU7iYNroGGTBZ
QmUFtMrBHqdjTtbebsL6YGebvjShh3Jud1insUv12fEVdA
QmUNLLsPACCz1vLxQVkXqqLX5R1X345qqfHbsf67hvA3Nn
QmVVNSyQkAeW4fA5oB1YY5rSxbz5pmGt3U4Vm1cqeaMrbz
QmX97wck9U7yUJHDjMVDHy2ZNmcHjgAseFaMoWMJtehxXT
QmXu6ouEAraepkgMshQ8C9Wpu6AVdQuSwZ1a7jJsoXQZMK
QmY5heUM5qgRubMDD1og9fhCPA6QdkMp3QCwd4s7gJsyE7
QmY6sC3NmsCbZiPihyfhDiR2gijdzqN7BaYK2g7PewbYpH
QmY9eMeuK2JYpPwUiFCd5j8UvM5CDroMeu4L8o96nxrrgs
QmYCvbfNbCwFR45HiNP45rwJgvatpiW38D961L5qAhUM5Y
QmZNe3xvQaxdtVp43NTJ9oURYPBKyVFJ8VDWHPipcGUwNF
QmZdL7uPYYEV3J1uzg3GARv1oAEmPB3ic3SrekgaaP1SZF
Qmbm4DRJd5eCMNeeHrtrJ4vYJGYAkbu2ZXtisb6C5ciWY1
Qmcqtw8FfrVSBaRmbWwHxt3AuySBhJLcvmFYi3Lbc4xnwj
QmdRkpcRWDQp3GDw2sLjdNjsmCAtaNivRex3r2ZkkgBNMC
QmeCd1SFRCxTqxfFDpV7sdj2Yci9ZzAUGCky7SmJkaQGf1
QmeEqpsKrvdhuuuVsguHaVdJcPnnUHHZ5qEWjCHavYbNqU
QmeFod9Whb3sMcXS3FyJrFdLPFad7PfiR8yFWADLTQFPB3
QmegAwrtM29oZqG52KM57SdxmiHveorJEguh1EdD42uYuh
QmfE3nUohq2nEYwieF7YFnJF1VfiL4i3wDxkMq8aGUg8Mt
QmfF48NZGzVq53XqutPmNRrgJQS3uypC73Ypc25qqsgKr5

It also appears in:
ALL LOCAL FILES
Type ID Actions
QmNxYrzU7nLMERzNn8SHnJYxiQQCr5xYFGBPMoDbXX3FCV
QmPQUsvqQH5kEntM99FspUWxMUd8iJy5FCFkd2dAa3eSFv
QmQmJ55Vm9Ct6Vvhpnv2r8JBpcxNeivvcGXvVvRogb8zu2
QmTumTjvcYCAvRRwQ8sDRxh8ezmrcr88YFU7iYNroGGTBZ
QmUFtMrBHqdjTtbebsL6YGebvjShh3Jud1insUv12fEVdA
QmUNLLsPACCz1vLxQVkXqqLX5R1X345qqfHbsf67hvA3Nn
QmVVNSyQkAeW4fA5oB1YY5rSxbz5pmGt3U4Vm1cqeaMrbz
QmX97wck9U7yUJHDjMVDHy2ZNmcHjgAseFaMoWMJtehxXT
QmXu6ouEAraepkgMshQ8C9Wpu6AVdQuSwZ1a7jJsoXQZMK
QmY5heUM5qgRubMDD1og9fhCPA6QdkMp3QCwd4s7gJsyE7
QmY6sC3NmsCbZiPihyfhDiR2gijdzqN7BaYK2g7PewbYpH
QmY9eMeuK2JYpPwUiFCd5j8UvM5CDroMeu4L8o96nxrrgs
QmYCvbfNbCwFR45HiNP45rwJgvatpiW38D961L5qAhUM5Y
QmZNe3xvQaxdtVp43NTJ9oURYPBKyVFJ8VDWHPipcGUwNF
QmZdL7uPYYEV3J1uzg3GARv1oAEmPB3ic3SrekgaaP1SZF
Qmbm4DRJd5eCMNeeHrtrJ4vYJGYAkbu2ZXtisb6C5ciWY1
Qmcqtw8FfrVSBaRmbWwHxt3AuySBhJLcvmFYi3Lbc4xnwj
QmdRkpcRWDQp3GDw2sLjdNjsmCAtaNivRex3r2ZkkgBNMC
QmeCd1SFRCxTqxfFDpV7sdj2Yci9ZzAUGCky7SmJkaQGf1
QmeEqpsKrvdhuuuVsguHaVdJcPnnUHHZ5qEWjCHavYbNqU
QmeFod9Whb3sMcXS3FyJrFdLPFad7PfiR8yFWADLTQFPB3
QmegAwrtM29oZqG52KM57SdxmiHveorJEguh1EdD42uYuh
QmfE3nUohq2nEYwieF7YFnJF1VfiL4i3wDxkMq8aGUg8Mt
QmfF48NZGzVq53XqutPmNRrgJQS3uypC73Ypc25qqsgKr5

But it’s NOT in [Files Tab]
Type Name ID Actions
HTM
You Are Here.htm
QmNxYrzU7nLMERzNn8SHnJYxiQQCr5xYFGBPMoDbXX3FCV
PNG
11080908_822881507801355_5238711632930395669_n.png
QmZNe3xvQaxdtVp43NTJ9oURYPBKyVFJ8VDWHPipcGUwNF
JPG
Terrorism 1966 Definition.jpg
QmXu6ouEAraepkgMshQ8C9Wpu6AVdQuSwZ1a7jJsoXQZMK
JPG
Errico-Malatesta.jpg
QmQmJ55Vm9Ct6Vvhpnv2r8JBpcxNeivvcGXvVvRogb8zu2
JPG
Lucy-Parsons-development-individuals.jpg
QmegAwrtM29oZqG52KM57SdxmiHveorJEguh1EdD42uYuh
JPG
11102920_786874584744137_4665089822529436252_o.jpg
QmY9eMeuK2JYpPwUiFCd5j8UvM5CDroMeu4L8o96nxrrgs
JPG
de19747bcbd79ad457971fa173f4952e_970x.jpg
QmdRkpcRWDQp3GDw2sLjdNjsmCAtaNivRex3r2ZkkgBNMC
PNG
boy 234x234.png
QmPQUsvqQH5kEntM99FspUWxMUd8iJy5FCFkd2dAa3eSFv
PNG
virtual reality 1213x449.png
QmX97wck9U7yUJHDjMVDHy2ZNmcHjgAseFaMoWMJtehxXT
JPG
boy electric socket.jpg
QmQQWN2nV3KgaWtGWMYGPvh1sLDk1Xg8MtCDQN2CCPoiyv

In fact all files in the Files list are only those I added before mid-October; none added since then appear. This begs the question: what is the intended purpose of the files list - only "unpinned" files?

As @whyrusleeping said, desktop icon, easy install.

today, when files are added via webui they get put on local storage.

this should no longer be the case. we should not be using browser local storage for this, as it gets inconsistent with the ipfs repo itself. all[1] state should go through the api.

[1] i think all. post if you think any should remain in local storage. possible that some user preferences -- now i think about it i think @STRML made it a preference to pick a particular globe. (sorry i haven't published that, was waiting on some bugfixes)

The API server is served by braintree/manners, which keeps serving until all connections are closed.

Parts of the webui, such as polling for peers in the swarm, will open a connection and keep it open, but there doesn't seem to be any check for whether or not the server is in "shut down mode", which means the webui will keep the server alive forever.

On the ipfs daemon side there's no logging of why the server is kept alive, such as e.g. "Waiting for API connections to finish", and closing the tab with the webui in Chrome doesn't seem to immediately close the connection either, so the reason for the stuck server is quite opaque.

The only option is to forcefully close the daemon with another Ctrl+C, resulting in "Received another interrupt before graceful shutdown, terminating...", which can be a bit scary, as the user doesn't know what bad effects that might result in.

See https://github.com/rackt/react-router/blob/master/CHANGES.md for details on what to do

• currently doesnt
• ipfs/kubo#850

context: we have an IPFS gateway on a server. gateway is bound to 0.0.0.0:8080. in front of gateway, nginx is reverse proxying 8080 to 443. that all works fine. in addition, the API port is bound to 0.0.0.0:5001.

when i go to the webui here and hover on links to the raw files they resolve to http://0.0.0.0:8080/ipfs/.... rather than our gateway.

if there was a way to pass an effective base URL to the webui for links that would be tremendous, or some other way to have the ui understand that our public facing gateway is running on a different URL than what the backend is bound to.

Great work, BTW, the UI looks fantastic.

I noticed that the web ui would stop working after a while, and permanently. The API still responds fine, but not when the UI makes the request. Chrome/firefox web tools lets you export a request to a cURL command, and I was able to export a working request (where I pasted in the api url into the address bar), and a broken request coming from the API. These results are replicated using cURL as well.

Chrome

Command from the address bar, working:

curl 'http://127.0.0.1:5001/api/v0/config?arg=Addresses.Gateway&stream-channels=true'
-H 'Accept-Encoding: gzip, deflate, sdch'
-H 'Accept-Language: en-US,en;q=0.8'
-H 'Upgrade-Insecure-Requests: 1'
-H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36'
-H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8'
-H 'Cache-Control: max-age=0'
-H 'Connection: keep-alive' --compressed

Response:

{
  "Key": "Addresses.Gateway",
  "Value": "/ip4/127.0.0.1/tcp/8080"
}%

Command from the web UI, broken:

curl 'http://127.0.0.1:5001/api/v0/config?arg=Addresses.Gateway&stream-channels=true'
-H 'Accept-Encoding: gzip, deflate, sdch'
-H 'Accept-Language: en-US,en;q=0.8'
-H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36'
-H 'content-type: undefined'
-H 'Accept: */*'
-H 'Referer: http://127.0.0.1:5001/ipfs/QmaaqrHyAQm7gALkRW8DcfGX3u8q9rWKnxEMmf7m9z515w/'
-H 'Connection: keep-alive' --compressed

Response:

403 - Forbidden%

The diff of these 2 requests are as follows (working on the left, web ui on the right):

I found that removing the referrer and adding the Cache-Control: max-age=0 fixed the request:

curl 'http://127.0.0.1:5001/api/v0/config?arg=Addresses.Gateway&stream-channels=true'
-H 'Accept-Encoding: gzip, deflate, sdch'
-H 'Accept-Language: en-US,en;q=0.8'
-H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36'
-H 'content-type: undefined'
-H 'Accept: */*'
-H 'Cache-Control: max-age=0'
-H 'Connection: keep-alive' --compressed

Result:

{                                                                 
  "Key": "Addresses.Gateway",
  "Value": "/ip4/127.0.0.1/tcp/8080"
}%  

Firefox

The requests coming from firefox are a bit different.

Working, from a request coming from the URL bar:

curl 'http://127.0.0.1:5001/api/v0/config?arg=Addresses.Gateway&stream-channels=true'
-H 'Host: 127.0.0.1:5001'
-H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 Firefox/41.0'
-H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8'
-H 'Accept-Language: en-US,en;q=0.5' --compressed
-H 'Cookie: __utma=96992031.1150785634.1435613418.1435613418.1435687582.2; __utmz=96992031.1435613418.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none)'
-H 'Connection: keep-alive'
-H 'Pragma: no-cache'
-H 'Cache-Control: no-cache'

Broken, coming from the web ui:

curl 'http://127.0.0.1:5001/api/v0/config?arg=Addresses.Gateway&stream-channels=true'
-H 'Host: 127.0.0.1:5001'
-H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 Firefox/41.0'
-H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8'
-H 'Accept-Language: en-US,en;q=0.5' --compressed
-H 'Content-Type: undefined'
-H 'Referer: http://127.0.0.1:5001/ipfs/QmaaqrHyAQm7gALkRW8DcfGX3u8q9rWKnxEMmf7m9z515w/'
-H 'Cookie: __utma=96992031.1150785634.1435613418.1435613418.1435687582.2; __utmz=96992031.1435613418.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none)'
-H 'Connection: keep-alive'
-H 'Pragma: no-cache'
-H 'Cache-Control: no-cache'

Diff:

P.S. Here's what the web ui looks when the api requests fail. You can see the network inspector open with the xhr filter, showing all the failed requests:

The webui is about to get an overhaul, and the build system needs to be figured out before too much work is done.

Here are some goals

• Modularize everything. See #73
• Create test suit. See #38
• Build ES2015 with Babel

The two main options are Webpack and Browserify.

Browserify:

Pros:

• Simple, follows Unix philosophy
• Mature and fast

Cons:

• Integrating non-JS assets requires writing non portable shell scripts

Webpack:

Pros:

• Fully featured. Plugins allow for awesome things like react hot-reloading
• Loads most any type of file. All assets can be processed with one tool

Cons:

• A bit of magic. Complicated config(well documented though)

I'm not quite sure if this is intentional or not, but when I enter a hash in the search bar of the webui that doesn't exist, the link to that let's you "Go to console home" sends you to http://localhost:5001 rather than http://localhost:5001/webui resulting in another 404 error.

#58 broke the small-screen view, as the peer-list completely obscures the globe.

@travisperson i agree that a fixed globe is better, could we find a way of doing it more screen-size responsive?

We should drop jquery as a dependency and replace all instances with alternatives. For all things bootstrap we should use react-bootstrap and drop bootstrap with jquery

• scripts/pages/files.js:5:16
• scripts/pages/objects.js:3:16
• scripts/views/config.js:3:16
• scripts/views/editable.js:2:16
• scripts/views/filelist.js:2:16
• scripts/views/page.js:5:16

This is an issue compiling a bunch of feedback in one place.

Styling + Home

Styling:

• links still break url + back button... use hash or query string?
• fa-list for logs
• reduce sidebar nav font-weight (use 200 or 400? maybe helvetica neue?)
• reduce size of sidebar?
• title or dag search bar at the top navbar
• top navbar 10px shorter
• top right icons should have tool tips
• add "Docs" top right icon

Home

• use <code> for all hashes (monospace).
• use <code> for version identifiers
• use <pre> for key
• use <code> or <pre> for addresses

Connections

• dont geolocate local addresses. treat them as self.
  (geolocate own addresses only if not local)
• still not loads conns for me :(

Files

• drag+drop is super nice. but there's little indication that file was successfully added. maybe add a <div class="alert alert-success"> with each filename.
• list all local unixfs files in this page.
• hashes should be selectable (use <code>?), no need to link.
• add a "DAG" (or maybe fa-share-alt) action, which takes you to object's dag page
• Pinned Files should be in its own page. it's going to get big.
• All Local Files should be in its own page (Local Objects

DAG

• add to field: placeholder="Enter hash or path: /ipfs/QmBpath..."
• as user enters things, the field outline should color greein if a hash is correctly entered, and red if not. (some taeke a sec to be transmitted)
• enter on the field should work
• needs an image when there is nothing selected.

Config

• move save btn to right
• add a reset btn
• add reset + save buttons to top right
• make textarea arbitrarily large.

Logs

• use "Tail" instead of "Bottom".
• make it actually tail (add events + rescroll to end)
• add "Clear" and "Top" to bottom of file
• clear looks too faded. use same color.
• use<pre> for the text area,
• pretty-print each json item.
• use js syntax highlighting with GFM. (highlight.js?)

The file input wants one or more files. And dragging and dropping the folder doesn't work.

https://github.com/protocol/ipfs-webui/blob/c0c42c092ba2e34a7a0818e45dc79d92544466f4/js/getlocation.js#L15

If this request fails, the peer list is not shown. My node does not have internet access but is still connected to IPFS.

If a file is removed from the static folder (or really anywhere) it could be left in the build directory from a previous build. We should remove everything from the build directory prior to doing a new build to make sure we are working with a clean slate.

Preparations for hive

Screens

Home

• Not very interesting or useful at the moment, what else could we show on this screen? We should keep in mind that at least 95% of all people viewing these screens will be newcomers to IPFS for quite a while, so we should optimize for those cases.

Connections

• Improve map (no more crazy fans)
• Make peer list a table that's easy to navigate

Files

Take inspiration from Dropbox/Finder/Explorer

• Drag n drop
• Rename
• Delete
• Pin/Unpin
• File type detection
• Thumbnails for images and videos
• Folder navigation

DAG

• Is this actually needed? Wouldn't it be enough to have this data shown as a details screen from the files panel, and if you enter a hash in the search at the top.

Config

• The config should not be a json object to edit, but rather toggles and input fields

Logs

• Never worked for me once, so not sure what to do here

Stats

• Ideas in #40

Other thoughts

• Documentation?

Drafts

Connections

• V1 https://ipfs.io/ipfs/QmTr8oTzi1upsHhHoK3ixmsxosD7hFMuMgbEZSakMRbTUT

When viewing the globe:

THREE.CubeGeometry has been renamed to THREE.BoxGeometry.
THREE.GeometryUtils: .merge() has been moved to Geometry. Use geometry.merge( geometry2, matrix, materialIndexOffset ) instead.

I am using Firefox (latest release, on Linux) and when using /webui I see the RES memory size in top climbing at about 1MB/s.

Also, the browser eats quite some CPU (even if the globe is not showing, but just a static page).

So, what is causing this?

When adding files using the webui, the browser adds this information into localStorage.

If you then go and ipfs pin rm the content from the command line the file remains in the webui and cannot be removed.

today points to https://github.com/ipfs/go-ipfs, should point to https://github.com/ipfs/webui/issues/

HT @d6e

Hi, I have a server with my basic webapp being served via nginx.

Now I have installed ipfs and want to add a /ipfsui proxy target which would take me to the webui for ipfs, thus I made the following additions to my existing fowardproxy in nginx.conf

        location /ipfsui {
            proxy_pass http://127.0.0.1:5001/webui/;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;
        }

        location /ipfs {
            proxy_pass http://127.0.0.1:5001;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;
        }    

Now I can go to the ipfs ui by going to http://my_server_ip/ipfsui which properly redirects me to
http://my_server_ip/ipfs/hash_here/#/

However, the page has no relevant ipfs info (like my peer id and so on).

Then I went on to inspect the console error messages and found:

Uncaught TypeError: Cannot read property 'split' of undefined     bundle.js:2185
(anonymous function) @ bundle.js:2185
(anonymous function) @ bundle.js:21711
EventEmitter.emit @ bundle.js:6430
Response.handle @ bundle.js:7115
xhr.onreadystatechange @ bundle.js:6878
bundle.js:2225 Object {version: undefined, updateAvailable: false, updating: false, gateway: "http://127.0.0.1:8080"}

After looking up these error lines I came to the conclusion that the code in page.jsx (which has since changed in the main webui git repo, link: https://github.com/ipfs/webui/blob/master/js/views/page.jsx, but not changed so as it would overcome this problem of mine) determines the ipfs api url and port from window.location.host and window.location.port.

This is the snippet of the webapp that that I currently get served (via ipfs of course):

var host = window.location.hostname
var port = window.location.port || 80
var daemonConf = LocalStorage.get('daemon')
if (daemonConf) {
  host = daemonConf.host
  port = daemonConf.port
}
var ipfs = require('ipfs-api')(host, port)
var ipfsHost = window.location.host

var Page = React.createClass({
  displayName: 'Page',
  getInitialState: function () {
    var t = this

    ipfs.config.get('Addresses.Gateway', function (err, res) {
      if (err || !res) return console.error(err)

      var split = res.Value.split('/')
      var port = split[4]

(you can see where the code failed to split and tracedback from this snippet and the error above)

I know that not everyone will be running this behind a proxy and also that I can temp fix via making the ipfs api listen on 0.0.0.0 by setting it via ipfs config ... but want to ask if there is anby other way to get around my current problem before I embark on that path.

Current when adding anything file to the webui they get pinned recursively. Any file you add via ipfs add gets pin recursively to protect the file, and all it's blocks, from a gc. The node-ipfs-api currently does not send a -r/--recursive when running the pin rm command (api.pin.remove), so on any file you try to "delete" (the X), will return an error saying it is added recursively.

Subdirectories should be recognizable by icon, and possibly be listed first (as commonly done).

when you have a lot of connections on the connections page, and you scroll down, the globe moves with the page. I think it would look nicer if only the connections list scrolled, knowing nothing about javascript, i'm not sure how easy that would be to do.

See http://i18next.com/docs/migration/ for details on what to do

I don't know how many files/directories I have added, but as an experiment I have added thousands of them.

Browsing to http://localhost:5001/ipfs/QmXX7YRpU7nNBKfw75VG7Y1c3GwpSAGHRev67XVPgZFv9R/#/files/all makes Firefox and Chromium on Linux hang a lot.

I wondered what the connections list is good for (except of "yay, I have 50 peers and they are all on earth!").

It shows me the node id of my peers, but it doesn't link the nodeid to the gateway URL for /ipns/, which would be a nice way to learn about their published content.

There is barely any error handling right now. I think the web ui could benefit from having a centralized error handling component.

Update: (17/2/2016) Please look at #229 for how you can help out with writing tests.

Pasting the hash of a local file in the search bar at the top or clicking the DAG link in the files list always results in a 404 page for me.

ipfs version 0.3.7 (latest version through homebrew)

https://github.com/protocol/ipfs-webui/blob/master/js/pages/objects.jsx#L4
(and probably a few other places in the code base)

Just need to make this a lowercase o.

• Use arrow functions where possible
• Convert react components to use class based syntax when they have state otherwise convert them to stateless functional components (https://facebook.github.io/react/blog/2015/10/07/react-v0.14.html)
• No more var. The default should be const and where mutability is needed use let (Enforced through no-var in eslint
• Use template strings instead of string concatenation

We should have some kind of loading animation, when objects are being resolved etc.

Also, a way to set context timeout to something much lower would be great for ux.

Hey everyone watching, we want to push to a 0.2.0 release of the webui next week. It will mostly be bug fixes and a couple improvements.

If you want to help with this, please self-assign an issue (if you don't have collab access to repo, can ask for it or just leave a comment at the end). -- but please keep assignments "fresh" (i.e. dont keep something assigned to self while not actively working on it).

Rough plan:

• 0.2.0 - bugfixes and so on
• ipfsdctl + atom-shell packaged app
• 0.3.0 - continue with new features and enhancements

cc @krl @travisperson @STRML

I would love to have a tab on the webui that gives you a file browser type thing into /ipns/local and allows you to do a lot of the same things you'd be able to do in a normal file browser.

features i want:

• view files and folders
• drag files into the browser to put them at that location
• delete files
• edit files
• move files around
• right click files to add metadata, rename, etc