atc endpoint for fossil repos

maiki
1

@tim, I’d like to setup up fossil.allthe.codes as an endpoint to sync our fossil repos.

I imagine we eventually setup various VCS on sub-domains and eventually move gitea to git.allthe.codes, but that’s down the road.

The setup I have in mind is shared host (so I’ll set it up and you can update the DNS), and we’d both have shell access.

In CGI mode fossil is just returning results, so I imagine the structure to be a single index page and everything else a two-liner pointing to a directory and the fossil binary.

This way we can have distinct groups, and I can have /maiki/dotfiles and /tule/core and /interi/deployment.

Thoughts? This is a low-budge way to try out the tech, and fits well with out small group of coders/preservers.

Also, do you want a public website at https://fossil.allthe.codes/timotheus/deep-thoughts?! :slight_smile:

1 Like
2

I’m glad I got this out of my head. Nevermind. atc goes with git, because that needs a domain in that sense. git is a thing that needs a domain, like Discourse and talkgroup. fossil is different, and can live in places like, maiki.interi.org/fossils/, which make them so attractive: they provide a better system design, allowing individual cells to be more resilient, rather than my brain saying, “hey, throw it all in one place!”.

@tim, you ought to look into hosting fossils on RPis, it would work really well!

1 Like