[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Enterprise Guix Hosting?

From: Yasuaki Kudo
Subject: Re: Enterprise Guix Hosting?
Date: Sun, 31 Jul 2022 08:18:02 +0900

Oh wow!! Thank you everyone!!!    I will definitely show our conversation 
thread to my partners - in fact, right now!!!   Let's make it happen!!

> On Jul 31, 2022, at 01:20, Phil <> wrote:
> Olivier Dion via writes:
>>> On Sat, 30 Jul 2022, Yasuaki Kudo <> wrote:
>>> I have been exposed to the world of Docker images and Continuous
>>> Integration that seem spend most of the time downloading and building
>>> them 😅
>> Yup.  Tons of energy wasted and pollution generated.
>>> Have you heard of Guix Hosting services jusy like the Docker or Github
>>> companies target enterprises customers?
>> IMO Guix is still very niche.  Only a handful of Unix enthusiasms /
>> scientifics use it and companies are not in yet.  I might be wrong.
> I introduced Guix to a company called Quantile where I work as the
> Head of Enterprise Architecture.  Docker would have been the typical
> mainstream alternative, but for the reasons you say and others Guix was
> considered a more complete solution to a whole engineering ecosystem.
> Nix was also considered, but we went with Guix in the end.
> We have integrated it into our standard Jenkins pipeline and AWS cloud,
> and it plays a central role both in how developers work (eg replacing
> Python's virtual environments) and how software is deployed by our CI/CD 
> system.
> It was a bit of a punt, given Guix is not yet widely used outside
> academia, but it ticked all the boxes, performed well in PoC tests, and
> seemed like a solid tech decision - and one I'm still very pleased I made!
> We've done a few talks on our setup and integration with more standard
> commercial tooling - in case you haven't seen these they might be of interest:
> I'm always very interested in any discussions regarding Guix use in
> mainstream and commerical projects - I think it has a bright future in
> this space.
> Phil

reply via email to

[Prev in Thread] Current Thread [Next in Thread]