A git-pages instance #6

New issue

Open

opened 2026-08-14 14:58:52 -05:00 by amp · 15 comments

amp commented 2026-08-14 14:58:52 -05:00

Owner

Copy link

static sites basically

static sites basically

playforge-coding was assigned by amp 2026-08-14 15:02:47 -05:00

playforge-coding commented 2026-08-14 15:11:51 -05:00

Owner

Copy link

nice

nice

playforge-coding commented 2026-08-14 15:25:34 -05:00

Owner

Copy link

@amp setting it up right now!!

@amp setting it up right now!!

PPPDUD commented 2026-08-14 15:28:48 -05:00

Owner

Copy link

That sounds nice, but could we make sure to keep everything in one site repo still?

That sounds nice, but could we make sure to keep everything in one site repo still?

playforge-coding commented 2026-08-14 15:29:48 -05:00

Owner

Copy link

@PPPDUD wrote in #6 (comment):

That sounds nice, but could we make sure to keep everything in one site repo still?

hmmm. not sure if that's possible

@PPPDUD wrote in https://git.hermits.cc/hermitage/.profile/issues/6#issuecomment-2037: > That sounds nice, but could we make sure to keep everything in one site repo still? hmmm. not sure if that's possible

PPPDUD commented 2026-08-14 15:34:15 -05:00

Owner

Copy link

@playforge-coding wrote in #6 (comment):

@PPPDUD wrote in #6 (comment):

That sounds nice, but could we make sure to keep everything in one site repo still?

hmmm. not sure if that's possible

On second thought, a multi-repo model would be much better anyway. Can we find a way to still keep a repo with common resources for all sites so that they can share the same Sandstone installation?

@playforge-coding wrote in https://git.hermits.cc/hermitage/.profile/issues/6#issuecomment-2038: > @PPPDUD wrote in #6 (comment): > > > That sounds nice, but could we make sure to keep everything in one site repo still? > > hmmm. not sure if that's possible On second thought, a multi-repo model would be much better anyway. Can we find a way to still keep a repo with common resources for all sites so that they can share the same Sandstone installation?

playforge-coding commented 2026-08-14 15:35:52 -05:00

Owner

Copy link

@PPPDUD wrote in #6 (comment):

@playforge-coding wrote in #6 (comment):

@PPPDUD wrote in #6 (comment):

That sounds nice, but could we make sure to keep everything in one site repo still?

hmmm. not sure if that's possible

On second thought, a multi-repo model would be much better anyway. Can we find a way to still keep a repo with common resources for all sites so that they can share the same Sandstone installation?

no i don't think it's worth it or possible but you can research it if you want

@PPPDUD wrote in https://git.hermits.cc/hermitage/.profile/issues/6#issuecomment-2041: > @playforge-coding wrote in #6 (comment): > > > @PPPDUD wrote in #6 (comment): > > > That sounds nice, but could we make sure to keep everything in one site repo still? > > > > > > hmmm. not sure if that's possible > > On second thought, a multi-repo model would be much better anyway. Can we find a way to still keep a repo with common resources for all sites so that they can share the same Sandstone installation? no i don't think it's worth it or possible but you can research it if you want

PPPDUD commented 2026-08-14 15:42:30 -05:00

Owner

Copy link

@playforge-coding On second thought, git-pages seems a bit underdocumented. Have you considered getting a normal web server like Apache or NGINX (no preference) and just pulling from a monorepo every hour? It's a bit simplistic, but it's easy to maintain and secure.

@playforge-coding On second thought, git-pages seems a bit underdocumented. Have you considered getting a normal web server like Apache or NGINX (no preference) and just pulling from a monorepo every hour? It's a bit simplistic, but it's easy to maintain and secure.

playforge-coding commented 2026-08-14 15:43:48 -05:00

Owner

Copy link

@PPPDUD wrote in #6 (comment):

@playforge-coding On second thought, git-pages seems a bit underdocumented. Have you considered getting a normal web server like Apache or NGINX (no preference) and just pulling from a monorepo every hour? It's a bit simplistic, but it's easy to maintain and secure.

git-pages is already used at codeberg in production

@PPPDUD wrote in https://git.hermits.cc/hermitage/.profile/issues/6#issuecomment-2045: > @playforge-coding On second thought, git-pages seems a bit underdocumented. Have you considered getting a normal web server like Apache or NGINX (no preference) and just pulling from a monorepo every hour? It's a bit simplistic, but it's easy to maintain and secure. git-pages is already used at codeberg in production

PPPDUD commented 2026-08-14 15:45:36 -05:00

Owner

Copy link

@playforge-coding wrote in #6 (comment):

@PPPDUD wrote in #6 (comment):

@playforge-coding On second thought, git-pages seems a bit underdocumented. Have you considered getting a normal web server like Apache or NGINX (no preference) and just pulling from a monorepo every hour? It's a bit simplistic, but it's easy to maintain and secure.

git-pages is already used at codeberg in production

Sure, but they're a pretty big forge. I think that the simplest option would be the best one for right now.

@playforge-coding wrote in https://git.hermits.cc/hermitage/.profile/issues/6#issuecomment-2046: > @PPPDUD wrote in #6 (comment): > > > @playforge-coding On second thought, git-pages seems a bit underdocumented. Have you considered getting a normal web server like Apache or NGINX (no preference) and just pulling from a monorepo every hour? It's a bit simplistic, but it's easy to maintain and secure. > > git-pages is already used at codeberg in production Sure, but they're a pretty big forge. I think that the simplest option would be the best one for right now.

playforge-coding commented 2026-08-14 15:47:21 -05:00

Owner

Copy link

@PPPDUD wrote in #6 (comment):

@playforge-coding wrote in #6 (comment):

@PPPDUD wrote in #6 (comment):

@playforge-coding On second thought, git-pages seems a bit underdocumented. Have you considered getting a normal web server like Apache or NGINX (no preference) and just pulling from a monorepo every hour? It's a bit simplistic, but it's easy to maintain and secure.

git-pages is already used at codeberg in production

Sure, but they're a pretty big forge. I think that the simplest option would be the best one for right now.

alright but honestly it would require probably more work to set up

@PPPDUD wrote in https://git.hermits.cc/hermitage/.profile/issues/6#issuecomment-2047: > @playforge-coding wrote in #6 (comment): > > > @PPPDUD wrote in #6 (comment): > > > @playforge-coding On second thought, git-pages seems a bit underdocumented. Have you considered getting a normal web server like Apache or NGINX (no preference) and just pulling from a monorepo every hour? It's a bit simplistic, but it's easy to maintain and secure. > > > > > > git-pages is already used at codeberg in production > > Sure, but they're a pretty big forge. I think that the simplest option would be the best one for right now. alright but honestly it would require probably more work to set up

PPPDUD commented 2026-08-14 15:47:59 -05:00

Owner

Copy link

@playforge-coding wrote in #6 (comment):

@PPPDUD wrote in #6 (comment):

@playforge-coding wrote in #6 (comment):

@PPPDUD wrote in #6 (comment):

@playforge-coding On second thought, git-pages seems a bit underdocumented. Have you considered getting a normal web server like Apache or NGINX (no preference) and just pulling from a monorepo every hour? It's a bit simplistic, but it's easy to maintain and secure.

git-pages is already used at codeberg in production

Sure, but they're a pretty big forge. I think that the simplest option would be the best one for right now.

alright but honestly it would require probably more work to set up

Well, it should be simple to maintain once it's up.

@playforge-coding wrote in https://git.hermits.cc/hermitage/.profile/issues/6#issuecomment-2049: > @PPPDUD wrote in #6 (comment): > > > @playforge-coding wrote in #6 (comment): > > > @PPPDUD wrote in #6 (comment): > > > > @playforge-coding On second thought, git-pages seems a bit underdocumented. Have you considered getting a normal web server like Apache or NGINX (no preference) and just pulling from a monorepo every hour? It's a bit simplistic, but it's easy to maintain and secure. > > > > > > > > > git-pages is already used at codeberg in production > > > > > > Sure, but they're a pretty big forge. I think that the simplest option would be the best one for right now. > > alright but honestly it would require probably more work to set up Well, it should be simple to maintain once it's up.

👍 1

playforge-coding commented 2026-08-14 15:52:37 -05:00

Owner

Copy link

@PPPDUD wrote in #6 (comment):

[...]

Well, it should be simple to maintain once it's up.

OK, how about a compromise:

We use git-pages, but there are also shared assets stored on the website that any page can access (like the sandstone theme)

@PPPDUD wrote in https://git.hermits.cc/hermitage/.profile/issues/6#issuecomment-2050: [...] > Well, it should be simple to maintain once it's up. OK, how about a compromise: We use git-pages, but there are also shared assets stored on the website that any page can access (like the sandstone theme)

PPPDUD commented 2026-08-14 16:54:46 -05:00

Owner

Copy link

@playforge-coding wrote in #6 (comment):

@PPPDUD wrote in #6 (comment):

[...]

Well, it should be simple to maintain once it's up.

OK, how about a compromise:

We use git-pages, but there are also shared assets stored on the website that any page can access (like the sandstone theme)

Sounds good.

@playforge-coding wrote in https://git.hermits.cc/hermitage/.profile/issues/6#issuecomment-2051: > @PPPDUD wrote in #6 (comment): > > [...] > > > Well, it should be simple to maintain once it's up. > > OK, how about a compromise: > > We use git-pages, but there are also shared assets stored on the website that any page can access (like the sandstone theme) Sounds good.

PPPDUD commented 2026-08-14 17:56:58 -05:00

Owner

Copy link

@playforge-coding What if we gave Sandstone its own dedicated sandstone.hermits.cc subdomain to make maintenance easier, and perhaps we also make cdn.hermits.cc for non-Sandstone shared resources?

@playforge-coding What if we gave Sandstone its own dedicated `sandstone.hermits.cc` subdomain to make maintenance easier, and perhaps we also make `cdn.hermits.cc` for non-Sandstone shared resources?

playforge-coding commented 2026-08-14 18:06:57 -05:00

Owner

Copy link

@PPPDUD wrote in #6 (comment):

@playforge-coding What if we gave Sandstone its own dedicated sandstone.hermits.cc subdomain to make maintenance easier, and perhaps we also make cdn.hermits.cc for non-Sandstone shared resources?

I suppose that could work. Sure

@PPPDUD wrote in https://git.hermits.cc/hermitage/.profile/issues/6#issuecomment-2085: > @playforge-coding What if we gave Sandstone its own dedicated `sandstone.hermits.cc` subdomain to make maintenance easier, and perhaps we also make `cdn.hermits.cc` for non-Sandstone shared resources? I suppose that could work. Sure

👍 1

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

No results found.

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

playforge-coding

3 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

hermitage/.profile#6

No description provided.