On Mon Aug 16, 2021 at 8:30 PM CEST, Drew DeVault wrote:
> It seems that you're trying to put together some sort of content
> generator, but your build isn't actually running the generator. Your
> source files were uploaded fine:
>
> gemini://onan.in/content/posts/2021-08-15_first-steps.gmi
>
> The tarball you send to pages.sr.ht does not undergo any further
> processing; we use it as-is. Any necessary pre-processing should be done
> during the build job. Only form the tarball out of the files which are
> actually a part of the final site, too.

Thank you! - I had made my mind up that the "quickstart" was a start to
finnish guide based on either keeping it real basic manually writing

Sorry for the lack of line wrapping!

Med vänlig hälsning
Robin Lundgren

Dear people,

I believe I have followed the gemini quickstart guide for custom domain and automatic deployments thouroghly but I still seem to have botched something. Wanted to reach out for help seeing where I went wrong or maybe figure out if the quickstart guide on gemini://srht.site has lead me astray somehow?

Capsule is generated via ```gssg``` as suggessted by the quickstart guide. Neat project!

Is then archived as suggested ```tar -C public -cvz . > site.tar.gz```

Then all things modified or created are *added-, commited- and pushed*, as suggested, to a git repo named according to my domain: https://git.sr.ht/~linkert/onan.in

The build manifest *site* variable has been modified and does seem to succeed just fine: https://builds.sr.ht/~linkert/job/567776

```
image: alpine/latest

Hi,

Neat tool this gssg, thanks for your work!

I checked out [Sylvain Durands](gemini://sylvaindurand.org) capsule where the posts are sorted by ```## Posts -> ### YYYY -> Articles```.

Wondering if this is something achievable with ```gssg```? Could not find much documentation on the variables available or templating.

Hope this is the right place for this question,

Med vänlig hälsning
linkert