From: Benjamin Slade <beoram@gmail.com>
To: Yasuaki Kudo <yasu@yasuaki.com>
Cc: Phil <phil@beadling.co.uk>,
Olivier Dion <olivier.dion@polymtl.ca>,
help-guix@gnu.org
Subject: Re: Enterprise Guix Hosting?
Date: Sun, 31 Jul 2022 00:42:34 +0000 (UTC) [thread overview]
Message-ID: <0c1f853a-f613-4ad2-9eda-05940cee5a23@gmail.com> (raw)
In-Reply-To: <961019EF-219A-4DAE-BED3-4DCB7BC386B8@yasuaki.com>
Not something I've tried personally, but maybe PantherX (Guix-based) could be relevant here? https://www.pantherx.org/
30 Jul 2022 17:18:13 Yasuaki Kudo <yasu@yasuaki.com>:
> 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 <phil@beadling.co.uk> wrote:
>>
>>
>> Olivier Dion via writes:
>>
>>>> On Sat, 30 Jul 2022, Yasuaki Kudo <yasu@yasuaki.com> 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:
>> https://www.cloudbees.com/videos/purely-functional-ci-cd-pipeline-using-jenkins-with-guix
>> https://xana.lepiller.eu/guix-days-2022/guix-days-2022-guix-aws-lambda.mkv
>>
>> 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
next prev parent reply other threads:[~2022-07-31 0:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 23:23 Enterprise Guix Hosting? Yasuaki Kudo
2022-07-30 14:36 ` Olivier Dion via
2022-07-30 16:20 ` Phil
2022-07-30 23:18 ` Yasuaki Kudo
2022-07-31 0:42 ` Benjamin Slade [this message]
2022-07-31 11:01 ` Phil
2022-08-09 20:37 ` Ludovic Courtès
2022-08-09 22:24 ` Yasuaki Kudo
2022-08-14 9:53 ` Phil
2022-08-14 22:03 ` Yasuaki Kudo
2022-08-15 20:50 ` Phil
2022-08-25 18:37 ` Olivier Dion via
2022-08-26 6:40 ` Yasuaki Kudo
2022-10-12 9:55 ` Ade Malsasa Akbar
2022-10-12 10:18 ` Olivier Dion via
2022-08-26 7:24 ` Ricardo Wurmus
2022-08-31 1:42 ` Thompson, David
2022-08-31 6:33 ` Ricardo Wurmus
2022-08-31 10:46 ` [EXT] " Thompson, David
2022-08-31 11:42 ` Olivier Dion via
2022-08-31 12:54 ` Thompson, David
2022-09-05 19:38 ` [EXT] " Ludovic Courtès
2023-01-23 15:34 ` declarative containers (was Re: [EXT] Re: Enterprise Guix Hosting?) Giovanni Biscuolo
2023-01-23 16:48 ` Przemysław Kamiński
2023-01-23 17:59 ` Wojtek Kosior via
2022-09-05 19:42 ` Enterprise Guix Hosting? Ludovic Courtès
2022-10-07 11:03 ` zimoun
2022-10-08 16:23 ` Phil
2022-10-10 7:58 ` zimoun
2022-10-10 10:30 ` (
2022-10-10 10:49 ` zimoun
2022-10-10 19:35 ` Phil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0c1f853a-f613-4ad2-9eda-05940cee5a23@gmail.com \
--to=beoram@gmail.com \
--cc=help-guix@gnu.org \
--cc=olivier.dion@polymtl.ca \
--cc=phil@beadling.co.uk \
--cc=yasu@yasuaki.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).