MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Subject: Re: The brick and mortar
From: "Drew DeVault" <sir@cmpwn.com>
To: "mieum" <mieum@namu.blue>, "Arav K." <nothien@uber.space>, "Callum
 Brown" <callum@calcuode.com>, <~mieum/booksin.space@lists.sr.ht>
Date: Mon, 02 Nov 2020 09:37:00 -0400
Message-Id: <C6STH0GAJB1G.2C0E9XCLJH74@taiga>
In-Reply-To: <C6SSLF9F0X0D.3JILVV5D9W7X3@maclibre>

On Mon Nov 2, 2020 at 8:55 AM EDT, mieum wrote:
> 1. Should the source files for the capsule builder be included in the
> repo, or should that be put into its own project repo elsewhere? I'm
> not really sure how the sourcehut builds system works or how to plan
> around it :)

I would probably put them in separate repos. builds.sr.ht can manage
that just fine.

> But as far as update intervals goes, I don't know that
> something such as this would require being updated frequently. I
> wonder about how many more resources this would require (not just the
> server, but also on sourcehut's end). Alternatively, couldn't the
> server pull the changes in response to a webhook, and then have a
> rebuild triggered if changes are merged?

I would just use .build.yml in the source data repository which builds
and pushes the books up to the server over SSH. See how I deploy my blog
as an example:

https://git.sr.ht/~sircmpwn/drewdevault.com/tree/master/.build.yml

> 3. Will this require a database, or would it suffice to just source the
> data and metadata directly through the source directory structure at
> build time?

A database might not be necessary at first, but it might be helpful
later on to enable features like search.

> 4. This one kind of relates to #1, but shouldn't the git repo include
> some sort of yaml template that includes all the necessary and
> accepted fields? Perhaps there should at least be a msc/ or meta/
> folder containing stuff like that...?

Yeah, probably.

> It seemed like there was more I wanted to ask about, but I'm too groggy
> to remember. Anyway, thanks again, Arav. I'm hoping that this week I
> will have a chance to start getting some code together (by the weekend
> at the latest).

I think it's time to go less talky more codey.