#ForgeJo

17 Beiträge13 Beteiligte3 Beiträge heute

DrWhoZee<a href="https://nerdculture.de/@fluchtkapsel" class="u-url mention">@fluchtkapsel</a> <a href="https://social.anoxinon.de/@unwichtigeallgemeine" class="u-url mention">@unwichtigeallgemeine</a> I‘m using caddy with a beefed up companion container that accepts rsync from a workflow action. <a href="https://troet.cafe/tags/worksForMe" class="mention hashtag" rel="tag">#worksForMe</a> <a href="https://troet.cafe/tags/caddy" class="mention hashtag" rel="tag">#caddy</a> <a href="https://troet.cafe/tags/forgejo" class="mention hashtag" rel="tag">#forgejo</a>

Phil<code>gptel-org-tools</code> update. 1. Cloned to <a href="https://codeberg.org/bajsicki/gptel-org-tools" rel="nofollow noopener noreferrer" target="_blank">https://codeberg.org/bajsicki/gptel-org-tools</a>, and all future work will be happening on Codeberg. 2. Added <code>gptel-org-tools-result-limit</code> and a helper function for it. This sets a hard limit on the number of characters a tool can return. If it's over that, the LLM is prompted to be more specific in its query. Not applied to all tools, just the ones that are likely to blow up the context window. 3. Added docstrings for the functions called by the tools, so LLMs can look up their definitions. 4. Improved the precision of some tool descriptions so instructions are easier to follow. 5. Some minor improvements w/r/t function names and calls, logic, etc. Basic QA. Now, as a user: 1. I'm finding it increasingly frustrating that Gemma 3 refuses to follow instructions. So here's a PSA: Gemma 3 doesn't respect the system prompt. It treats it just the same as any other user input. 2. Mistral 24B is a mixed bag. I'm not sure if it's my settings or something else, but it fairly consistently ends up looping; it'll call the same tool over and over again with the exact same arguments. This happens with other models as well, but not nearly as frequently. 3. Qwen 2.5 14B: pretty dang good, I'd say. The Cogito fine-tune is also surprisingly usable. 4. Prompting: I have found that a good, detailed system prompt tends to /somewhat/ improve results, especially if it contains clear directions on where to look for things related to specific topics. I'm still in the middle of writing one that's accurate to my Emacs set-up, but when I do finish it, it'll be in the repository as an example. 5. One issue that I still struggle with is that the LLMs don't take any time to process the user request. Often they'll find some relevant information in one file, and then decide that's enough and just refuse to look any further. Often devolving into traversing directories /as if/ they're looking for something... and they get stuck doing that without end. It all boils down to the fact that LLMs aren't intelligent, so while I have a reasonable foundation for the data collection, the major focus is on creating guardrails, processes and inescapable sequences. These will (ideally) railroad LLMs into doing actual research and processing before they deliver a summary/ report based on the org-mode notes I have. Tags: <a href="https://fed.bajsicki.com/tags/Emacs" rel="nofollow noopener noreferrer" target="_blank">#Emacs</a> <a href="https://fed.bajsicki.com/tags/gptel" rel="nofollow noopener noreferrer" target="_blank">#gptel</a> <a href="https://fed.bajsicki.com/tags/codeberg" rel="nofollow noopener noreferrer" target="_blank">#codeberg</a> <a href="https://fed.bajsicki.com/tags/forgejo" rel="nofollow noopener noreferrer" target="_blank">#forgejo</a> <a href="https://fed.bajsicki.com/tags/orgmode" rel="nofollow noopener noreferrer" target="_blank">#orgmode</a> <a href="https://fed.bajsicki.com/tags/orgql" rel="nofollow noopener noreferrer" target="_blank">#orgql</a> <a href="https://fed.bajsicki.com/tags/llm" rel="nofollow noopener noreferrer" target="_blank">#llm</a> <a href="https://fed.bajsicki.com/tags/informationmanagement" rel="nofollow noopener noreferrer" target="_blank">#informationmanagement</a> <a href="https://fed.bajsicki.com/tags/gptelorgtools" rel="nofollow noopener noreferrer" target="_blank">#gptelorgtools</a> PS. Links should work now, apparently profile visibility affects repo visibility on Codeberg. I would not have expected that. PPS. Deleted and reposted because of strong anti-bridge sentiment on my part. Screw Bluesky and bots that repost to it. Defederated: newsmast.*

Phil<code>gptel-org-tools</code> update. 1. Cloned to <a href="https://codeberg.org/bajsicki/gptel-org-tools" rel="nofollow noopener noreferrer" target="_blank">https://codeberg.org/bajsicki/gptel-org-tools</a>, and all future work will be happening on Codeberg. 2. Added <code>gptel-org-tools-result-limit</code> and a helper function for it. This sets a hard limit on the number of characters a tool can return. If it's over that, the LLM is prompted to be more specific in its query. Not applied to all tools, just the ones that are likely to blow up the context window. 3. Added docstrings for the functions called by the tools, so LLMs can look up their definitions. 4. Improved the precision of some tool descriptions so instructions are easier to follow. 5. Some minor improvements w/r/t function names and calls, logic, etc. Basic QA. Now, as a user: 1. I'm finding it increasingly frustrating that Gemma 3 refuses to follow instructions. So here's a PSA: Gemma 3 doesn't respect the system prompt. It treats it just the same as any other user input. 2. Mistral 24B is a mixed bag. I'm not sure if it's my settings or something else, but it fairly consistently ends up looping; it'll call the same tool over and over again with the exact same arguments. This happens with other models as well, but not nearly as frequently. 3. Qwen 2.5 14B: pretty dang good, I'd say. The Cogito fine-tune is also surprisingly usable. 4. Prompting: I have found that a good, detailed system prompt tends to /somewhat/ improve results, especially if it contains clear directions on where to look for things related to specific topics. I'm still in the middle of writing one that's accurate to my Emacs set-up, but when I do finish it, it'll be in the repository as an example. 5. One issue that I still struggle with is that the LLMs don't take any time to process the user request. Often they'll find some relevant information in one file, and then decide that's enough and just refuse to look any further. Often devolving into traversing directories /as if/ they're looking for something... and they get stuck doing that without end. It all boils down to the fact that LLMs aren't intelligent, so while I have a reasonable foundation for the data collection, the major focus is on creating guardrails, processes and inescapable sequences. These will (ideally) railroad LLMs into doing actual research and processing before they deliver a summary/ report based on the org-mode notes I have. Tags: <a href="https://fed.bajsicki.com/tags/Emacs" rel="nofollow noopener noreferrer" target="_blank">#Emacs</a> <a href="https://fed.bajsicki.com/tags/gptel" rel="nofollow noopener noreferrer" target="_blank">#gptel</a> <a href="https://fed.bajsicki.com/tags/codeberg" rel="nofollow noopener noreferrer" target="_blank">#codeberg</a> <a href="https://fed.bajsicki.com/tags/forgejo" rel="nofollow noopener noreferrer" target="_blank">#forgejo</a> <a href="https://fed.bajsicki.com/tags/orgmode" rel="nofollow noopener noreferrer" target="_blank">#orgmode</a> <a href="https://fed.bajsicki.com/tags/orgql" rel="nofollow noopener noreferrer" target="_blank">#orgql</a> <a href="https://fed.bajsicki.com/tags/llm" rel="nofollow noopener noreferrer" target="_blank">#llm</a> <a href="https://fed.bajsicki.com/tags/ai" rel="nofollow noopener noreferrer" target="_blank">#ai</a> <a href="https://fed.bajsicki.com/tags/informationmanagement" rel="nofollow noopener noreferrer" target="_blank">#informationmanagement</a> <a href="https://fed.bajsicki.com/tags/gptelorgtools" rel="nofollow noopener noreferrer" target="_blank">#gptelorgtools</a>

PhilSo currently I'm hosting <code>gptel-org-tools</code> on my own forge... <a href="https://git.bajsicki.com/phil/gptel-org-tools" rel="nofollow noopener noreferrer" target="_blank">https://git.bajsicki.com/phil/gptel-org-tools</a> I can't seem to find a good way for people to create issues. I thought that creating issues via email was a thing with Forgejo, but it appears not. So here's a poll. Despite my hatred of Microsoft, is it for the best to move the repo to GitHub? Or is there some way to federate with GitHub users so I don't need to open public sign-ups on my git? I'm not exactly clear on what the move is here. <a href="https://fed.bajsicki.com/tags/Emacs" rel="nofollow noopener noreferrer" target="_blank">#Emacs</a> <a href="https://fed.bajsicki.com/tags/gptel" rel="nofollow noopener noreferrer" target="_blank">#gptel</a> <a href="https://fed.bajsicki.com/tags/gitforge" rel="nofollow noopener noreferrer" target="_blank">#gitforge</a> <a href="https://fed.bajsicki.com/tags/forgejo" rel="nofollow noopener noreferrer" target="_blank">#forgejo</a> <a href="https://fed.bajsicki.com/tags/github" rel="nofollow noopener noreferrer" target="_blank">#github</a> <a href="https://fed.bajsicki.com/tags/microsoft" rel="nofollow noopener noreferrer" target="_blank">#microsoft</a> <a href="https://fed.bajsicki.com/tags/foss" rel="nofollow noopener noreferrer" target="_blank">#foss</a>

jerger<a href="https://chaos.social/@yorgos" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@yorgos</a> <a href="https://toot.radicle.xyz/@radicle" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@radicle</a> Why not use <a href="https://social.meissa-gmbh.de/tags/forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#forgejo</a> on <a href="https://codeberg.org" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://codeberg.org</a> ?It is NonProfit & <a href="https://social.meissa-gmbh.de/tags/Federation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Federation</a> is in heavy development ...

Al SuttonThanks to <a href="https://androiddev.social/@botteaap" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@botteaap</a>'s <a href="https://snapp.social/tags/gradle" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gradle</a> version catalogue update plugin, I now have a replacement for <a href="https://snapp.social/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a> <a href="https://snapp.social/tags/Dependatbot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Dependatbot</a>, which means we're on feature parity for our <a href="https://snapp.social/tags/Forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Forgejo</a> instance 🕺 .Thanks Hugo 🤗 <a href="https://github.com/littlerobots/version-catalog-update-plugin" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/littlerobots/version-catalog-update-plugin</a>

meissa-teamIhr seid an <a href="https://social.meissa-gmbh.de/tags/Forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Forgejo</a> und <a href="https://social.meissa-gmbh.de/tags/Federation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Federation</a> interessiert?Dann trefft uns doch in Backnang auf der <a href="https://social.meissa-gmbh.de/tags/FSCK" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FSCK</a> Wir erzählen, was sich im vergangen Jahr alles ergeben hat :-)<a href="https://cfp.ctbk.de/fsck-2025/talk/review/PBCE9EQLHZCKAV7UE8E7XYRJDL3SQVUW" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://cfp.ctbk.de/fsck-2025/talk/review/PBCE9EQLHZCKAV7UE8E7XYRJDL3SQVUW</a>

revolutionary girl erinTo anyone who runs a forgejo instance, small or large: does it feel mature and stable at this point? Is there anything that you feel is essential missing?I need to set some folks up with a self hosted git forge and its basically a choice between gitlab and forgejo.<a href="https://kolektiva.social/tags/git" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#git</a> <a href="https://kolektiva.social/tags/forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#forgejo</a> <a href="https://kolektiva.social/tags/gitlab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitlab</a>

FluchtkapselMaybe people here can help me. Does Forgejo allow serving static pages? And what's the best way to push the result of an Action to a different Forgejo repo?Edit: Set post language to English <a href="https://nerdculture.de/tags/forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#forgejo</a> <a href="https://nerdculture.de/tags/actions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#actions</a>

Kompot.si :unverified:<a href="https://toot.si/tags/kompot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kompot</a> 🐌 <a href="https://toot.si/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosting</a> collective finally made a move to switch over from <a href="https://toot.si/tags/gitea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitea</a> to <a href="https://toot.si/tags/forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#forgejo</a>sysadmins <a href="https://toot.si/@g1smo" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@g1smo</a>, <a href="https://mstdn.social/@testman" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@testman</a> and <a href="https://mastodon.social/@shtumf" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@shtumf</a> described a process as very smooth with a sole problem of a wrong last updated date on all of the projects.We had this planned since the fork, we were following the process closely and stood firmly on forgejo side. We're still a few versions behind the latest. A big server update is planed for May, if we will manage to summon 🔮 up the community 🥁 🔥🏕️

Baa:ai_yaysuperfast: <a href="https://mk.absturztau.be/tags/kubernetes" rel="nofollow noopener noreferrer" target="_blank">#kubernetes</a> <a href="https://mk.absturztau.be/tags/forgejo" rel="nofollow noopener noreferrer" target="_blank">#forgejo</a>

BaaI did it! Auto-registering forgejo runners in kubernetes :ai_yaysuperfast: <a href="https://mk.absturztau.be/tags/kubernetes" rel="nofollow noopener noreferrer" target="_blank">#kubernetes</a> <a href="https://mk.absturztau.be/tags/forgejo" rel="nofollow noopener noreferrer" target="_blank">#forgejo</a>

Alexey SkobkinА ещё, кажется, в Forgejo сделали что-то с федерацией репозиториев. Вижу вот такое.Это что, задел на федерацию пуллреквестов что ли? :philosoraptor:<a href="https://gts.skobk.in/tags/federation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#federation</a> <a href="https://gts.skobk.in/tags/forgefed" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#forgefed</a> <a href="https://gts.skobk.in/tags/fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fediverse</a> <a href="https://gts.skobk.in/tags/forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Forgejo</a> <a href="https://gts.skobk.in/tags/pic" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pic</a>

Alexey SkobkinКстати, если кто вдруг не в курсе, то то ли в последний LTS, то ли в один из предыдущих релизов Forgejo завезли возможность push-зеркалирования через SSH-ключи.И это просто замечательно, учитывая, что зеркализоваться в тот же Github через токены было болью: либо нужно было выписывать вечный легаси токен, который может дофига лишнего, либо выписывать гранулированные токены не реже, чем раз в год и обновлять во всех репозиториях Forgejo/Gitea, что вызывало жопоболь.Теперь можно просто создать конфигурацию зеркалирования в Forgejo, оно создаст SSH-ключ для этого, который можно будет добавить на гитхабе как Deploy-ключ, у которого никакого доступа, кроме записи (и чтения) в репозиторий не будет.🎉<a href="https://gts.skobk.in/tags/forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Forgejo</a> <a href="https://gts.skobk.in/tags/features" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#features</a> <a href="https://gts.skobk.in/tags/good" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#good</a> <a href="https://gts.skobk.in/tags/github" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Github</a> <a href="https://gts.skobk.in/tags/mirroring" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mirroring</a> <a href="https://gts.skobk.in/tags/log" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#log</a>

Hippo 🍉<a href="https://mastodon.social/@kuenefe" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@kuenefe</a> it depends...I've been using the <a href="https://fosstodon.org/tags/Forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Forgejo</a> instance hosted by <a href="https://nixnet.social/users/disroot" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@disroot</a> since I already have an account. For <a href="https://squeet.me/profile/snipette" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@snipette</a> I used to maintain a dedicated Gitea (later Forgejo) instance installed via <a href="https://fosstodon.org/tags/YunoHost" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#YunoHost</a>, because we had a bunch of tools that we wanted to publish 🐶The "go-to" option nowadays is <a href="https://social.anoxinon.de/@Codeberg" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Codeberg</a> (again running Forgejo), which we use for <a href="https://venera.social/profile/prav" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@prav</a> :xmpp:Besides Forgejo, there are a bunch of more minimal options like <a href="https://fosstodon.org/tags/sourcehut" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sourcehut</a> and <a href="https://fosstodon.org/tags/humungus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#humungus</a>

FluchtkapselBecause of my stupid curiosity I always try to achieve what other people do with a different toolset. People use LXC? I use systemd-nspawn. Docker? Nah, podman!And today I setup Forgejo running in a systemd-nspawn container. I setup a second nspawn-container for the Forgejo runner.It went as is to be expected. "Error: cannot ping the docker daemon. […]"Of course I can't find anything regarding my special situation. 🤷 I got it working by overridng the podman.socket with SocketMode=0666 (default is 0660). Doesn't seem to be safe, though. After adding a group podman and adding the runner to this group the forgejo-runner.service also works with SocketGroup=podman.<a href="https://nerdculture.de/tags/nspawn" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nspawn</a> <a href="https://nerdculture.de/tags/forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#forgejo</a> <a href="https://nerdculture.de/tags/podman" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#podman</a>

Hippo 🍉I nowadays get the same uncomfortable feeling when engaging with <a href="https://fosstodon.org/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a> that I used to get when dealing with <a href="https://fosstodon.org/tags/Google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Google</a>. Maybe I'll soon reach the point where seeing someone use GitHub is as much of a culture shock as spotting someone searching with Google is to me today 💥Hopefully all the projects I'm interested in would have moved on by then :forgejo:<a href="https://fosstodon.org/tags/Forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Forgejo</a> <a href="https://fosstodon.org/tags/Git" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Git</a> <a href="https://fosstodon.org/tags/CultureShock" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CultureShock</a> <a href="https://fosstodon.org/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SelfHosting</a> <a href="https://fosstodon.org/tags/Codeberg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Codeberg</a> <a href="https://fosstodon.org/tags/Mercurial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mercurial</a>

Andreu Casablanca 🐀Happy :neocat_bongo_down: , today I deployed a <a href="https://hachyderm.io/tags/Forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Forgejo</a> instance to manage my private code projects. I won't be using <a href="https://hachyderm.io/tags/Github" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Github</a> anymore for my stuff, only to contribute to 3rd party projects.I still have some pending work to configure the CI workers, but I'll leave that for next week.Along the way I've learnt some stuff about <a href="https://hachyderm.io/tags/OpenTofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenTofu</a> and networking. Enough to know that I still prefer to be on the dev side of the "devops" :neocat_googly_shocked: .

FrançoisOh very neat, Forgejo 11 supports providing SSH public key via OpenID Connect authentication as well! Now just need to implement this in my OP. Is there a standardized claim name/scope for this?<a href="https://floss.social/tags/forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#forgejo</a> <a href="https://floss.social/tags/openid" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openid</a> <a href="https://floss.social/tags/oidc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#oidc</a> <a href="https://floss.social/tags/ssh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ssh</a>

DIGITAL PRIVACY .DIYAs an RSS user, you like such simple things:<a href="https://floss.social/@forgejo" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@forgejo</a> / <a href="https://social.anoxinon.de/@Codeberg" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Codeberg</a> Thanks<a href="https://fosstodon.org/tags/forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#forgejo</a> <a href="https://fosstodon.org/tags/rss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rss</a> <a href="https://fosstodon.org/tags/codeberg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#codeberg</a> <a href="https://fosstodon.org/tags/git" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#git</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

ForgeJoZurück

#forgejo