stebalien changed the topic of #ipfs to: Heads Up: To talk, you need to register your nick! Announcements: go-ipfs 0.4.23 and js-ipfs 0.41 are out! Get them from dist.ipfs.io and npm respectively! | Also: #libp2p #ipfs-cluster #filecoin #ipfs-dev | IPFS, the InterPlanetary FileSystem: https://github.com/ipfs/ipfs | Logs: https://view.matrix.org/room/!yhqiEdqNjyPbxtUjzm:matrix.org/ | Forums: https://discuss.ipfs.io | Code of
Jesin has joined #ipfs
risk has quit [Quit: Connection closed for inactivity]
snk07523 has joined #ipfs
themsay has quit [Remote host closed the connection]
themsay has joined #ipfs
doubtingben has joined #ipfs
galaxie has quit [Ping timeout: 240 seconds]
Adbray has joined #ipfs
galaxie has joined #ipfs
themsay has quit [Remote host closed the connection]
themsay has joined #ipfs
Ecran has quit [Quit: Going offline, see ya! (www.adiirc.com)]
irisisgay has joined #ipfs
}ls{ has quit [Ping timeout: 256 seconds]
themsay has quit [Remote host closed the connection]
themsay has joined #ipfs
}ls{ has joined #ipfs
fleeky has joined #ipfs
stoopkid has quit [Quit: Connection closed for inactivity]
<Pie-jacker875>
I'm back again, still trying to get my nginx reverse proxy to work
<Pie-jacker875>
any nginx wizards have a few minutes to spare? I've got ipfs running on my local server box, and I want to use it with the ipfs companion plugin
<RubenKelevra>
Wouldn't call me a wizard, but go ahead
<Pie-jacker875>
currently getting a 502 from it
<Pie-jacker875>
I'm not sure where location should be pointing
<RubenKelevra>
So you want nginx to accept the connections and proxy them to the Gateway?
<Pie-jacker875>
yeah, so that I can use a letsencrypt cert
<RubenKelevra>
(haven't found your last messages here)
<RubenKelevra>
ah!
<Pie-jacker875>
it was quite a while ago
<Pie-jacker875>
I didn't go much into it because I hadn't done anything at the time
<RubenKelevra>
okay, how's your Access-Control-Allow-Origin in the ipfs config look like?
<Pie-jacker875>
if you mean what it's listening on, it's [::] and 0.0.0.0
<RubenKelevra>
no
<Pie-jacker875>
k hold on, I need to remind myself where the ipfs config stuff is
<RubenKelevra>
take a look at the config stored at .ipfs/config... DONT BLINDLY COPY IT COMPLETLY IT CONTAINS YOUR PRIVATE KEY
<Pie-jacker875>
right
<RubenKelevra>
there's basicly an access filter for the gateway, which defines where requests are allowed to come from
<Pie-jacker875>
access-control-allow-origin is "*"
<RubenKelevra>
this sounds wrong
<RubenKelevra>
it also shoudn't listen on :: / 0.0.0.0
<Pie-jacker875>
I'm connecting to it from another machine
<Pie-jacker875>
on my network
<RubenKelevra>
ah okay, than this machine should be allowed to access this gateway
<Pie-jacker875>
yeah if I throw out the reverse proxy that works
<RubenKelevra>
oh wait, it's "origin" -> then * could be fine
<RubenKelevra>
I'm a bit tired, sorry
<Pie-jacker875>
the reason I'm setting this up is because it needs to go over https for ipfs companion browser extension
<RubenKelevra>
I understand the need for https :)
<RubenKelevra>
so, if you connect to the server which runs the nginx, and do a wget on the ipfs gateway, like http://1.2.3.4:8080/ipns/ipfs.io
<RubenKelevra>
what will wget give you as output?
<Pie-jacker875>
502
fleeky has quit [Ping timeout: 256 seconds]
<RubenKelevra>
oh, great!
<Pie-jacker875>
idk what the location dir should be
<RubenKelevra>
so it's not an nginx issue :D
<Pie-jacker875>
currently it's /
Adbray has quit [Quit: Ah! By Brain!]
<Pie-jacker875>
I don't really know what I'm doing, I only know enough to hurt myself lol
<Pie-jacker875>
I had followed a guide for reverse proxy for my matrix synapse instance
<Pie-jacker875>
but I couldn't find any guides for this
fleeky has joined #ipfs
<RubenKelevra>
we ignore the nginx part for now, it's just a glorified http client in this setup
<Pie-jacker875>
hmm k
<RubenKelevra>
just try to get ipfs to work fine as a gateway from the computer which should run the nginx. When this works it's somewhat simple.
<Pie-jacker875>
oh actually I only have port 8080 right now, there's nothing in nginx for 5001
<RubenKelevra>
I don't really get what that means :/
<RubenKelevra>
5001 is the API
<RubenKelevra>
8080 is the Gateway
<Pie-jacker875>
so I don't need that, right?
themsay has quit [Remote host closed the connection]
<Pie-jacker875>
I figured I didn't because the browser extension doesn't complain about that being over http
themsay has joined #ipfs
<RubenKelevra>
Do you want to talk to the API and make API calls over your nginx?
<Pie-jacker875>
probably not, unless it needs https
<RubenKelevra>
maybe we start in the beginning, tomorrow again ... I get pretty tired right now and I really don't get what you're trying to do :D
<RubenKelevra>
sorry
<Pie-jacker875>
no worries, thanks for responding so quickly
<RubenKelevra>
feel free to message me in like 10 hours again :)
<Pie-jacker875>
that works for me
themsay has quit [Remote host closed the connection]
themsay has joined #ipfs
doubtingben has quit [Ping timeout: 265 seconds]
<postables[m]1>
Pie-jacker875: post your nginx config, getting 502 means you're not proxying your connectinos properly
<Pie-jacker875>
hey so actually I can reach stuff over ipfs, though when I visit the Web UI page, it says it fails to connect to the API
<Pie-jacker875>
now it gives 404
<Pie-jacker875>
sorry, I said that in a confusing order
<Pie-jacker875>
webui page loads and says it fails to connect to api, trying to connect to the reverse proxy 404s
<Pie-jacker875>
which I think is probably fine
<postables[m]1>
without seeing your nginx config its hard to see whats wrong.
mowcat has quit [Remote host closed the connection]
dqx_ has joined #ipfs
fleeky has joined #ipfs
mowcat has joined #ipfs
mowcat has quit [Remote host closed the connection]
<Pie-jacker875>
I get 502 with that one verbatim
themsay has quit [Ping timeout: 240 seconds]
Pie-jacker875 has quit [Read error: Connection reset by peer]
Pie-jacker875 has joined #ipfs
<postables[m]1>
not an exact config you'll need to adjust it to suit your environment, but there's likely something off with your setup
irisisgay has quit [Quit: irisisgay]
<Pie-jacker875>
should I set listening back to just loopback?
zeden has quit [Quit: WeeChat 2.8]
g2anj has quit [Quit: .]
<bonedaddyDiscor4>
Wdym? Like the port the server config is listening on? I'd probably have it 0.0.0.0 but really it depends on what you need for your use case
<bonedaddyDiscor4>
My setup has the ipfs API port on localhost and nginx on 0.0.0.0
g2anj has joined #ipfs
<Pie-jacker875>
ipfs gateway and api on loopback and nginx on 0.0.0.0
Taoki has quit [Read error: Connection reset by peer]
Taoki has joined #ipfs
RingtailedFox has quit [Ping timeout: 260 seconds]
RingtailedFox has joined #ipfs
<bonedaddyDiscor4>
yea generally speaking thats a good idea
mowcat has joined #ipfs
irisisgay has joined #ipfs
irisisgay has quit [Client Quit]
irisisgay has joined #ipfs
NickBusey has quit [Ping timeout: 260 seconds]
MDude has quit [Quit: Going offline, see ya! (www.adiirc.com)]
cris has quit [Ping timeout: 240 seconds]
MDude has joined #ipfs
Adbray has quit [Quit: Ah! By Brain!]
cris has joined #ipfs
cris has quit [Read error: Connection reset by peer]
cris has joined #ipfs
NickBusey has joined #ipfs
NickBusey has quit [Client Quit]
dqx_ has quit [Quit: .]
NickBusey has joined #ipfs
mowcat has quit [Remote host closed the connection]
RBB has quit [Remote host closed the connection]
fuxorn has joined #ipfs
aLeSD has joined #ipfs
<aLeSD>
hi all
<aLeSD>
why I have to explicitly add a peer in p2p-circuit to find its content? Why my local node do not discover it automatically ?
cris has quit [Ping timeout: 256 seconds]
cris has joined #ipfs
null1337 has quit [Quit: Some folks are wise, and some otherwise.]
arky has joined #ipfs
airgapp has joined #ipfs
arky has quit [Quit: Ex-Chat]
tsrt^ has quit [Ping timeout: 256 seconds]
tsrt^ has joined #ipfs
xcm has joined #ipfs
Adbray has joined #ipfs
fleeky has quit [Ping timeout: 265 seconds]
fleeky has joined #ipfs
ylp has joined #ipfs
bengates has joined #ipfs
bengates has quit [Remote host closed the connection]
bengates has joined #ipfs
fleeky has quit [Ping timeout: 265 seconds]
rendar has joined #ipfs
fleeky has joined #ipfs
pecastro has joined #ipfs
Ben38 has joined #ipfs
pescobar has joined #ipfs
pescobar has joined #ipfs
RingtailedFox has quit [Ping timeout: 260 seconds]
dethos has joined #ipfs
_whitelogger has joined #ipfs
Ben38 has quit [Remote host closed the connection]
fleeky has quit [Ping timeout: 265 seconds]
irisisgay has quit [Quit: irisisgay]
misuto has quit [Ping timeout: 256 seconds]
fleeky has joined #ipfs
misuto has joined #ipfs
irisisgay has joined #ipfs
themsay has joined #ipfs
themsay has quit [Remote host closed the connection]
<moinmoin>
or is the CID just the Markel root of all the digests?
<moinmoin>
merkle*
themsay has quit [Remote host closed the connection]
themsay has joined #ipfs
Ecran has joined #ipfs
themsay has quit [Remote host closed the connection]
themsay has joined #ipfs
<moinmoin>
it does not look like it is...atleast from the diagram in the link, each digest get tranlsated to CID's first and from there, the root CID is derived
<moinmoin>
So I guess my question still remains: Digest -?-> Cid. What transforms digests to cids?
mare[m] has joined #ipfs
themsay has quit [Remote host closed the connection]
themsay has joined #ipfs
}ls{ has joined #ipfs
themsay has quit [Remote host closed the connection]
themsay has joined #ipfs
aLeSD has quit [Remote host closed the connection]
anujdasguptaDisc has joined #ipfs
xcm has quit [Remote host closed the connection]
xcm has joined #ipfs
redfish has quit [Ping timeout: 246 seconds]
themsay has quit [Remote host closed the connection]
themsay has joined #ipfs
themsay has quit [Remote host closed the connection]
themsay has joined #ipfs
redfish has joined #ipfs
ylp has quit [Quit: Leaving.]
fleeky has quit [Ping timeout: 250 seconds]
__jrjsmrtn__ has joined #ipfs
_jrjsmrtn has quit [Ping timeout: 256 seconds]
fleeky has joined #ipfs
fazo96 has quit [Ping timeout: 265 seconds]
RingtailedFox has joined #ipfs
RingtailedFox has quit [Ping timeout: 260 seconds]
fazo96 has joined #ipfs
fuxorn has quit [Quit: Konversation terminated!]
SMT_YHVH has quit [Ping timeout: 252 seconds]
epictestuser1234 has quit [Ping timeout: 256 seconds]
epictestuser1234 has joined #ipfs
Ecran has quit [Ping timeout: 240 seconds]
epictestuser1234 has quit [Ping timeout: 264 seconds]
themsay has quit [Remote host closed the connection]
fleeky has quit [Ping timeout: 258 seconds]
epictestuser1234 has joined #ipfs
themsay has joined #ipfs
jcea has joined #ipfs
SMT_YHVH has joined #ipfs
epictestuser1234 has quit [Ping timeout: 265 seconds]
hurikhan77 has quit [Ping timeout: 246 seconds]
ipfs-stackbot has quit [Remote host closed the connection]
themsay has quit [Remote host closed the connection]
themsay has joined #ipfs
fleeky has joined #ipfs
ipfs-stackbot has joined #ipfs
fleeky has quit [Ping timeout: 240 seconds]
hurikhan77 has joined #ipfs
themsay has quit [Remote host closed the connection]
themsay has joined #ipfs
llorllale has joined #ipfs
themsay has quit [Remote host closed the connection]
themsay has joined #ipfs
irisisgay has quit [Quit: irisisgay]
guardianx has joined #ipfs
fleeky has joined #ipfs
test[m]3 has joined #ipfs
aphelionzDiscor4 has joined #ipfs
cipres has joined #ipfs
cipres has quit [Ping timeout: 260 seconds]
cipres has joined #ipfs
themsay has quit [Remote host closed the connection]
themsay has joined #ipfs
xcm has quit [Remote host closed the connection]
xcm has joined #ipfs
ylp has joined #ipfs
themsay has quit [Remote host closed the connection]
themsay has joined #ipfs
fleeky has quit [Ping timeout: 265 seconds]
KempfCreative has joined #ipfs
themsay has quit [Remote host closed the connection]
themsay has joined #ipfs
xcm has quit [Read error: Connection reset by peer]
KempfCreative has quit [Ping timeout: 265 seconds]
KempfCreative has joined #ipfs
xcm has joined #ipfs
kivutar has quit [Ping timeout: 256 seconds]
moinmoin has quit [Ping timeout: 240 seconds]
fleeky has joined #ipfs
themsay has quit [Remote host closed the connection]
themsay has joined #ipfs
fleeky has quit [Ping timeout: 260 seconds]
kivutar has joined #ipfs
themsay has quit [Remote host closed the connection]
themsay has joined #ipfs
agsv has joined #ipfs
<agsv>
hello
<perguth>
hi
RingtailedFox has joined #ipfs
airgapp has quit [Quit: airgapp]
fleeky has joined #ipfs
themsay has quit [Remote host closed the connection]
themsay has joined #ipfs
guardianx has quit [Quit: Konversation terminated!]
bengates has quit [Read error: Connection reset by peer]
CGretski has joined #ipfs
<nickdex[m]>
Hey, anyone knows of a ipfs directory monitoring tool? I have ~3tb which changes frequently and its a pain to manage it manually
<agsv>
what do you mean by "monitoring"
<agsv>
logs changes?
JohnFromAtl1 has joined #ipfs
JohnFromAtl has quit [Ping timeout: 260 seconds]
lord| has quit [Read error: Connection reset by peer]
lord| has joined #ipfs
lord| has quit [Read error: Connection reset by peer]
redfish has quit [Ping timeout: 272 seconds]
lord| has joined #ipfs
lord| has quit [Read error: Connection reset by peer]
lord| has joined #ipfs
redfish has joined #ipfs
fleeky has quit [Ping timeout: 256 seconds]
<RubenKelevra>
The better idea woud be to use just ZFS. You can do a snapshots - which takes around 1 second on a large dataset and then just ask for the differences to the last snapshot and add/remove the files from IPFS
<RubenKelevra>
nickdex: well, I use a custom script which reads just an rsync log and react on the changes.
dwilliams has joined #ipfs
<RubenKelevra>
When you activate dedup and changes the recordsize to 256K it will also perfectly dedup the regular files and the files stored in a flatfs on IPFS as --raw-leaves
NickBusey has quit [Read error: Connection reset by peer]
<RubenKelevra>
It can recover from crashes, can feed a ipfs-cluster and keep a history of your dataset as an HTML file, while holding the data in the cluster for the amount of time you configured
<RubenKelevra>
* It can recover from crashes, can feed a ipfs-cluster and keep a history of your dataset as an HTML file, while holding outdated data in the cluster for the amount of time you configured
RBB has joined #ipfs
<agsv>
RubenKelevra: I wonder if pacman needs to be patched in order to be use IPFS effectivly
fleeky has joined #ipfs
<agsv>
like, to bulk download all packages simultaniously.
<RubenKelevra>
agsv: I started a discussion on the pacman development list to do exactly this
<agsv>
yea I read it, they kinda denied it though :(
<agsv>
but I wonder if we can craft a pacman-wrapper instead.
<RubenKelevra>
It's for fetching the databases without using pacman's internal functions
<RubenKelevra>
While pacman would get a mounted IPFS CID afterwards (this script is also ready but not published)
<RubenKelevra>
... as a cache folder.
mowcat has joined #ipfs
<RubenKelevra>
But this needs some serious performance boost of listing folders :/
<RubenKelevra>
And I would love to address the files via a CID instead of a filename
<RubenKelevra>
I thought about adding a list of SHA256 sum - CID and load this additionally to the database. But this get's quite hacky fast... so I decided to ask for build in support
mowcat has quit [Remote host closed the connection]
<RubenKelevra>
<agsv "like, to bulk download all packa"> You could do this of course with a dedicated daemon: IPFS prefetching basiclly
<agsv>
well but that sucks for anyone whos not into following the cluster
<RubenKelevra>
But actually, it's not really needed if you pin one file after another, you can easily reach 300 MBit/s on a very weak 1 core CPU with 2 GB memory
<RubenKelevra>
<agsv "well but that sucks for anyone w"> Well, no. The "cluster" is just a way to distribute the packages from one server to multiple servers in a reliably way. It's still just regular IPFS nodes holding some pins.
<RubenKelevra>
agsv: maybe you got my prefetching term wrong: Just a daemon asking the local database which packages need to be updated, and will pin them locally as a background task.
<RubenKelevra>
Since: You need to download them anyway
<agsv>
yea that will work.
<agsv>
Im just still wondering how many packages I will download without installing if I upgrade every two weeks
<agsv>
how many versions will I skip.
<agsv>
definately better though.
<RubenKelevra>
Well, you can just alter the frequency when this task runs, like every 2 weeks at the day you do your updates anyway.
<RubenKelevra>
I tend to do the updates if a new kernel comes out (except browser updates), and then reboot the system
<RubenKelevra>
A service could easily be configured to do exactly this and notify you, when the updates are 'ready'
<RubenKelevra>
agsv: you can get a feeling for the requency of package updates, if you look at the folders of some larger packages you've installed.