From: Arun Isaac <arunisaac@systemreboot.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: zimoun <zimon.toutoune@gmail.com>,
Olivier Dion <olivier.dion@polymtl.ca>, jgart <jgart@dismail.de>,
Guix Devel <guix-devel@gnu.org>,
Mathieu Othacehe <othacehe@gnu.org>
Subject: Re: Cuirass and SQL
Date: Tue, 31 May 2022 00:42:38 +0530 [thread overview]
Message-ID: <87sfoqdec9.fsf@systemreboot.net> (raw)
In-Reply-To: <87wne310kf.fsf@gnu.org>
Hi Ludo,
> Years before, Hydra (https://nixos.org/hydra) also dropped its SQLite
> backend in favor of PostgreSQL only.
>
> Like you, not being a database person, I liked that SQLite was easy to
> deploy and had a clear model: it just touches this one file and that’s
> it.
Exactly! :-)
If we use guile-dbi, it should be possible to support both sqlite and
postgresql. Popular projects like Nextcloud do allow the user to choose
their preferred database system. But, then again, Cuirass is built for
very large scale. So, perhaps it is best to not try and also cover the
small scale end.
> SQLite may be good enough at a small scale; the problem is that you
> never know how long it’ll be before the project you’re hosting is no
> longer small-scale.
Scale may not be an issue at least for the CI. Unlike Guix which needs
to rebuild the entire world of software, most other software are only
going to have a handful of jobs---easily less than 5 or less than 10 in
the worst case. So, even if we trigger all these jobs on every commit,
the total number of runs will easily be manageable with sqlite.
Regards,
Arun
next prev parent reply other threads:[~2022-05-30 19:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 23:26 Arun Isaac Presentation on guix-forge this Saturday jgart
2022-05-24 23:45 ` Tobias Geerinckx-Rice
2022-05-25 0:06 ` jgart
2022-05-25 6:29 ` Pjotr Prins
2022-05-25 7:27 ` Blake Shaw
2022-05-26 7:17 ` Arun Isaac
2022-05-30 15:55 ` Ludovic Courtès
2022-05-30 19:02 ` Arun Isaac
2022-05-30 19:31 ` jgart
2022-05-31 1:07 ` jgart
2022-08-16 12:25 ` Christine Lemmer-Webber
2022-05-25 9:07 ` zimoun
2022-05-25 16:25 ` jgart
2022-05-25 14:14 ` Olivier Dion via Development of GNU Guix and the GNU System distribution.
2022-05-25 18:54 ` Arun Isaac
2022-05-25 19:41 ` Olivier Dion via Development of GNU Guix and the GNU System distribution.
2022-05-26 7:28 ` Arun Isaac
2022-05-26 15:13 ` Olivier Dion via Development of GNU Guix and the GNU System distribution.
2022-05-26 15:52 ` Arun Isaac
2022-05-27 9:06 ` Cuirass and SQL zimoun
2022-05-28 7:28 ` Blake Shaw
2022-05-28 8:45 ` Arun Isaac
2022-05-28 14:25 ` Ryan Prior
2022-05-28 15:30 ` Arun Isaac
2022-05-30 15:50 ` Ludovic Courtès
2022-05-30 19:12 ` Arun Isaac [this message]
2022-06-01 16:24 ` Ludovic Courtès
2022-05-28 18:01 ` jgart
2022-05-30 15:02 ` Olivier Dion via Development of GNU Guix and the GNU System distribution.
2022-05-28 12:12 ` Arun Isaac Presentation on guix-forge this Saturday david larsson
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=87sfoqdec9.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.de \
--cc=ludo@gnu.org \
--cc=olivier.dion@polymtl.ca \
--cc=othacehe@gnu.org \
--cc=zimon.toutoune@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).