4 ms·

It's hard to give you any specific recommendations with so little context, but I will try. For starters, I should point out that you can't really compare Guix

It's hard to give you any specific recommendations with so little context, but I will try. For starters, I should point out that you can't really compare Guix directly to Docker. Guix is a package manager, Docker isn't. The article talks about 'guix pack', which makes it possible for Guix to interoperate with non-Guix systems, and one supported system is Docker. You can deploy software with just Guix, too, either on GuixSD or a foreign distro with Guix installed. Anyway, in your Dockerfile I see that your application uses Python and you do some package management and service management stuff that is mixed together. In Guix, these things are separated. So the first step would be to define a package for your software, and then you would deploy that package. For a real world example of a Python application, here is what the AWS CLI package looks like: (define-public awscli (package (name "awscli") (version "1.14.41") (source (origin (method url-fetch) (uri (pypi-uri name version)) (sha256 (base32 "0sispclx263lybbk19zp1n9yhg8xxx4jddypzgi24vpjaqnsbwlc")))) (build-system python-build-system) (propagated-inputs `(("python-colorama" ,python-colorama) ("python-botocore" ,python-botocore) ("python-s3transfer" ,python-s3transfer) ("python-docutils" ,python-docutils) ("python-pyyaml" ,python-pyyaml) ("python-rsa" ,python-rsa))) (arguments '(#:tests? #f)) (home-page "https://aws.amazon.com/cli/") (synopsis "Command line client for AWS") (description "AWS CLI provides a unified command line interface to the Amazon Web Services (AWS) API.") (license license:asl2.0))) The package recipe contains all the metadata, build instructions, and dependencies. Now that you have a package, it can be built with Guix and then deployed in a variety of ways. Judging from the Dockerfile, your software is some daemon that listens on port 8080, so: * You can install the software directly using 'guix package -i your-package-name' and run the notify.py program. Good for trying things out. * If you are deploying to the Guix system distribution, you could write a service definition so that you can manage the daemon via the init system. The service would take care of creating the notifier user and group, starting the service on boot, etc. * You could use 'guix pack --format=docker' to export an image suitable for running with 'docker load' * You could use a different 'guix pack' format (and maybe make it relocatable) for running on some other non-Guix system I should also add that I don't think the work is fully done yet on handling the entirety of Docker use-cases. It's a work in progress. I can think of a number of things that I want to add to Guix to make this workflow better that I haven't had a chance to hack on yet.

justinsaccount 8y ago
That's interesting, but where does it specify which python version is used and the version of all the dependencies? If the versions are specified in the 'python-botocore' type definitions, how do you install more than one version of a library? Does guix only track the latest version of dependencies or can you request any version of something?
- rekado 8y ago
  Packages in Guix are just Scheme variables. The package here uses the `python-build-system`, which defaults to the latest version of Python, but you can override that by specifying `(arguments '(#:python ,my-python))`, where `my-python` is a variable bound to a package value of the Python variant that you want to use. You can easily install more than one version of a package as long as you have a package definition for it. You can install different variants (not just different versions) into separate profiles. Guix is a Scheme library providing lots of variables that are bound to package values. These package values may have links to other packages (that's done with quasiquotation). Together they form a big graph of packages with zero degrees of freedom. Every version of Guix provides a slightly different variant of this package graph. When installing any package you instantiate a subset of this particular graph. Updating or modifying Guix gives you a different graph. In order to keep things manageable we try to keep the number of variants of any particular package in Guix to a minimum, but you can install older variants by using an older version of Guix; or you can add new variables that are bound to package variants or different versions and install those. It's very convenient and conceptually simple.

justinsaccount 8y ago

That's interesting, but where does it specify which python version is used and the version of all the dependencies? If the versions are specified in the 'python-botocore' type definitions, how do you install more than one version of a library? Does guix only track the latest version of dependencies or can you request any version of something?

rekado 8y ago
Packages in Guix are just Scheme variables. The package here uses the `python-build-system`, which defaults to the latest version of Python, but you can override that by specifying `(arguments '(#:python ,my-python))`, where `my-python` is a variable bound to a package value of the Python variant that you want to use. You can easily install more than one version of a package as long as you have a package definition for it. You can install different variants (not just different versions) into separate profiles. Guix is a Scheme library providing lots of variables that are bound to package values. These package values may have links to other packages (that's done with quasiquotation). Together they form a big graph of packages with zero degrees of freedom. Every version of Guix provides a slightly different variant of this package graph. When installing any package you instantiate a subset of this particular graph. Updating or modifying Guix gives you a different graph. In order to keep things manageable we try to keep the number of variants of any particular package in Guix to a minimum, but you can install older variants by using an older version of Guix; or you can add new variables that are bound to package variants or different versions and install those. It's very convenient and conceptually simple.