#dockerized — Public Fediverse posts

Pixelfed - vollständig in Containern, quasi als one-click Installation. Alles noch irgendwie beta. Aber tut schon mal. #pixelfed #docker #container #dockerized #fediverse

https://github.com/aheil/pixelfed-dockerized

I tried a #dockerized self-hosted #AppFlowy, hoping for seamless synchronization. However, it didn't sync between my devices, so I switched back to #Obsidian. I like how simple, fast, and yet extendable it is, if necessary.

#learnedfromexperience

I tried a #dockerized self-hosted #AppFlowy, hoping for seamless synchronization. However, it didn't sync between my devices, so I switched back to #Obsidian. I like how simple, fast, and yet extendable it is, if necessary.

#learnedfromexperience

I tried a #dockerized self-hosted #AppFlowy, hoping for seamless synchronization. However, it didn't sync between my devices, so I switched back to #Obsidian. I like how simple, fast, and yet extendable it is, if necessary.

#learnedfromexperience

I tried a #dockerized self-hosted #AppFlowy, hoping for seamless synchronization. However, it didn't sync between my devices, so I switched back to #Obsidian. I like how simple, fast, and yet extendable it is, if necessary.

#learnedfromexperience

I tried a #dockerized self-hosted #AppFlowy, hoping for seamless synchronization. However, it didn't sync between my devices, so I switched back to #Obsidian. I like how simple, fast, and yet extendable it is, if necessary.

#learnedfromexperience

I really like to do #devlogs, so here is one:
I implemented a lot of things in my blog the last couple of days.
From generating an #rssfeed, listing my #github projects in a #serverside fetched view, to the Onion-Location header used by #brave to tell users that there's an #onionservice available. I've also #dockerized it. It looks like it's not gonna take too much time until i can finally publish it.

I really like to do #devlogs, so here is one:
I implemented a lot of things in my blog the last couple of days.
From generating an #rssfeed, listing my #github projects in a #serverside fetched view, to the Onion-Location header used by #brave to tell users that there's an #onionservice available. I've also #dockerized it. It looks like it's not gonna take too much time until i can finally publish it.

I really like to do #devlogs, so here is one:
I implemented a lot of things in my blog the last couple of days.
From generating an #rssfeed, listing my #github projects in a #serverside fetched view, to the Onion-Location header used by #brave to tell users that there's an #onionservice available. I've also #dockerized it. It looks like it's not gonna take too much time until i can finally publish it.

I really like to do #devlogs, so here is one:
I implemented a lot of things in my blog the last couple of days.
From generating an #rssfeed, listing my #github projects in a #serverside fetched view, to the Onion-Location header used by #brave to tell users that there's an #onionservice available. I've also #dockerized it. It looks like it's not gonna take too much time until i can finally publish it.

I really like to do #devlogs, so here is one:
I implemented a lot of things in my blog the last couple of days.
From generating an #rssfeed, listing my #github projects in a #serverside fetched view, to the Onion-Location header used by #brave to tell users that there's an #onionservice available. I've also #dockerized it. It looks like it's not gonna take too much time until i can finally publish it.

Just spent two solid days trying to figure out why my #dockerized #ASPNet project wouldn't publish to my #docker #registry from #VisualStudio.

Wanna take a wild guess as to the problem? Was it my code? Was it my configuration?

No. Turns out that Docker Desktop 4.3x just has a bug with Visual Studio. :pepe_g: That's a lot of my life I can't get back for something so stupid.