Here is an interesting application of IPFS to serve a static website:
https://withblue.ink/2019/03/20/hugo-and-ipfs-how-this-blog-works-and-scales.html
Ludo and Me have played with it at the Reproducible Build summit, and it works
quite well indeed!
Ludo is working Guile bindings.
I'll implement the service later, but I'd really like to get the first contract
money first. Alicia told me there were some issues with the University because
they is
IPFS is working like a charm. Thanks Pierre a.o!
Pj.
> Now it is time to finish polishing a service/services for it no?
Would be a good idea indeed!
--
Pierre Neidhardt
https://ambrevar.xyz/
signature.asc
Description: PGP signature
On 2018-12-10 02:52, Pjotr Prins wrote:
On Sun, Dec 09, 2018 at 09:19:20PM +0100, Pierre Neidhardt wrote:
I found a solution to package IPFS without gx, so go-ipfs has just hit master!
That is excellent news. That means we have a way of distributing
materials in a robust fashion.
Congratulat
On Sun, Dec 09, 2018 at 09:19:20PM +0100, Pierre Neidhardt wrote:
> I found a solution to package IPFS without gx, so go-ipfs has just hit master!
That is excellent news. That means we have a way of distributing
materials in a robust fashion.
Pj.
I found a solution to package IPFS without gx, so go-ipfs has just hit master!
I'll put the "gx-download" on hold since it's not used for anything else at the
moment.
--
Pierre Neidhardt
https://ambrevar.xyz/
signature.asc
Description: PGP signature
Hello,
Gábor Boskovits skribis:
> Pierre Neidhardt ezt írta (időpont: 2018. okt. 25., Cs
> 20:11):
>
>>
>> > What does ‘gx’ tell you in the builder?
>>
>> Sorry, I don't understand what you are asking. The following is the
>> output I
>> get when I attempt to build a package using gx-fetch:
>>
Pierre Neidhardt ezt írta (időpont: 2018. okt. 25., Cs
20:11):
>
> > What does ‘gx’ tell you in the builder?
>
> Sorry, I don't understand what you are asking. The following is the
> output I
> get when I attempt to build a package using gx-fetch:
>
> --8<---cut here---st
Hello!
Pierre Neidhardt skribis:
>> To be precise, builders of fixed-output derivations (derivations for
>> which the hash of the result is known in advance) have network access.
>
> Oh, I did not know this detail. Thanks for pointing it out!
[...]
> + (mlet %store-monad ((guile (package->de
> To be precise, builders of fixed-output derivations (derivations for
> which the hash of the result is known in advance) have network access.
Oh, I did not know this detail. Thanks for pointing it out!
> How did you define ‘gx-fetch’?
It's on the wip-ipfs2 branch. Find the (broken) patch at
Hi!
Pierre Neidhardt skribis:
>> As discussed before (I think?), builds are performed in an isolated
>> environment without network access—this is one of the measures taken to
>> guarantee build reproducibility and statelessness.
>>
>> So what you’re doing here (running “gx” in a derivation) ca
> As discussed before (I think?), builds are performed in an isolated
> environment without network access—this is one of the measures taken to
> guarantee build reproducibility and statelessness.
>
> So what you’re doing here (running “gx” in a derivation) cannot work.
No, the above error comes
Hi,
Pierre Neidhardt skribis:
> ERROR: from shell.Get(): Post
> https://ipfs.io/api/v0/get?arg=QmSP88ryZkHSRn1fnngAaV2Vcn63WUJzAavnRM9CVdU1Ky&create=true:
> x509: failed to load system roots and no roots provided
> retrying fetch QmSP88ryZkHSRn1fnngAaV2Vcn63WUJzAavnRM9CVdU1Ky after a
> second
Hello,
Pjotr Prins skribis:
> Nix, these days, has a two phase build. In the second phase you get network
> access where you can run network tests. That is kinda interesting.
Interesting, do you have links to documentation or code?
Thanks,
Ludo.
I've started writing "gx-download.scm", it's on the wip-ipfs branch.
On the ipfs-go-ipfs-cmdkit example, I get this error:
--8<---cut here---start->8---
> ./pre-inst-env guix build -K ipfs-go-ipfs-cmdkit
;;; note: source file /home/ambrevar/projects/guix/guix/g
On Mon, Oct 15, 2018 at 12:40:18PM +0200, Pierre Neidhardt wrote:
> No, Go programs typically refer only to repositories, not to their commit.
> This
> is precisely why it's a problem. Golang's dependency management was not very
> well designed I'm afraid.
>
> Misunderstanding?
I think you and
On Tue, Oct 16, 2018 at 01:51:29PM +0200, Ludovic Courtès wrote:
> That won’t work: there’s not network access in the build environment in
> order to maximize reproducibility.
IPFS-gx, if I am correct, is just like git for downloading sources. So
we could do gx-fetch in the download phase.
> So I
Hi,
Pierre Neidhardt skribis:
> Back to IPFS: I have some bad news :(
> The import path are hard-coded to use "gx/ipfs...", for instance
>
> import (
> cid "gx/ipfs/QmPSQnBKM9g7BaUcZCvswUJVscQ1ipjmwxN5PXCjkp9EQ7/go-cid"
> )
>
> so this won't build directly. I see two possibilities:
>
> 1.
FWIW, that reads to me like: "this program is extremely brittle and
unfit for distribution in any distro - here, take our blob instead"
perhaps guix is in a unique position to accommodate such constrained
dependency requirements; but such caveat warnings are indicative of a
project that is still i
On Mon, Oct 15, 2018 at 01:40:45PM +0200, Pierre Neidhardt wrote:
> > I'm not much into go, but it seems, that most of the times it is safe
> > to use another version of dependencies.
>
> This is unrelated to Go: it's safe as long as there is no API breakage. My
> understanding of the IPFS projec
> Now, there are apparently several dependency management tools in use,
Yup, and it's still not fixed :(
Thanks for the patch, I'll try to use it and report :)
--
Pierre Neidhardt
https://ambrevar.xyz/
signature.asc
Description: PGP signature
Pierre Neidhardt skribis:
>> FWIW Pierre-Antoine (who was working with me as an intern on Guix-HPC)
>> has given me the last revision of the gopkg importer, which I’m planning
>> to include soon. It might be useful to you!
>
> Absolutely! Could you share the code now so that I can start using i
> I'm not much into go, but it seems, that most of the times it is safe
> to use another version of dependencies.
This is unrelated to Go: it's safe as long as there is no API breakage. My
understanding of the IPFS project is that they don't want to make that kind of
assumptions.
> This seems to
Pierre Neidhardt ezt írta (időpont: 2018. okt.
15., H, 12:40):
>
>
> > FWIW Pierre-Antoine (who was working with me as an intern on Guix-HPC)
> > has given me the last revision of the gopkg importer, which I’m planning
> > to include soon. It might be useful to you!
>
> Absolutely! Could you sha
> FWIW Pierre-Antoine (who was working with me as an intern on Guix-HPC)
> has given me the last revision of the gopkg importer, which I’m planning
> to include soon. It might be useful to you!
Absolutely! Could you share the code now so that I can start using it? Thanks!
> This seems to be t
Hello!
Pierre Neidhardt skribis:
> I'm in the process of packaging IPFS.
> It has about 100 dependencies, most of which are currently missing in
> Guix, so that's gonna take me some hours :p
FWIW Pierre-Antoine (who was working with me as an intern on Guix-HPC)
has given me the last revision of
On Mon, Oct 15, 2018 at 09:59:04AM +0200, Pierre Neidhardt wrote:
> Hi Guix!
>
> I'm in the process of packaging IPFS.
> It has about 100 dependencies, most of which are currently missing in
> Guix, so that's gonna take me some hours :p
> Thankfully Go is rather straightforward to package so that
On Mon, Oct 15, 2018 at 09:59:04AM +0200, Pierre Neidhardt wrote:
> Hi Guix!
>
> I'm in the process of packaging IPFS.
> It has about 100 dependencies, most of which are currently missing in
> Guix, so that's gonna take me some hours :p
> Thankfully Go is rather straightforward to package so that
29 matches
Mail list logo
