These are some refreshingly different things to consider running on Docker.

Covered in the linked article are:

• game servers for popular multiplayer titles
  
• Kasm Workspaces
  
• LLMs and image generators (Generative AI)
  
• emulate retro games inside your browser
  
• macOS

See https://www.xda-developers.com/coolest-things-you-can-run-on-docker
#Blog, #docker, #gaming, #technology

Como ver contenido acestream en Linux https://myblog.clonbg.es/como-ver-contenido-acestream-en-linux/ #Docker #Media https://clonbg.es

Como ver contenido acestream en Linux https://myblog.clonbg.es/como-ver-contenido-acestream-en-linux/ #Docker #Media https://clonbg.es

Ich habe heute eine Adaption des #MediaWiki #Docker Images gebastelt: https://hub.docker.com/repository/docker/gbeine/mediawiki

Meine Änderung ist, dass mein Image auf mediawiki-core basiert und skins und extensions über Volumes hinzugefügt werden können.
Außerdem unterstützt mein Image Authorisierung für Bilder, sperrt mw-config wenn LocalSettings.php vorhanden ist und führt automatisch update.php aus, wenn Extensions das erfordern.

Allerdings habe ich nur Debian/Apache laufen; andere Varianten unterstütze ich damit nicht.

It took me a long time: Here is how I put a #django app in #docker, serve it with #traefik and automate the deployment with #ansible

I started the project at #GPN and consider it finished with this blog post 🥳

https://hyteck.de/post/deploying-django-with-docker-and-ansible/

Essentially #flatpak is to desktop Linux what #docker is to servers IMHO. It tries to solve the "works on my machine"-problem by essentially bringing the developers machine to the end user.

Although now everyone has "the same machine" now a lot of new problems are arising, especially because with Docker and Flatpak the *developers* need to care about the "package". Which may work in some cases, but often might also lead to important updates not being distributed all over the place