wiki &mdash; csantosb https://infosec.press/csantosb/tag:wiki Random thoughts Wed, 13 May 2026 23:35:30 +0000 sourcehut crash course https://infosec.press/csantosb/sourcehut-crash-course <![CDATA[img br/ Everything you need to get started with sourcehut, an original and interesting #gitforge . !--more-- br/ #Sourcehut is organized in independent, closely related services. #Git repositories, #maillists, #wiki pages, #bug trackers, etc. belong to different domains, see below. They cooperate to provide a pleasant and practical experience when doing #modernhw. br/ Check the official documentation for details in all that follows. br/ Each user is given a ~alias. Each user’s service will appear under the SERVICE.sr.ht/~user domain, and are accessible in the top panels of the web interface. br/ Main services are: br/ git git.sr.ht/~user/project, #git repositories. br/ There are no groups to combine them. I use dot notation to group my projects git.sr.ht/~user/group1.prj1. br/ builds builds.sr.ht/~user, task building service, with the list of builds by the user, with user’s recent activity. br/ builds.sr.ht, similar to the previous. br/ Builds are trigger by a .build.yml manifest, or by a .build folder folder with up to 4 manifest files, at the root of a project. br/ It is also possible to automatically submit builds when a patch to a repo with build manifests is sent to a mailing list. This is achieved by appending the project name as a prefix to the subject of the message, for example [PATCH project-name]. br/ Check doc for details. br/ hub The main tab, sourcehut, gives access to the hub hub.sr.ht/~user (identical to sr.ht/~user). br/ The hub displays user’s projects. br/ Projects are groups of git repositories, #maillists and bug trackers. There may be any of them in a project. br/ Sourcehut itself is organised as a project here https://sr.ht/~sircmpwn/sourcehut, and may be used as an example. br/ todo todo.sr.ht/~user, ticket tracking service, with the list of trackers created by the user, with user’s recent activity br/ todo.sr.ht, similar to the previous br/ man man.sr.ht/~user/NAME, #wiki service to create documentation, with the wikis created by the user br/ man.sr.ht, sourcehut documentation br/ man.sr.ht/builds.sr.ht, builds service documentation br/ man.sr.ht/hub.sr.ht, hub service documentation, etc. br/ lists lists.sr.ht/~user/NAME, #email #maillists service, with the list created by the user, with user’s recent activity br/ lists.sr.ht, lists the user follows, with recent activity br/ Extra services are alse provided: br/ chat chat.sr.ht, without the user alias, is a paid service. It provides a bouncer to save history of IRC channels while not connected, and may be used from another IRC client. br/ paste.sr.ht Paste hosting service. br/ srht.site Once again, the official documentation gives in depth details about the previous. And remember, there is also hut to operate from the #cli. br/]]> img
Everything you need to get started with sourcehut, an original and interesting #gitforge .
#Sourcehut is organized in independent, closely related services. #Git repositories, #maillists, #wiki pages, #bug trackers, etc. belong to different domains, see below. They cooperate to provide a pleasant and practical experience when doing #modernhw.
Check the official documentation for details in all that follows.
Each user is given a ~alias. Each user’s service will appear under the SERVICE.sr.ht/~user domain, and are accessible in the top panels of the web interface.
Main services are:

git

git.sr.ht/~user/project, #git repositories.
There are no groups to combine them. I use dot notation to group my projects git.sr.ht/~user/group1.prj1.

builds

builds.sr.ht/~user, task building service, with the list of builds by the user, with user’s recent activity.
builds.sr.ht, similar to the previous.
Builds are trigger by a .build.yml manifest, or by a .build folder folder with up to 4 manifest files, at the root of a project.
It is also possible to automatically submit builds when a patch to a repo with build manifests is sent to a mailing list. This is achieved by appending the project name as a prefix to the subject of the message, for example [PATCH project-name].
Check doc for details.

hub

The main tab, sourcehut, gives access to the hub hub.sr.ht/~user (identical to sr.ht/~user).
The hub displays user’s projects.
Projects are groups of git repositories, #maillists and bug trackers. There may be any of them in a project.
Sourcehut itself is organised as a project here https://sr.ht/~sircmpwn/sourcehut, and may be used as an example.

todo

todo.sr.ht/~user, ticket tracking service, with the list of trackers created by the user, with user’s recent activity
todo.sr.ht, similar to the previous

man

man.sr.ht/~user/NAME, #wiki service to create documentation, with the wikis created by the user
man.sr.ht, sourcehut documentation
man.sr.ht/builds.sr.ht, builds service documentation
man.sr.ht/hub.sr.ht, hub service documentation, etc.

lists

lists.sr.ht/~user/NAME, #email #maillists service, with the list created by the user, with user’s recent activity
lists.sr.ht, lists the user follows, with recent activity

Extra services are alse provided:

chat

chat.sr.ht, without the user alias, is a paid service. It provides a bouncer to save history of IRC channels while not connected, and may be used from another IRC client.

paste.sr.ht

Paste hosting service.

srht.site

Once again, the official documentation gives in depth details about the previous. And remember, there is also hut to operate from the #cli.

]]> https://infosec.press/csantosb/sourcehut-crash-course Fri, 29 Nov 2024 14:33:48 +0000