Thanks for the good work.

I have a webpage hosted at gavox.srht.site.

To generate the site I use hugo, as explained in 
https://srht.site/quickstart

(this is, I use markdown files and hugo generates the html, css, etc 
that is needed to render the site)

To update the website I follow the procedure in explained in 
https://srht.site/automating-deployments

(that is, I have a git repository at ~gavox/gavox.srht.site to which I 
send the updates via git push)

Now, my question is, which files should be included in the repository? 
Specifically, do I need to register changes to the "public/" directory?

Thanks.

Sincerely,

Gabriel Villalobos,

On Mon Apr 8, 2024 at 9:51 PM CEST, Gabriel villalobos wrote:
> ...
> Now, my question is, which files should be included in the repository? 
> Specifically, do I need to register changes to the "public/" directory?

No, the `public/` directory should not be tracked by git (i.e. add it to
.gitignore).

You could add a build manifest to generate and publish the web pages via
builds.sr.ht every time you push changes to the repo, take this example:

    https://git.sr.ht/~sircmpwn/pages.sr.ht-examples/tree/master/item/hugo.yml

BR,
wth

Thank you for your answer.

On Mon, Apr 8, 2024 at 6:17 PM Tianhao Wang <shrik3@mailbox.org> wrote:
>
> On Mon Apr 8, 2024 at 9:51 PM CEST, Gabriel villalobos wrote:
> > ...
> > Now, my question is, which files should be included in the repository?
> > Specifically, do I need to register changes to the "public/" directory?
>
> No, the `public/` directory should not be tracked by git (i.e. add it to
> .gitignore).
>
> You could add a build manifest to generate and publish the web pages via
> builds.sr.ht every time you push changes to the repo, take this example:
>
>     https://git.sr.ht/~sircmpwn/pages.sr.ht-examples/tree/master/item/hugo.yml
>
> BR,
> wth



-- 
Gabriel Villalobos Camargo


===============
Profesor Ciencia de Datos ESAP
Profesor MM&S UTADEO
Doctor en Ciencias - Física, UN
===============

> You could add a build manifest to generate and publish the web pages via
> builds.sr.ht every time you push changes to the repo, take this example:
> 
>     https://git.sr.ht/~sircmpwn/pages.sr.ht-examples/tree/master/item/hugo.yml

Please, note that acurl is deprecated. It is recommended to use hut
instead:

	https://srht.site/quickstart

It simplifies things as you don't need to create the archive, see the
doc:

	https://git.sr.ht/~emersion/hut/tree/master/item/doc/hut.1.scd

I use it with the Sphinx, e.g.:

	https://git.sr.ht/~qeef/dd-hot-tm/tree/master/item/.build.yml

Jiri Vlasak <jiri.hubacek@gmail.com> writes:

>> You could add a build manifest to generate and publish the web pages via
>> builds.sr.ht every time you push changes to the repo, take this example:
>> 
>>     https://git.sr.ht/~sircmpwn/pages.sr.ht-examples/tree/master/item/hugo.yml
>
> Please, note that acurl is deprecated. It is recommended to use hut
> instead

Indeed, I have an updated version of that Hugo example as well:

        https://git.sr.ht/~rensoliemans/pages.sr.ht-examples/tree/master/item/hugo.yml