Hi,
Arun Isaac skribis:
>> 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.
>
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 u
Hi,
Arun Isaac skribis:
>> Initially, Cuirass was using SQLite but then switched [1] to
>> PostgreSQL. The main reason is scalability.
>
> Ah, I see. I didn't know that.
Years before, Hydra (https://nixos.org/hydra) also dropped its SQLite
backend in favor of PostgreSQL only.
Like you, not be
On Fri, 27 May 2022, zimoun wrote:
> Initially, Cuirass was using SQLite but then switched [1] to
> PostgreSQL. The main reason is scalability.
Make sens for the main CI used by Guix or for an organization.
> I do not know if it is a technically doable to have two SQL backends and
> let the us
On Fri, 27 May 2022 11:06:24 +0200 zimoun wrote:
Hi Guixers,
Here is the video recording from today:
https://archive.org/details/guix-forge-arun-isaac-may-28-2022
enjoy,
jgart
https://whereis.xn--q9jyb4c/
> For simplicity in a single-system deployment I recommend running
> postgres in "trust" mode and listen on a local unix socket rather than
> exposing it to the network. This allows you to use the same access
> control for Postgres that you'd use for an sqlite3 db file: file
> permissions.
This
--- Original Message ---
On Saturday, May 28th, 2022 at 8:45 AM, Arun Isaac
wrote:
> There's still the complexity of backing up a PostgreSQL
> database
How much easier is sqlite3?
I host a Postgres server on DigitalOcean with automatic db backup. I've had to
restore, it's easy and it
Hi zimoun,
> Initially, Cuirass was using SQLite but then switched [1] to
> PostgreSQL. The main reason is scalability.
Ah, I see. I didn't know that.
> I do not know if it is a technically doable to have two SQL backends and
> let the user pick the one they prefer. For sure, it is not doabl
For any cuirass-curious readers, I want to say I deployed it on Linode a
week ago and its been one of the most "just works" out-of-the-box tools in
the guix arsenal that I've encountered. It was really easy and painless to
get going, and makes "pinning" milestone system & profile generations a
bree
Hi,
On jeu., 26 mai 2022 at 00:24, Arun Isaac wrote:
>> Quick question about guix-forge. Why laminar instead of cuirass as
>> the CI?
>
> Two reasons:
>
> - Cuirass requires a PostgreSQL database, but I wanted guix-forge to be
> as stateless as possible and definitely not require a complex da
10 matches
Mail list logo
