This repository has been archived by the owner on Feb 12, 2024. It is now read-only.
Deploying js-ipfs to the Galaxy #804
Assignees
Labels
exp/wizard
Extensive knowledge (implications, ramifications) required
kind/maybe-in-helia
need/maintainer-input
Needs input from the current maintainer(s)
status/deferred
Conscious decision to pause or backlog
Comments
|
|
|
re relays: https://github.com/libp2p/js-libp2p-circuit/issues/4
How are active relays gonna be handled, does it make sense to have them as dedicated nodes, maybe part of the bootstrap list? |
Metrics to expose
|
|
@victorbjelkholm is Datastore or Repo? Otherwise looks good :) |
Probably repository on second thought, went by the IRC log posted in the beginning.
For reference, this is a example call to |
|
@victorbjelkholm check out http://npmjs.org/prom-client, most of that templating comes from there, it is a good head start :) |
|
Now (#913) we have the possibility of getting metrics from a running js-ipfs node! Docs here: https://github.com/ipfs/js-ipfs#monitoring Created another issue in the dweblink-infra repo for tracking work on getting some js-ipfs gateways up and running: ipfs-inactive/dweblink-infra#1 Then we'll be full-speed ahead serving content to the galaxy from js-ipfs 🎉 |
|
Really close to https://github.com/ipfs/js-ipfs/pull/968/files Can we have |
Yeah, sounds good to me. Perhaps could be more specific, like |
|
I like |
|
Ok, Gateway has been merged into master. @victorbjelkholm can we have just one js-ipfs node as a gateway under js.ipfs.io? @lgierth ? 🙏🏽 please! |
daviddias
added
P0
ghost
self-assigned this
daviddias
added
status/in-progress
|
Hi @lgierth you asked me two weeks ago to ping you in two weeks if this hasn't moved. Any update here? |
|
Not getting to this over the rest of this year -- this should be done on the new infra and that's not ready yet. |
|
😢 What's the new infra? |
daviddias
added
exp/wizard
|
|
@victorbjelkholm that's expected, I believe (depends on the log message). If the daemon can't start a listener, it won't start (and therefore crash and stop). |
|
Hm, I understand what you're saying. But if my local state is exactly the same, I don't expect the daemon to start crashing because of some external application. I think it would be more reasonable to output a warning/error but keep the daemon running. |
|
@victorbjelkholm just saw the IPFS All Hands notes
Woowow!! 👏🏽 Can you put it accessible behind |
|
@diasdavid indeed :) It's coming, waiting for Lars to verify the DNS change and to review the infra change. |
|
@victorbjelkholm js.ipfs.io is not letting me using the js-ipfs daemon as a gateway -- https://js.ipfs.io/ipfs/QmSXArjcBFsHY7WznMyuAqZKVh5cX95DkeNyR5wqcNmprQ |
Merged
|
@diasdavid missed this. Two points: daemon is too unstable to rely on currently, so I've stopped working on it for now. Second is that that I haven't yet setup the DNS records for js.ipfs.io, that's why it's not working for you :) |
|
@victorbjelkholm I'm going to work on having the daemon more stable, as in #1325. The thing is: I'm not sure how to tackle this, as you're working on it too can you point me in the right direction? |
hugomrdias
added
status/deferred
|
js-ipfs is being deprecated in favor of Helia. You can #4336 and read the migration guide. Please feel to reopen with any comments by 2023-06-02. We will do a final pass on reopened issues afterwards (see #4336). @achingbrain @BigLep do we have js-ipfs running on infra? Do we have a tracking item for replacing them with Helia? |
SgtPooki
added
need/maintainer-input
|
js-ipfs is not running in NodeJS context on any PL-owned infra that I'm aware of. |
|
No, there were big plans that never really got executed. Closing as this was a piece of work that never got finished. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Similar to go-ipfs, we want to run some js-ipfs nodes and monitor their behaviour. From a quick chat with @lgierth on IRC, here are some notes:
The text was updated successfully, but these errors were encountered: