#Docker
Raphaël.
@[email protected] · Reply to nixCraft 🐧's post
How many projects or CI stacks, critical or not, in production or not, rely on some Dockerfile starting with "FROM alpine:xxx" ?
https://alpinelinux.org/posts/Seeking-Support-After-Equinix-Metal-Sunsets.html
#alpinelinux #docker #CI #dev #webdev #saas #programming #devops
Ariel
Raphaël.
@[email protected] · Reply to nixCraft 🐧's post
How many projects or CI stacks, critical or not, in production or not, rely on some Dockerfile starting with "FROM alpine:xxx" ?
https://alpinelinux.org/posts/Seeking-Support-After-Equinix-Metal-Sunsets.html
#alpinelinux #docker #CI #dev #webdev #saas #programming #devops
Qiita - 人気の記事
Quokka 🇦🇺
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.
Riccardo Pasquini
Kushal Das :python: :tor: 🇵🇸
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 @[email protected]
Mauricio Teixeira 🇧🇷🇺🇲
@[email protected] · Reply to Mauricio Teixeira 🇧🇷🇺🇲's post
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.
Chris Brooking
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 ?
AdrianC
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
AdrianC
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
DevOps Weekly
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
Hollo
@[email protected] · Reply to Hollo :hollo:'s post
#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
이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다.
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Fedify: an ActivityPub server framework
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉
Here's what moved:
- @dahlia/fedify → @fedify-dev/fedify
- @dahlia/botkit → @fedify-dev/botkit
- @dahlia/hollo → @fedify-dev/hollo
- @dahlia/fedify-amqp → @fedify-dev/amqp
- @dahlia/fedify-h3 → @fedify-dev/h3
- @dahlia/fedify-express → @fedify-dev/express
- @dahlia/fedify-postgres → @fedify-dev/postgres
- @dahlia/fedify-redis → @fedify-dev/redis
- @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
- @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
- @dahlia/fedichatbot → @fedify-dev/fedichatbot
- @dahlia/microblog → @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!
New GitHub organization: https://github.com/fedify-dev.
洪 民憙 (Hong Minhee)
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
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!
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Hollo
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!
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Fedify: an ActivityPub server framework
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉
Here's what moved:
- @dahlia/fedify → @fedify-dev/fedify
- @dahlia/botkit → @fedify-dev/botkit
- @dahlia/hollo → @fedify-dev/hollo
- @dahlia/fedify-amqp → @fedify-dev/amqp
- @dahlia/fedify-h3 → @fedify-dev/h3
- @dahlia/fedify-express → @fedify-dev/express
- @dahlia/fedify-postgres → @fedify-dev/postgres
- @dahlia/fedify-redis → @fedify-dev/redis
- @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
- @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
- @dahlia/fedichatbot → @fedify-dev/fedichatbot
- @dahlia/microblog → @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!
New GitHub organization: https://github.com/fedify-dev.
Hollo
@[email protected] · Reply to Hollo :hollo:'s post
#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
이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다.
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Fedify: an ActivityPub server framework
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉
Here's what moved:
- @dahlia/fedify → @fedify-dev/fedify
- @dahlia/botkit → @fedify-dev/botkit
- @dahlia/hollo → @fedify-dev/hollo
- @dahlia/fedify-amqp → @fedify-dev/amqp
- @dahlia/fedify-h3 → @fedify-dev/h3
- @dahlia/fedify-express → @fedify-dev/express
- @dahlia/fedify-postgres → @fedify-dev/postgres
- @dahlia/fedify-redis → @fedify-dev/redis
- @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
- @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
- @dahlia/fedichatbot → @fedify-dev/fedichatbot
- @dahlia/microblog → @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!
New GitHub organization: https://github.com/fedify-dev.
Hollo
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!
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Fedify: an ActivityPub server framework
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉
Here's what moved:
- @dahlia/fedify → @fedify-dev/fedify
- @dahlia/botkit → @fedify-dev/botkit
- @dahlia/hollo → @fedify-dev/hollo
- @dahlia/fedify-amqp → @fedify-dev/amqp
- @dahlia/fedify-h3 → @fedify-dev/h3
- @dahlia/fedify-express → @fedify-dev/express
- @dahlia/fedify-postgres → @fedify-dev/postgres
- @dahlia/fedify-redis → @fedify-dev/redis
- @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
- @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
- @dahlia/fedichatbot → @fedify-dev/fedichatbot
- @dahlia/microblog → @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!
New GitHub organization: https://github.com/fedify-dev.
Hollo
@[email protected] · Reply to Hollo :hollo:'s post
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 #フェディバース #Docker #ドッカー
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Fedify: an ActivityPub server framework
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉
Here's what moved:
- @dahlia/fedify → @fedify-dev/fedify
- @dahlia/botkit → @fedify-dev/botkit
- @dahlia/hollo → @fedify-dev/hollo
- @dahlia/fedify-amqp → @fedify-dev/amqp
- @dahlia/fedify-h3 → @fedify-dev/h3
- @dahlia/fedify-express → @fedify-dev/express
- @dahlia/fedify-postgres → @fedify-dev/postgres
- @dahlia/fedify-redis → @fedify-dev/redis
- @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
- @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
- @dahlia/fedichatbot → @fedify-dev/fedichatbot
- @dahlia/microblog → @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!
New GitHub organization: https://github.com/fedify-dev.
Hollo
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!
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Fedify: an ActivityPub server framework
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉
Here's what moved:
- @dahlia/fedify → @fedify-dev/fedify
- @dahlia/botkit → @fedify-dev/botkit
- @dahlia/hollo → @fedify-dev/hollo
- @dahlia/fedify-amqp → @fedify-dev/amqp
- @dahlia/fedify-h3 → @fedify-dev/h3
- @dahlia/fedify-express → @fedify-dev/express
- @dahlia/fedify-postgres → @fedify-dev/postgres
- @dahlia/fedify-redis → @fedify-dev/redis
- @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
- @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
- @dahlia/fedichatbot → @fedify-dev/fedichatbot
- @dahlia/microblog → @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!
New GitHub organization: https://github.com/fedify-dev.
洪 民憙 (Hong Minhee)
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
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!
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Hollo
@[email protected] · Reply to Hollo :hollo:'s post
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 #フェディバース #Docker #ドッカー
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Fedify: an ActivityPub server framework
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉
Here's what moved:
- @dahlia/fedify → @fedify-dev/fedify
- @dahlia/botkit → @fedify-dev/botkit
- @dahlia/hollo → @fedify-dev/hollo
- @dahlia/fedify-amqp → @fedify-dev/amqp
- @dahlia/fedify-h3 → @fedify-dev/h3
- @dahlia/fedify-express → @fedify-dev/express
- @dahlia/fedify-postgres → @fedify-dev/postgres
- @dahlia/fedify-redis → @fedify-dev/redis
- @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
- @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
- @dahlia/fedichatbot → @fedify-dev/fedichatbot
- @dahlia/microblog → @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!
New GitHub organization: https://github.com/fedify-dev.
Hollo
@[email protected] · Reply to Hollo :hollo:'s post
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 #フェディバース #Docker #ドッカー
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Fedify: an ActivityPub server framework
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉
Here's what moved:
- @dahlia/fedify → @fedify-dev/fedify
- @dahlia/botkit → @fedify-dev/botkit
- @dahlia/hollo → @fedify-dev/hollo
- @dahlia/fedify-amqp → @fedify-dev/amqp
- @dahlia/fedify-h3 → @fedify-dev/h3
- @dahlia/fedify-express → @fedify-dev/express
- @dahlia/fedify-postgres → @fedify-dev/postgres
- @dahlia/fedify-redis → @fedify-dev/redis
- @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
- @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
- @dahlia/fedichatbot → @fedify-dev/fedichatbot
- @dahlia/microblog → @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!
New GitHub organization: https://github.com/fedify-dev.
Hollo
@[email protected] · Reply to Hollo :hollo:'s post
#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
이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다.
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Fedify: an ActivityPub server framework
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉
Here's what moved:
- @dahlia/fedify → @fedify-dev/fedify
- @dahlia/botkit → @fedify-dev/botkit
- @dahlia/hollo → @fedify-dev/hollo
- @dahlia/fedify-amqp → @fedify-dev/amqp
- @dahlia/fedify-h3 → @fedify-dev/h3
- @dahlia/fedify-express → @fedify-dev/express
- @dahlia/fedify-postgres → @fedify-dev/postgres
- @dahlia/fedify-redis → @fedify-dev/redis
- @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
- @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
- @dahlia/fedichatbot → @fedify-dev/fedichatbot
- @dahlia/microblog → @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!
New GitHub organization: https://github.com/fedify-dev.
Hollo
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!
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Fedify: an ActivityPub server framework
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉
Here's what moved:
- @dahlia/fedify → @fedify-dev/fedify
- @dahlia/botkit → @fedify-dev/botkit
- @dahlia/hollo → @fedify-dev/hollo
- @dahlia/fedify-amqp → @fedify-dev/amqp
- @dahlia/fedify-h3 → @fedify-dev/h3
- @dahlia/fedify-express → @fedify-dev/express
- @dahlia/fedify-postgres → @fedify-dev/postgres
- @dahlia/fedify-redis → @fedify-dev/redis
- @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
- @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
- @dahlia/fedichatbot → @fedify-dev/fedichatbot
- @dahlia/microblog → @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!
New GitHub organization: https://github.com/fedify-dev.
Hollo
@[email protected] · Reply to Hollo :hollo:'s post
#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
이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다.
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Fedify: an ActivityPub server framework
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉
Here's what moved:
- @dahlia/fedify → @fedify-dev/fedify
- @dahlia/botkit → @fedify-dev/botkit
- @dahlia/hollo → @fedify-dev/hollo
- @dahlia/fedify-amqp → @fedify-dev/amqp
- @dahlia/fedify-h3 → @fedify-dev/h3
- @dahlia/fedify-express → @fedify-dev/express
- @dahlia/fedify-postgres → @fedify-dev/postgres
- @dahlia/fedify-redis → @fedify-dev/redis
- @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
- @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
- @dahlia/fedichatbot → @fedify-dev/fedichatbot
- @dahlia/microblog → @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!
New GitHub organization: https://github.com/fedify-dev.
Hollo
@[email protected] · Reply to Hollo :hollo:'s post
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 #フェディバース #Docker #ドッカー
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Fedify: an ActivityPub server framework
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉
Here's what moved:
- @dahlia/fedify → @fedify-dev/fedify
- @dahlia/botkit → @fedify-dev/botkit
- @dahlia/hollo → @fedify-dev/hollo
- @dahlia/fedify-amqp → @fedify-dev/amqp
- @dahlia/fedify-h3 → @fedify-dev/h3
- @dahlia/fedify-express → @fedify-dev/express
- @dahlia/fedify-postgres → @fedify-dev/postgres
- @dahlia/fedify-redis → @fedify-dev/redis
- @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
- @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
- @dahlia/fedichatbot → @fedify-dev/fedichatbot
- @dahlia/microblog → @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!
New GitHub organization: https://github.com/fedify-dev.
洪 民憙 (Hong Minhee)
@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post
#Hollo 關聯 重要 消息을 共有합니다. 貯藏所가 새로운 곳으로 移徙했어요! #Docker 이미지로 使用中이신 분들은 確認 付託드립니다:
https://hollo.social/@hollo/0194aa7b-017e-74e7-b97a-f91bb6c7b8e6
Hollo
@[email protected] · Reply to Hollo :hollo:'s post
#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
이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다.
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Hollo
@[email protected] · Reply to Hollo :hollo:'s post
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 #フェディバース #Docker #ドッカー
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Fedify: an ActivityPub server framework
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉
Here's what moved:
- @dahlia/fedify → @fedify-dev/fedify
- @dahlia/botkit → @fedify-dev/botkit
- @dahlia/hollo → @fedify-dev/hollo
- @dahlia/fedify-amqp → @fedify-dev/amqp
- @dahlia/fedify-h3 → @fedify-dev/h3
- @dahlia/fedify-express → @fedify-dev/express
- @dahlia/fedify-postgres → @fedify-dev/postgres
- @dahlia/fedify-redis → @fedify-dev/redis
- @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
- @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
- @dahlia/fedichatbot → @fedify-dev/fedichatbot
- @dahlia/microblog → @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!
New GitHub organization: https://github.com/fedify-dev.
洪 民憙 (Hong Minhee)
@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post
#Hollo 關聯 重要 消息을 共有합니다. 貯藏所가 새로운 곳으로 移徙했어요! #Docker 이미지로 使用中이신 분들은 確認 付託드립니다:
https://hollo.social/@hollo/0194aa7b-017e-74e7-b97a-f91bb6c7b8e6
Hollo
@[email protected] · Reply to Hollo :hollo:'s post
#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
이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다.
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Hollo
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!
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Fedify: an ActivityPub server framework
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉
Here's what moved:
- @dahlia/fedify → @fedify-dev/fedify
- @dahlia/botkit → @fedify-dev/botkit
- @dahlia/hollo → @fedify-dev/hollo
- @dahlia/fedify-amqp → @fedify-dev/amqp
- @dahlia/fedify-h3 → @fedify-dev/h3
- @dahlia/fedify-express → @fedify-dev/express
- @dahlia/fedify-postgres → @fedify-dev/postgres
- @dahlia/fedify-redis → @fedify-dev/redis
- @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
- @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
- @dahlia/fedichatbot → @fedify-dev/fedichatbot
- @dahlia/microblog → @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!
New GitHub organization: https://github.com/fedify-dev.
Hollo
@[email protected] · Reply to Hollo :hollo:'s post
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 #フェディバース #Docker #ドッカー
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Fedify: an ActivityPub server framework
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉
Here's what moved:
- @dahlia/fedify → @fedify-dev/fedify
- @dahlia/botkit → @fedify-dev/botkit
- @dahlia/hollo → @fedify-dev/hollo
- @dahlia/fedify-amqp → @fedify-dev/amqp
- @dahlia/fedify-h3 → @fedify-dev/h3
- @dahlia/fedify-express → @fedify-dev/express
- @dahlia/fedify-postgres → @fedify-dev/postgres
- @dahlia/fedify-redis → @fedify-dev/redis
- @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
- @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
- @dahlia/fedichatbot → @fedify-dev/fedichatbot
- @dahlia/microblog → @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!
New GitHub organization: https://github.com/fedify-dev.
Hollo
@[email protected] · Reply to Hollo :hollo:'s post
#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
이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다.
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Fedify: an ActivityPub server framework
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉
Here's what moved:
- @dahlia/fedify → @fedify-dev/fedify
- @dahlia/botkit → @fedify-dev/botkit
- @dahlia/hollo → @fedify-dev/hollo
- @dahlia/fedify-amqp → @fedify-dev/amqp
- @dahlia/fedify-h3 → @fedify-dev/h3
- @dahlia/fedify-express → @fedify-dev/express
- @dahlia/fedify-postgres → @fedify-dev/postgres
- @dahlia/fedify-redis → @fedify-dev/redis
- @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
- @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
- @dahlia/fedichatbot → @fedify-dev/fedichatbot
- @dahlia/microblog → @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!
New GitHub organization: https://github.com/fedify-dev.
洪 民憙 (Hong Minhee)
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
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!
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Hollo
@[email protected] · Reply to Hollo :hollo:'s post
#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
이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다.
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Fedify: an ActivityPub server framework
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉
Here's what moved:
- @dahlia/fedify → @fedify-dev/fedify
- @dahlia/botkit → @fedify-dev/botkit
- @dahlia/hollo → @fedify-dev/hollo
- @dahlia/fedify-amqp → @fedify-dev/amqp
- @dahlia/fedify-h3 → @fedify-dev/h3
- @dahlia/fedify-express → @fedify-dev/express
- @dahlia/fedify-postgres → @fedify-dev/postgres
- @dahlia/fedify-redis → @fedify-dev/redis
- @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
- @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
- @dahlia/fedichatbot → @fedify-dev/fedichatbot
- @dahlia/microblog → @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!
New GitHub organization: https://github.com/fedify-dev.
洪 民憙 (Hong Minhee)
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
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!
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Hollo
@[email protected] · Reply to Hollo :hollo:'s post
#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
이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다.
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Fedify: an ActivityPub server framework
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉
Here's what moved:
- @dahlia/fedify → @fedify-dev/fedify
- @dahlia/botkit → @fedify-dev/botkit
- @dahlia/hollo → @fedify-dev/hollo
- @dahlia/fedify-amqp → @fedify-dev/amqp
- @dahlia/fedify-h3 → @fedify-dev/h3
- @dahlia/fedify-express → @fedify-dev/express
- @dahlia/fedify-postgres → @fedify-dev/postgres
- @dahlia/fedify-redis → @fedify-dev/redis
- @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
- @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
- @dahlia/fedichatbot → @fedify-dev/fedichatbot
- @dahlia/microblog → @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!
New GitHub organization: https://github.com/fedify-dev.
Hollo
@[email protected] · Reply to Hollo :hollo:'s post
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 #フェディバース #Docker #ドッカー
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Fedify: an ActivityPub server framework
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉
Here's what moved:
- @dahlia/fedify → @fedify-dev/fedify
- @dahlia/botkit → @fedify-dev/botkit
- @dahlia/hollo → @fedify-dev/hollo
- @dahlia/fedify-amqp → @fedify-dev/amqp
- @dahlia/fedify-h3 → @fedify-dev/h3
- @dahlia/fedify-express → @fedify-dev/express
- @dahlia/fedify-postgres → @fedify-dev/postgres
- @dahlia/fedify-redis → @fedify-dev/redis
- @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
- @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
- @dahlia/fedichatbot → @fedify-dev/fedichatbot
- @dahlia/microblog → @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!
New GitHub organization: https://github.com/fedify-dev.
Hollo
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!
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Fedify: an ActivityPub server framework
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉
Here's what moved:
- @dahlia/fedify → @fedify-dev/fedify
- @dahlia/botkit → @fedify-dev/botkit
- @dahlia/hollo → @fedify-dev/hollo
- @dahlia/fedify-amqp → @fedify-dev/amqp
- @dahlia/fedify-h3 → @fedify-dev/h3
- @dahlia/fedify-express → @fedify-dev/express
- @dahlia/fedify-postgres → @fedify-dev/postgres
- @dahlia/fedify-redis → @fedify-dev/redis
- @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
- @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
- @dahlia/fedichatbot → @fedify-dev/fedichatbot
- @dahlia/microblog → @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!
New GitHub organization: https://github.com/fedify-dev.
Hollo
@[email protected] · Reply to Hollo :hollo:'s post
#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
이번 이전은 프로젝트의 더 나은 운영과 지속적인 개발을 위해 진행되었습니다. 원활한 전환에 협조해 주셔서 감사합니다.
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Fedify: an ActivityPub server framework
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉
Here's what moved:
- @dahlia/fedify → @fedify-dev/fedify
- @dahlia/botkit → @fedify-dev/botkit
- @dahlia/hollo → @fedify-dev/hollo
- @dahlia/fedify-amqp → @fedify-dev/amqp
- @dahlia/fedify-h3 → @fedify-dev/h3
- @dahlia/fedify-express → @fedify-dev/express
- @dahlia/fedify-postgres → @fedify-dev/postgres
- @dahlia/fedify-redis → @fedify-dev/redis
- @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
- @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
- @dahlia/fedichatbot → @fedify-dev/fedichatbot
- @dahlia/microblog → @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!
New GitHub organization: https://github.com/fedify-dev.
Hollo
@[email protected] · Reply to Hollo :hollo:'s post
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 #フェディバース #Docker #ドッカー
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Fedify: an ActivityPub server framework
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉
Here's what moved:
- @dahlia/fedify → @fedify-dev/fedify
- @dahlia/botkit → @fedify-dev/botkit
- @dahlia/hollo → @fedify-dev/hollo
- @dahlia/fedify-amqp → @fedify-dev/amqp
- @dahlia/fedify-h3 → @fedify-dev/h3
- @dahlia/fedify-express → @fedify-dev/express
- @dahlia/fedify-postgres → @fedify-dev/postgres
- @dahlia/fedify-redis → @fedify-dev/redis
- @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
- @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
- @dahlia/fedichatbot → @fedify-dev/fedichatbot
- @dahlia/microblog → @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!
New GitHub organization: https://github.com/fedify-dev.
Hollo
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!
https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14
Fedify: an ActivityPub server framework
@[email protected] · Reply to Fedify: an ActivityPub server framework's post
We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉
Here's what moved:
- @dahlia/fedify → @fedify-dev/fedify
- @dahlia/botkit → @fedify-dev/botkit
- @dahlia/hollo → @fedify-dev/hollo
- @dahlia/fedify-amqp → @fedify-dev/amqp
- @dahlia/fedify-h3 → @fedify-dev/h3
- @dahlia/fedify-express → @fedify-dev/express
- @dahlia/fedify-postgres → @fedify-dev/postgres
- @dahlia/fedify-redis → @fedify-dev/redis
- @dahlia/markdown-it-hashtag → @fedify-dev/markdown-it-hashtag
- @dahlia/markdown-it-mention → @fedify-dev/markdown-it-mention
- @dahlia/fedichatbot → @fedify-dev/fedichatbot
- @dahlia/microblog → @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!
New GitHub organization: https://github.com/fedify-dev.
Qiita - 人気の記事
【🪙中級者向け】改めてDockerを深ぼる① ~ 仮想化の歴史について ~
https://qiita.com/ikemura-ren/items/b24d9eb497acfa48486a?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
pandoc
Use locally installed fonts in the LaTeX Docker container by mounting your fonts directory to /usr/local/share/fonts, e.g.
docker --volume=/usr/share/fonts:/usr/local/share/fonts pandoc/latex …
Should work with XeLaTeX and LuaLaTeX PDF engines as well as with the "typst" container.
joschi
🚀 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.
Qiita - 人気の記事
[rails] tailwindインストール時にexit code 127が出た時の対処法 [tailwind]
https://qiita.com/YamzknA/items/53478370761f716b068f?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
Attractive Nuisance
@[email protected] · Reply to Attractive Nuisance's post
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.
Marc Trius
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/
Marc Trius
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/
AliveDevil
Naming convention for #Podman --env-file?
Do you use .service.env, or .env.service.
Option | Voters |
---|---|
.env.service | 2 (50%) |
.service.env | 2 (50%) |
AliveDevil
Naming convention for #Podman --env-file?
Do you use .service.env, or .env.service.
Option | Voters |
---|---|
.env.service | 2 (50%) |
.service.env | 2 (50%) |
Marc Trius
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/
pandoc
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
Attractive Nuisance
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.
Qiita - 人気の記事
Qiita - 人気の記事
MacのDocker Desktopがマルウェアで開かない対応方法
https://qiita.com/topi_log/items/b65ea476e9da2d7a6155?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
Codeberg.org
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.
Sascha Wübbena
Qiita - 人気の記事
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 - 人気の記事
Qiita - 人気の記事
Sascha Wübbena
@[email protected] · Reply to Sascha Wübbena :mastodon:'s post
Sascha Wübbena
@[email protected] · Reply to Sascha Wübbena :mastodon:'s post
Sascha Wübbena
Ich sehe gerade, dass es bei #Docker auch #TeslaMate gibt. Jetzt, wo ich meinen Account bei #Tronity gelöscht habe, könnte das eine sehr nette Alternative sein.
Hat jemand mit TeslaMate Erfahrungen? Funktioniert das?
hobbsc
hobbsc
Qiita - 人気の記事
Qiita - 人気の記事
Docker Desktop for Macがエラーで起動できない件(#7527)についての情報
https://qiita.com/zembutsu/items/00e147cc1b97d89aaab6?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
Qiita - 人気の記事
Docker Desktopがマルウェア扱いされてしまった時の対処
https://qiita.com/rena_n/items/f77a40bfd91872b68153?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
ale
Crear la imagen oficial de #docker de #nginx con el módulo #testcookie 🍪
https://blog.manalejandro.com/~/Art%C3%ADculos/Crear%20la%20imagen%20oficial%20de%20docker%20de%20nginx%20con%20el%20m%C3%B3dulo%20testcookie
Ariel
The joke... it just wrote itself
#DevOps #PlatformEngineering #Docker #Containers #OCI #Cloud #Podman
Qiita - 人気の記事
改めてDockerを理解する⑥[Dockerのネットワークについて]
https://qiita.com/ikemura-ren/items/0e6071f26a847366e585?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
Kazuky Akayashi ฅ^•ﻌ•^ฅ
Ça va trop loin la, foutre du docker pour un thème ...
#Docker
段風桜 Dampuzakura(わかいい)
個人的・仲間内でセルフホストしているサービス 2022 - Google Workspaceから離脱するための検討ログ (2) - #Docker - Qiita
https://qiita.com/jqtype/items/ca576967ffa1a25e6e4a
개복치 🌺🎗️
WSL 2 - docker 컨테이너에서 GUI 앱을 실행하여 Windows에서 표시
Andrew Lock
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
PR ☮ ♥ ♬ 🧑💻
"If #WASM + #WASI existed in 2008, we wouldn't have needed to create #Docker. That's how important it is. #WebAssembly on the server is the future of computing." — Solomon Hykes
#Manning / #books / #software / #technology <https://manning.com/books/server-side-webassembly?trk_msg=FDRHHVMGQS84ND9TE0J9TOI5LS&trk_contact=BPSP1BEUS2OH7DKUHDUSI721NG&trk_sid=47B5DN0BGE66P09999EC5ACG40&trk_link=MF42PIS2BJK4N01BGQDFFBUOM4>
Adam ♿
Nah, I'll stick with #docker compose
Josep Monjo
Switching from Portainer to Dockge
https://monjo.eu/switching-from-portainer-to-dockge/ #docker #portainer #dockge #devops #linux
Philip Bernhart
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?
Kyle Taylor
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/
Ariel
Nifty new Docker build features
joschi
Happy **Container Base Image Update Day** to those who celebrate! 🎆
Andy Todd
Josep Monjo
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
Esurio
[ Kubernetes をローカルで試してみる #Docker - Qiita ]
https://qiita.com/coitate/items/cca2105e00ea5cae7dcc
Valentin B.
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.
Stefano Marinelli
This morning, a colleague noticed an issue with a Docker-based workload. I stepped in and checked—an upgrade hadn't migrated the database schema, and everything was failing. I manually ran the command in the container and resolved the issue.
The colleague couldn't understand what had happened. He asked me to explain, so I showed him the procedure.
Like many others, he was fascinated by how easily a "docker compose up -d" can set up a service, but this unfortunately hides complexities that, without adequate knowledge of what's underneath, can make the setup extremely fragile.
These tools are powerful, but we shouldn't make the mistake of thinking that understanding the underlying tools is no longer necessary.
noim
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.
Ariel
Anyone know the health/readiness endpoint for Docker daemon on TCP/HTTP?
I'm having pains with it not being up remotely and need something that'll wait until it's ready.
joschi
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
Pedro Piñera
Carlos D. Álvaro
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
Daniël Franke
Am I the only one who doesn't really like configuring services with environment variables?
Alex Popescu
Backup your postgres database to Hetzner S3 Object Storage: https://blog.popescul.com/posts/2024-10-12-backup-postgresql-with-docker/ #postgresql #hetzner #docker
Victor García 👨🏻💻😸🎃
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.
Brianna Townsend
Someone recently told me that it's a constant losing war of attrition to try to host your own mail server because you'll never have reliable delivery.
I'm not paying for anything and I want to use my domain for my email and it feels dumb to have that be the thing I have to pay for.
Was going to just spin up Docker Mailserver
I'd be using it for professional communications, admin for other hosted services, and sending newsletters.
Curious to hear first-hand experiences!
Stefan :veritrek:
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 🎉
Ariel
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!
Ariel
Huh, now that I think about it why *doesn't* Dockerfile have build-time assertion tests...
Ariel
Dockerfiles tried to warn us - it says RUN FROM *right there*
AmyFou 🥥🌴
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 👋
Mo :ferris: :tux:
#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
DevOps Weekly
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
:mastodon: Ric Harvey 🇪🇺🌍💚
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
noim
@[email protected] · Reply to noim's post
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
noim
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?
Chad :vbike:
Self-hosting Mastodon server owners, did you install from source or docker?
Ariel
Somebody was interested in Docker Compose and container tips so I've posted mine
https://www.richtman.au/blog/gitlab-docker-compose-tips-n-tricks/
#Containers #Docker #DockerCompose #DevOps #PlatformEngineering #GitLab #GitLabCI #CICD
Floppy 💾
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.
n00q
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?
Hossain Khan
@[email protected] · Reply to Hossain Khan's post
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
Hossain Khan
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!
joschi
🐳 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
Suzanne Aldrich (she/her)
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
🌈 Kerblambuli 🦄
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
Jeff Sikes
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:
Adam ♿
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.
Ross Grady
So, for example, if you're a company with > 250 employees or > $10M revenue, and you have a Linux box pulling one open source image a week from Docker Hub, you must buy a Docker subscription for that box. And any others.
Previously, their website verbiage was focused solely on usage of Docker Desktop by enterprises.
If you are an #OpenSource maintainer and you're publishing container images on Docker Hub, they are monetizing your images, and they're doing so via a flat monthly rate regardless of consumption level. (IMHO that rate is too high, but YMMV, I guess)
This is obviously their prerogative. Really my only request/suggestion to Open Source maintainers who publish container images would be to consider also publishing them on GitHub's container registry (aka GitHub Packages) or any other registry, rather than single-sourcing with Docker Hub.
:vfd: holm 🦻🏻🤯 :abc:
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.
Schenkl 🏳️🌈
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:
David Vasandani
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.
BLACKVOID ⚫️
@[email protected] · Reply to JRSofty's post
@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.
BLACKVOID ⚫️
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.
JRSofty
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!
Ariel
Finally: Nix devShells used to build containers for GitLab CI jobs.
https://gitlab.com/arichtman-srt/nix-devshell-ci-container
If anyone wants to help me dive deeper into this I'd love to get right into why `streamNixShellImage` doesn't work...
#Nix #CICD #GitLabCI #DevOps #PlatformEngineering #Docker #Containers #Podman
Kris Hardy 🌮
@[email protected] · Reply to Kris Hardy 🌮's post
To my #FDIR friends: are there any good playbooks you have for #fdir of #docker containers, especially #Azure #ContainerApps or #ContainerInstances?
Matt Cengia (seeking work)
: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/
.:\dGh/:.
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
Jon Seager
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
Deekshith Allamaneni
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
Paul Wilde
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
Drew Naylor
gemma lynn
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.
ale
Aparte de por seguridad y mantenimiento, me gusta usar #docker porque en alguna ocasión me ha petado alguna máquina y he podido levantar los servicios en minutos.
ale
Una de las cosas que más me gustan del nuevo eclipse es poder desplegar el proyecto en #docker directamente 🐳
ale
ale
ale
Pues funciona perfectamente la red en el contenedor de #docker.
ale
Nuevo repositorio que he creado evolucionando un proyecto de #docker para usar el IDS Snort2 en la última versión.
https://gitlab.com/manalejandro/snort2-docker
mk
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
Jeff Standen
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
Robert von Burg
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.
Uffe
Lidt om mig, meget om IT
#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.
Rory McCune
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.
Magnus Hedemark
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
Artemis
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!