From: Raffael Mancini <raffael@mancini.lu>
To: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Packaging a django application
Date: Sun, 30 Apr 2023 22:59:02 +0200 (CEST) [thread overview]
Message-ID: <363229649.1374751.1682888342312@office.mailbox.org> (raw)
Hello,
I'm trying to deploy a django application on guix system using nginx as a reverse proxy and gunicorn as wsgi server. I have written the prototype of a gunicorn service based on the already packaged gunicorn by extending the shepherd-service-type. This new service seems to work to some extent and I will hopefully be able to submit it as a patch once it's ready. The end goal is a simple extensible django-application-service-type that you could extend in order to easily deploy any kind of django application.
In order to serve my django application, would the best approach be to just create a regular guix package for it and reference it in the gunicorn configuration? What's a good method to translate a very long requirements.txt file to a guix package? Is there anyone who has done this already? How would you deal with the read/write part of the application like uploads or a sqlite3 database since the store items are read-only?
I was also wondering if it's possible to somehow specify the guix profile used in the execution of gunicorn and "abuse" is as a pip replacement. I could thus iteratively create a profile with the needed dependencies to run my application and then configure the gunicorn daemon to use it.
Thanks for any input on this!
Raffael
reply other threads:[~2023-04-30 20:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=363229649.1374751.1682888342312@office.mailbox.org \
--to=raffael@mancini.lu \
--cc=help-guix@gnu.org \
/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).