I use SANE for scanning.

• install sane-utils
• configure /etc/sane.d/saned.conf, list the IP adresses or network allowed to connect
• start saned.socket

on your client (linux desktop)

• add the SANE server IP to to the config echo "192.168.xx.xx" > /etc/sane.d/net.conf
• list the scanners scanimage -L

The scanner is also automatically listed in scanning utilities like simple-scan etc. Don’t know about phones or other devices, I assume there are scanner auto-discovery utilities; phones also have cameras so thy can scan on their own. I don’t know about Web UIs, why not just use native printing/scanning features of guest devices?

https://github.com/nodiscc/toolbox/blob/master/SCRIPTS/llamacpp-summarize

FUD

Gitea is still MIT licensed and the Enterprise tier features only cater to large org needs [1]. Why would I want to deal with nightmarish SAML config when OIDC does a better job

Forgejo was forked because the maintainers were butthurt they didn’t have more say in the development roadmap and their large PRs didn’t get reviewed and merged fast enough. Which is a valid reason to fork

I wish more people understood this.

Do I use LLMs to write software for my personal use? Sure. I still try to build it in an “incremental” way the same way I would write software manually so I don’t get 10k SLOC written in a week, but at some point, even reviewing 100 LOC changes takes time, so I just take a cursory look at the diff, yolo-merge-and-run to test it. It’s not critical. This is fine. I’m just exploring the problem domain and solutions.

But would I go as far as sharing it, making a damn git repo and advertising it on Lemmy? Fuck no. This is unreliable, inscrutable slopware tailored for my own use. Anyone with a local LLM or a 20 euro claude/codex/z.ai subscription can do the same thing in a few minutes of work a day.

A single 10-line patch/contribution to a human-written project, with contributors who understand the code, or even a well-curated comment in a bug tracker that helps devs debug an issue or clearly expresses a need, has more value for the community than 50 vibe-coded projects.

I didn’t find one that would work entirely authelssly and which would allow negative entries

Have you considered filing feature requests for these on existing, well-maintained projects?

Yes, even writing a proper issue report probably entails more work and brainstorming than prompting your way to a shitty solution. No offense meant, I do it as well. I know using a LLM and pumping out a working solution to a complex problem in a week gives a feeling of euphoria and power; this wouldn’t have been possible at all a few years ago. But there is absolutely no value in proactively sharing and advertising it.

I appreciate OP being transparent about it though.

Yep. https://lemmy.world/post/46066942/23416719 Basic setup, works for me

they don’t go out of their way to make the self hosted option easy

Just follow the docs https://docs.nextcloud.com/server/stable/admin_manual/installation/source_installation.html ? The manual install is a simple webserver + PHP-FPM + postgres setup

I have automated it with an ansible role [1], there’s nothing complicated about it, really.

That’s only if you use the default Build agent with the built-in prompt (https://github.com/anomalyco/opencode/blob/dev/packages/opencode/src/session/prompt/default.txt), and yes it is quite large.

It’s trivial to create custom agents in opencode.json with custom prompts, tools, whatever…

For example I have created a Personal agent which handles menial stuff such as searching/editing my notes, appointments, tasks… with a restricted set of tools and skills.

The single most important change I made is only allowing the local provider in the config, which disables all cloud providers. IMHO this should be the default but I’m not complaining. It’s the best open-source harness I’ve tried so far. I want to try pi.dev someday (quite minimal, needs a good amount of setup and tuning).

I also argue that some local models actually behave much better with a semi-large system prompt (qwen 3.6 for example tends to lose itself in reasoning if you only use the default You are a helpful assistant system prompt and a basic Say hi user prompt - opencode-like large system prompts fixes this; even if you lose some time for initial prompt loading)

Podman pods (or quadlets) managed by ansible.

True.

But by default the unattended-upgrades timer has a randomized trigger time (so that not all Debian machines in the world start hammering the mirrors at the same time). If you enable the auto reboot option in unattended-upgrades, your boxes will reboot at an unpredictable time. I prefer doing this at known times (middle of the night when I know nothing important is running/number of users is low).

This is a kernel bug, unattended-upgrades will take care of installing the new kernel once the fix is published, but you still have to reboot to load it. I’ve set up a cron job that runs needrestart nightly and reboots my servers if there is a pending kernel upgrade [1]

Damn their website has become a mess. Anyway

• https://get.kiwix.org/en/solutions/applications/download-options/
• https://packages.debian.org/trixie/kiwix

Yes. This is my ansible role that deploys it

This is fine as long as upstream supports a convenient way to get the latest versions of software for which you actually need latest (APT repositories)

Stable base, only explicitly allow selected unstable/bleeding edge components.

This is what I do for ROCm and a few other things which need to be constantly updated (yt-dlp). Sometimes stable-backports repositories are enough, but not always.

I suggest using llama.cpp instead of ollama, you can easily squeeze +10% in inference speed and other memory optimizations from llama.cpp. With hardware prices nowadays I think every % saved on resources matters. Here is a simple ansible role to setup llama.cpp, it should give you a good idea of how to deploy it.

A dedicated inference rig is not gonna be cheap. What I did, since I need a gaming rig; is getting 32GB DDR5 (this was before the current RAMpocalypse, if I had known I would have bought 64) and an AMD 9070 (16GB VRAM - again if I had known how crazy prices would get I’d probably ahve bought a 24GB VRAM card). The home server runs the usual/non-AI stuff, and llamacpp runs on the gaming desktop (the home server just has a proxy to it). Yeah the gaming desktop has to be powered up when I want to run inference, this is my main desktop so it’s powered on most of the time, no big deal

There is https://www.infomaniak.com/en/euria (Switzerland)

And https://mammouth.ai/ (France), though they’re more a “middleman” for various providers (including providers serving open-weights models)

And of course you can still run models locally with LLM hosts like https://github.com/ggml-org/llama.cpp (there are hundreds of derivatives, but llama.cpp is the OG/underlying library for most of them). A decent gaming PC can now run local LLMs on par with SOTA proprietary models from 6-12 months ago (qwen3.6 is a beast). https://old.reddit.com/r/LocalLLaMA/ is a decent subreddit for news and discussions about this, I didn’t find a real equivalent on lemmy.

Email

Most applications/services offer mail as notification channel. Even old school unix utilities such as cron support sending mail (through the system MTA). I use msmtp. Then configure K-9 mail or any decent mail client on your phone, setup filters so that mail from your services ends up in a high priority folder in your mailbox with notifications enabled.

I want to be able to receive notifications both on mobile and desktop, this is the only reasonable option I found and have been running with it for > 10 years.

• use APT repositories when possible -> then unattended-upgrades
• For OCI images that do not provide tagged releases (looking at you searxng…), podman auto-update
• for everything else, subscribe to releases RSS feed, read release notes when they come out, check for breaking changes and possibly interesting stuff, update version in ansible playbook, deploy ansible playbook

It can protect APIs as much as any other URL. Or more simply you could disallow any unauthenticated API access in gitea or at the reverse proxy level?

cannot protect against bot traffic coming from many different residential proxies

It can block anything that doesn’t pass the proof-of-work/JS challenge. Most bots don’t interpret JS.

The scraping/bandwidth abuse problem can easily be worked around.

But there still are actual good reasons to not host a public forge.

For example, as long as pull requests are allowed (which is required for actual contributors), anyone can abuse the PR feature to fork your repository, then start pushing random shit into their fork (since the fork is an actual separate git repository).

Bad actors can do it on github all they want, it’s not my storage, not my server used to host potentially illegal content.

Self-hosting public services where you are the only authenticated user and sole publisher of content is easy (using your public forge as a mirror with account creation disabled is fine), hosting other’s people content is another can of worms. Think twice before you do that.

The blurb is my own submission, since it was not so evident how the article was related to self-hosting. I am not the author of the blog post. I am a maintainer of awesome-selfhosted.