Note* This is in Linux folder because I've only tested extensively all these on linux debian system, but should work fine on any linux system the same. windows ehhh good luck. Luckily all these containers have backends you can connect to from windows system through the browser. Which is lovely. i manage everything from windows system, but I host my backend linux.
Below is a list of containers I’ve tested and recommend for various home server tasks.
- adguard
Network-wide ad blocker and privacy protection.
- amule
Peer-to-peer file sharing client for the eDonkey network.
- apprise
Unified notification service for multiple platforms.
- audiobookshelf
Self-hosted audiobook server and web player.
- authelia
Authentication and authorization server for your applications.
- bazarr
Subtitle management for Radarr and Sonarr.
- beets
Music library organizer and tagger.
- calibre
E-book management software.
- calibre-web
Web-based interface for Calibre e-book library.
- chd-converter
Tool for converting disk images to CHD format.
- code-server
VS Code running on a remote server accessible through the browser.
- ddclient
Dynamic DNS update client.
- deemix
Music downloader for Deezer.
- deluge
Lightweight, open-source BitTorrent client.
- dillinger
Online Markdown editor.
- doublecommander
Cross-platform file manager.
- elasticsearch
Distributed search and analytics engine.
- filebrowser
Web-based file manager for your server.
- flaresolverr
Proxy server to bypass Cloudflare protection.
- gamevault
Game library manager.
- gameyfin
Game streaming server.
- gitea
Self-hosted Git service.
- glances
System monitoring tool.
- gluetun
VPN client for Docker containers.
- gmod
Garry's Mod game server.
- grafana
Analytics and monitoring dashboard.
- grifter
Automation and scripting tool.
- headphones
Music download manager for Usenet and torrents.
- heimdall
Application dashboard for your server.
- homarr
Modern dashboard for managing your home server.
- homeassistant
Open-source home automation platform.
- homebridge
HomeKit support for non-Apple devices.
- immich
Self-hosted photo and video backup solution.
- jackett
API support for torrent indexers.
- jdownloader
Download manager for various file hosts.
- jellyfin
Open-source media server.
- joplin
Note-taking and to-do application.
- jupyter
Interactive notebooks for code and data.
- kometa
Media library metadata manager.
- lazylibrarian
Book download and management tool.
- libation
Audiobook downloader and manager.
- lidarr
Music collection manager for Usenet and torrents.
- mailcow
Self-hosted mail server suite.
- mailserver
General purpose mail server.
- mariadb
Open-source relational database.
- mastadon
Decentralized social network server.
- mastodon
Decentralized social network server.
- mealie
Recipe management and meal planning.
- mediacms
Open-source media content management system.
- minecraft-paper_itzg
Minecraft Paper server by itzg.
- mkvtoolnix
Tools for working with Matroska media files.
- mongodb
NoSQL document database.
- mosquitto-eclipse
MQTT broker for IoT messaging.
- musicbrainz
Open music encyclopedia database.
- n8n
Workflow automation tool.
- navidrome
Music streaming server.
- netbootxyz
Network boot server for OS installations.
- nginxproxymanager
Web proxy management with a GUI.
- node-red
Flow-based programming for IoT.
- nostr-relay
Relay server for Nostr protocol.
- notifiarr
Notification integration for media servers.
- nzbget
Usenet downloader.
- ombi
Media request management for Plex/Emby/Jellyfin.
- open-assistant
Open-source AI assistant.
- openbooks
Book search and download tool.
- organizr
Unified web interface for your services.
- paperless-ng
Document management system.
- phpmyadmin
Web-based MySQL/MariaDB administration.
- picard
Music tagger by MusicBrainz.
- pidgin
Multi-protocol chat client.
- plex
Media server for streaming your content.
- plex-image-cleanup
Tool to clean up Plex image cache.
- pms-docker
Plex Media Server Docker image.
- podgrab
Podcast downloader and manager.
- portainer
Docker management GUI.
- portainer-be
Portainer backend service.
- portainer-ce
Portainer Community Edition.
- postgres_data
PostgreSQL database data container.
- prometheus
Monitoring and alerting toolkit.
- prowlarr
Indexer manager for Usenet and torrents.
- qbittorrent
Open-source BitTorrent client.
- radarr
Movie collection manager for Usenet and torrents.
- rainloop
Webmail client.
- readarr
Book collection manager for Usenet and torrents.
- recyclarr
Syncs trash/recycle settings for media managers.
- requestrr
Discord bot for media requests.
- romm
Retro game manager.
- romvault
ROM management and auditing tool.
- sabnzbd
Usenet binary downloader.
- shoutrrr
Notification library for various services.
- sonarr
TV series collection manager for Usenet and torrents.
- soulseek
Peer-to-peer music sharing client.
- spotify-playlist-generator
Tool to generate Spotify playlists.
- spotisub
Spotify playlist subscription manager.
- sptnr
Spotify playlist and library manager.
- swag-letsencrypt
Secure Web Application Gateway with Let's Encrypt.
- swag-letsencrypt_duckdns
SWAG with DuckDNS integration.
- tautulli
Plex usage monitoring and analytics.
- tdarr
Distributed media transcoding system.
- tellytv
IPTV proxy for Plex.
- traefik
Modern reverse proxy and load balancer.
- trilium
Hierarchical note-taking application.
- tubearchivist
YouTube archiving and management tool.
- tvheadend
TV streaming server for DVB, ATSC, IPTV.
- unpackerr
Automated extraction of archives for media managers.
- vscodium
Open-source build of VS Code.
- watchtower
Automatic update for Docker containers.
- web-dev-compose.yml
Web development Docker Compose setup.
- webgrabplus
EPG (Electronic Program Guide) grabber.
- wg-easy
Simple WireGuard VPN management.
- whisper-webui
Web UI for OpenAI Whisper speech-to-text.
- wireguard
Fast, modern VPN tunnel.
- wireshark
Network protocol analyzer.
- xbackbone
File sharing and image hosting platform.
- xteve
IPTV proxy for Plex and Emby.
- youtube-dl-material
Web UI for youtube-dl downloads.
- youtube-dl-server
REST API for youtube-dl.
Gitea Full Link:
https://gitea.sickgaming.net/sickprodigy/home-server
You will find instructions if you scroll down on gitea full link page. Explains everything fairly well.
Let me know if you have any questions.]]>
Note* This is in Linux folder because I've only tested extensively all these on linux debian system, but should work fine on any linux system the same. windows ehhh good luck. Luckily all these containers have backends you can connect to from windows system through the browser. Which is lovely. i manage everything from windows system, but I host my backend linux.
Below is a list of containers I’ve tested and recommend for various home server tasks.
- adguard
Network-wide ad blocker and privacy protection.
- amule
Peer-to-peer file sharing client for the eDonkey network.
- apprise
Unified notification service for multiple platforms.
- audiobookshelf
Self-hosted audiobook server and web player.
- authelia
Authentication and authorization server for your applications.
- bazarr
Subtitle management for Radarr and Sonarr.
- beets
Music library organizer and tagger.
- calibre
E-book management software.
- calibre-web
Web-based interface for Calibre e-book library.
- chd-converter
Tool for converting disk images to CHD format.
- code-server
VS Code running on a remote server accessible through the browser.
- ddclient
Dynamic DNS update client.
- deemix
Music downloader for Deezer.
- deluge
Lightweight, open-source BitTorrent client.
- dillinger
Online Markdown editor.
- doublecommander
Cross-platform file manager.
- elasticsearch
Distributed search and analytics engine.
- filebrowser
Web-based file manager for your server.
- flaresolverr
Proxy server to bypass Cloudflare protection.
- gamevault
Game library manager.
- gameyfin
Game streaming server.
- gitea
Self-hosted Git service.
- glances
System monitoring tool.
- gluetun
VPN client for Docker containers.
- gmod
Garry's Mod game server.
- grafana
Analytics and monitoring dashboard.
- grifter
Automation and scripting tool.
- headphones
Music download manager for Usenet and torrents.
- heimdall
Application dashboard for your server.
- homarr
Modern dashboard for managing your home server.
- homeassistant
Open-source home automation platform.
- homebridge
HomeKit support for non-Apple devices.
- immich
Self-hosted photo and video backup solution.
- jackett
API support for torrent indexers.
- jdownloader
Download manager for various file hosts.
- jellyfin
Open-source media server.
- joplin
Note-taking and to-do application.
- jupyter
Interactive notebooks for code and data.
- kometa
Media library metadata manager.
- lazylibrarian
Book download and management tool.
- libation
Audiobook downloader and manager.
- lidarr
Music collection manager for Usenet and torrents.
- mailcow
Self-hosted mail server suite.
- mailserver
General purpose mail server.
- mariadb
Open-source relational database.
- mastadon
Decentralized social network server.
- mastodon
Decentralized social network server.
- mealie
Recipe management and meal planning.
- mediacms
Open-source media content management system.
- minecraft-paper_itzg
Minecraft Paper server by itzg.
- mkvtoolnix
Tools for working with Matroska media files.
- mongodb
NoSQL document database.
- mosquitto-eclipse
MQTT broker for IoT messaging.
- musicbrainz
Open music encyclopedia database.
- n8n
Workflow automation tool.
- navidrome
Music streaming server.
- netbootxyz
Network boot server for OS installations.
- nginxproxymanager
Web proxy management with a GUI.
- node-red
Flow-based programming for IoT.
- nostr-relay
Relay server for Nostr protocol.
- notifiarr
Notification integration for media servers.
- nzbget
Usenet downloader.
- ombi
Media request management for Plex/Emby/Jellyfin.
- open-assistant
Open-source AI assistant.
- openbooks
Book search and download tool.
- organizr
Unified web interface for your services.
- paperless-ng
Document management system.
- phpmyadmin
Web-based MySQL/MariaDB administration.
- picard
Music tagger by MusicBrainz.
- pidgin
Multi-protocol chat client.
- plex
Media server for streaming your content.
- plex-image-cleanup
Tool to clean up Plex image cache.
- pms-docker
Plex Media Server Docker image.
- podgrab
Podcast downloader and manager.
- portainer
Docker management GUI.
- portainer-be
Portainer backend service.
- portainer-ce
Portainer Community Edition.
- postgres_data
PostgreSQL database data container.
- prometheus
Monitoring and alerting toolkit.
- prowlarr
Indexer manager for Usenet and torrents.
- qbittorrent
Open-source BitTorrent client.
- radarr
Movie collection manager for Usenet and torrents.
- rainloop
Webmail client.
- readarr
Book collection manager for Usenet and torrents.
- recyclarr
Syncs trash/recycle settings for media managers.
- requestrr
Discord bot for media requests.
- romm
Retro game manager.
- romvault
ROM management and auditing tool.
- sabnzbd
Usenet binary downloader.
- shoutrrr
Notification library for various services.
- sonarr
TV series collection manager for Usenet and torrents.
- soulseek
Peer-to-peer music sharing client.
- spotify-playlist-generator
Tool to generate Spotify playlists.
- spotisub
Spotify playlist subscription manager.
- sptnr
Spotify playlist and library manager.
- swag-letsencrypt
Secure Web Application Gateway with Let's Encrypt.
- swag-letsencrypt_duckdns
SWAG with DuckDNS integration.
- tautulli
Plex usage monitoring and analytics.
- tdarr
Distributed media transcoding system.
- tellytv
IPTV proxy for Plex.
- traefik
Modern reverse proxy and load balancer.
- trilium
Hierarchical note-taking application.
- tubearchivist
YouTube archiving and management tool.
- tvheadend
TV streaming server for DVB, ATSC, IPTV.
- unpackerr
Automated extraction of archives for media managers.
- vscodium
Open-source build of VS Code.
- watchtower
Automatic update for Docker containers.
- web-dev-compose.yml
Web development Docker Compose setup.
- webgrabplus
EPG (Electronic Program Guide) grabber.
- wg-easy
Simple WireGuard VPN management.
- whisper-webui
Web UI for OpenAI Whisper speech-to-text.
- wireguard
Fast, modern VPN tunnel.
- wireshark
Network protocol analyzer.
- xbackbone
File sharing and image hosting platform.
- xteve
IPTV proxy for Plex and Emby.
- youtube-dl-material
Web UI for youtube-dl downloads.
- youtube-dl-server
REST API for youtube-dl.
Gitea Full Link:
https://gitea.sickgaming.net/sickprodigy/home-server
You will find instructions if you scroll down on gitea full link page. Explains everything fairly well.
Let me know if you have any questions.]]>
Smart Playlists Link:
https://gitea.rcs1.top/sickprodigy/navid...-playlists
I've created around 40+ so far, and I edit out certain artists and genres from showing. You can see how detailed they are above. This is how they look in feishin and navidrome.
Feishin:
![[Image: yWN3nce.png]](https://i.imgur.com/yWN3nce.png)
Navidrome:
![[Image: UGOgx3E.png]](https://i.imgur.com/UGOgx3E.png)
My favorite right now is jukebox Example below:
Code:
{
"title": "-Jukebox ;)",
"comment": "The highest rated music on random, discounting recently played.",
"any": [
{ "all": [
{"is": {"rating": 3}},
{"notInTheLast": {"lastPlayed": 90}}
]},
{ "all": [
{"is": {"rating": 4}},
{"notInTheLast": {"lastPlayed": 30}}
]},
{ "all": [
{"is": {"rating": 5}},
{"notInTheLast": {"lastPlayed": 10}}
]},
{ "all": [
{"is": {"loved": true}},
{"notInTheLast": {"lastPlayed": 2}}
]}
],
"sort": "lastPlayed",
"order": "desc",
"limit": 1000
}To edit navidrome smart playlists, this link will come in handy:
https://www.navidrome.org/docs/usage/smartplaylists/]]>
Smart Playlists Link:
https://gitea.rcs1.top/sickprodigy/navid...-playlists
I've created around 40+ so far, and I edit out certain artists and genres from showing. You can see how detailed they are above. This is how they look in feishin and navidrome.
Feishin:
Navidrome:
My favorite right now is jukebox Example below:
Code:
{
"title": "-Jukebox ;)",
"comment": "The highest rated music on random, discounting recently played.",
"any": [
{ "all": [
{"is": {"rating": 3}},
{"notInTheLast": {"lastPlayed": 90}}
]},
{ "all": [
{"is": {"rating": 4}},
{"notInTheLast": {"lastPlayed": 30}}
]},
{ "all": [
{"is": {"rating": 5}},
{"notInTheLast": {"lastPlayed": 10}}
]},
{ "all": [
{"is": {"loved": true}},
{"notInTheLast": {"lastPlayed": 2}}
]}
],
"sort": "lastPlayed",
"order": "desc",
"limit": 1000
}To edit navidrome smart playlists, this link will come in handy:
https://www.navidrome.org/docs/usage/smartplaylists/]]>
![[Image: FreshRSS-logo.png]](https://github.com/FreshRSS/FreshRSS/raw/edge/docs/img/FreshRSS-logo.png){kind=logo}
Anyone else using an RSS reader? My go to is FreshRSS. What's your favorite feed so I can add some more!
https://github.com/FreshRSS/FreshRSS
A free, self-hostable news aggregator…
![[Image: dPjYgXe.png]](https://i.imgur.com/dPjYgXe.png)
Rss Feeds you can try!
Cointelegraph: https://cointelegraph.com/rss
Noted: https://noted.lol/rss/
TechCrunch: https://techcrunch.com/feed/
IGN: https://www.ign.com/rss/articles/feed
9Gag: http://9gagrss.com/feed/
If you use another rss feed reader, please let me know also! Curious which is the best!]]>
Anyone else using an RSS reader? My go to is FreshRSS. What's your favorite feed so I can add some more!
https://github.com/FreshRSS/FreshRSS
A free, self-hostable news aggregator…
Rss Feeds you can try!
Cointelegraph: https://cointelegraph.com/rss
Noted: https://noted.lol/rss/
TechCrunch: https://techcrunch.com/feed/
IGN: https://www.ign.com/rss/articles/feed
9Gag: http://9gagrss.com/feed/
If you use another rss feed reader, please let me know also! Curious which is the best!]]>
<div><p>Fedora test days are events where anyone can help make certain that changes in Fedora work well in an upcoming release. Fedora community members often participate, and the public is welcome at these events. If you’ve never contributed to Fedora before, this is a perfect way to get started.</p>
<p>There are three test days occurring in the next two weeks covering three topics:</p>
<ul>
<li><strong>Tuesday October 03</strong>, is to test the <strong>Fedora Cloud</strong></li>
<li><strong>Thursday October 05 </strong>, is to test the <strong>Fedora Upgrade</strong></li>
<li><strong>Monday October 09 </strong>, is to test <strong>Virtualization</strong> </li>
</ul>
<p>Come and test with us to make Fedora 39 even better. Read more below on how to do it.</p>
<p> <span id="more-38873"></span> </p>
<h2 class="wp-block-heading">Fedora Cloud test day</h2>
<p>Fedora Linux 39 is coming close to the release date and the Fedora Cloud SIG would like to get the community together to find and squash some bugs.</p>
<p>The test day will occur on <strong>Tuesday October 03</strong>. This event will test Fedora Cloud Base content. See the <a href="http://fedoraproject.org/wiki/Test_Day:2023-10-03_Fedora_39_Cloud_Testday" target="_blank" rel="noreferrer noopener">wiki page</a> for links to the Beta Cloud Base Images. We have qcow, AMI, and ISO images ready for testing.</p>
<h2 class="wp-block-heading">Upgrade test day</h2>
<p>As we come closer to Fedora Linux 39 release dates, it’s time to test upgrades. This release has a lot of <a href="https://fedoraproject.org/wiki/Releases/39/ChangeSet" target="_blank" rel="noreferrer noopener">changes</a> and it becomes essential that we test the graphical upgrade methods as well as the command line methods.</p>
<p>This test day will happen on <strong>Thursday, October 05</strong>. It will test upgrading from a full updated F37 and F38 to F39 for all architectures (x86_64, ARM, aarch64) and variants (WS, cloud, server, silverblue, IoT). See this <a href="http://fedoraproject.org/wiki/Test_Day:2023-10-05_F39_Upgrade_Test_Day" target="_blank" rel="noreferrer noopener">wiki page</a> for information and details. </p>
<h2 class="wp-block-heading">Virtualization test day</h2>
<p>This test day will happen on <strong> Monday, October 09</strong> and will test all forms of virtualization possible in Fedora. The <a href="http://fedoraproject.org/wiki/Test_Day:2023-10-09_Virtualization" target="_blank" rel="noreferrer noopener">test day</a> will focus on testing Fedora or your favorite distro inside a bare metal implementation of Fedora running Boxes, KVM, VirtualBox and whatever you have. The general features of installing the OS and working with it are outlined in the test cases which you will find on the <a href="https://testdays.fedoraproject.org/events/171" target="_blank" rel="noreferrer noopener">results</a> page.</p>
<h2 class="wp-block-heading">How do test days work?</h2>
<p>A test day is an event where anyone can help make certain that changes in Fedora work well in an upcoming release. Fedora community members <a href="https://fedoramagazine.org/?s=test+days" target="_blank" rel="noreferrer noopener">often participate</a>, and the public is welcome at these events. Test days are the perfect way to start contributing if you not in the past.</p>
<p>The only requirement to get started is the ability to download test materials (which include some large files) and then read and follow directions step by step.</p>
<p>Detailed information about all the test days are on the wiki page links provided above. If you are available on or around the days of the events, please do some testing and report your results.</p>
</div>
https://www.sickgaming.net/blog/2023/09/...-test-day/]]>
<div><p>Fedora test days are events where anyone can help make certain that changes in Fedora work well in an upcoming release. Fedora community members often participate, and the public is welcome at these events. If you’ve never contributed to Fedora before, this is a perfect way to get started.</p>
<p>There are three test days occurring in the next two weeks covering three topics:</p>
<ul>
<li><strong>Tuesday October 03</strong>, is to test the <strong>Fedora Cloud</strong></li>
<li><strong>Thursday October 05 </strong>, is to test the <strong>Fedora Upgrade</strong></li>
<li><strong>Monday October 09 </strong>, is to test <strong>Virtualization</strong> </li>
</ul>
<p>Come and test with us to make Fedora 39 even better. Read more below on how to do it.</p>
<p> <span id="more-38873"></span> </p>
<h2 class="wp-block-heading">Fedora Cloud test day</h2>
<p>Fedora Linux 39 is coming close to the release date and the Fedora Cloud SIG would like to get the community together to find and squash some bugs.</p>
<p>The test day will occur on <strong>Tuesday October 03</strong>. This event will test Fedora Cloud Base content. See the <a href="http://fedoraproject.org/wiki/Test_Day:2023-10-03_Fedora_39_Cloud_Testday" target="_blank" rel="noreferrer noopener">wiki page</a> for links to the Beta Cloud Base Images. We have qcow, AMI, and ISO images ready for testing.</p>
<h2 class="wp-block-heading">Upgrade test day</h2>
<p>As we come closer to Fedora Linux 39 release dates, it’s time to test upgrades. This release has a lot of <a href="https://fedoraproject.org/wiki/Releases/39/ChangeSet" target="_blank" rel="noreferrer noopener">changes</a> and it becomes essential that we test the graphical upgrade methods as well as the command line methods.</p>
<p>This test day will happen on <strong>Thursday, October 05</strong>. It will test upgrading from a full updated F37 and F38 to F39 for all architectures (x86_64, ARM, aarch64) and variants (WS, cloud, server, silverblue, IoT). See this <a href="http://fedoraproject.org/wiki/Test_Day:2023-10-05_F39_Upgrade_Test_Day" target="_blank" rel="noreferrer noopener">wiki page</a> for information and details. </p>
<h2 class="wp-block-heading">Virtualization test day</h2>
<p>This test day will happen on <strong> Monday, October 09</strong> and will test all forms of virtualization possible in Fedora. The <a href="http://fedoraproject.org/wiki/Test_Day:2023-10-09_Virtualization" target="_blank" rel="noreferrer noopener">test day</a> will focus on testing Fedora or your favorite distro inside a bare metal implementation of Fedora running Boxes, KVM, VirtualBox and whatever you have. The general features of installing the OS and working with it are outlined in the test cases which you will find on the <a href="https://testdays.fedoraproject.org/events/171" target="_blank" rel="noreferrer noopener">results</a> page.</p>
<h2 class="wp-block-heading">How do test days work?</h2>
<p>A test day is an event where anyone can help make certain that changes in Fedora work well in an upcoming release. Fedora community members <a href="https://fedoramagazine.org/?s=test+days" target="_blank" rel="noreferrer noopener">often participate</a>, and the public is welcome at these events. Test days are the perfect way to start contributing if you not in the past.</p>
<p>The only requirement to get started is the ability to download test materials (which include some large files) and then read and follow directions step by step.</p>
<p>Detailed information about all the test days are on the wiki page links provided above. If you are available on or around the days of the events, please do some testing and report your results.</p>
</div>
https://www.sickgaming.net/blog/2023/09/...-test-day/]]>
<div style="margin: 5px 5% 10px 5%;"><img src="https://www.sickgaming.net/blog/wp-content/uploads/2023/09/share-your-game-achievements-with-gamerzilla.png" width="645" height="582" title="" alt="" /></div><div><p>Gamerzilla is an open source game achievement system that stores and shares your game achievements. Games use libgamerzilla to easily add achievements. The Gamerzilla library is written in C but bindings exist for other languages.</p>
<p>Two years ago I described how to setup a <a href="https://fedoramagazine.org/open-source-game-achievements/" target="_blank" rel="noreferrer noopener">Gamerzilla server</a>. In addition to the .net implementation, php and python implementations are available. But you probably don’t want to run your own server. Here is an introduction to a public server and the Gnome interface.</p>
<p> <span id="more-38793"></span> </p>
<h2 class="wp-block-heading">Public server</h2>
<p>My web server now hosts an instance of <a href="https://identicalsoftware.com/trophy/" target="_blank" rel="noreferrer noopener">Gamerzilla</a> with public registration enabled. To create an account click on the <em>Sign In</em> link on the top right corner. From there click the <em>Register</em> link next to the <em>Login</em> button.</p>
<p>The user accounts collect very little information. Simply enter a username and password. You do not need to enter your real name or email address. As a result, forgotten password is not implemented.</p>
<p>Accounts start as invisible. If you want the public to see your achievements after login, click on your username on the top right of the page and select <em>Make Visible</em>. New users must be approved before they can upload achievements. Currently no indication appears whether you are approved or not.</p>
<h2 class="wp-block-heading">Getting an achievement</h2>
<p>Before you get your first achievement, you need to install the Gamerzilla gnome shell extension with:</p>
<pre class="wp-block-preformatted">sudo dnf install gnome-shell-extension</pre>
<p> After installation you will need to logout and log back in. The extension needs to be enabled with the the following:</p>
<pre class="wp-block-preformatted">gnome-extensions enable gamerzilla@gamerzilla.identicalsoftware.com </pre>
<p>The game controller icon appears in the top bar of the gnome shell.</p>
<p>Click on the controller icon and select <em>preferences</em>. On the resulting screen enter your gamerzilla url including the trailing slash but without the ‘trophy’ destination for the UI. If using my server, the value will be ‘<em>https://identicalsoftware.com/</em> ‘. Fill in your username and password. Click on save. By default Automatic Connect is enabled. If you don’t want to always connect disable this.</p>
<figure class="wp-block-image size-full"><a href="https://www.sickgaming.net/blog/wp-content/uploads/2023/09/share-your-game-achievements-with-gamerzilla.png"><img decoding="async" fetchpriority="high" width="645" height="582" src="https://www.sickgaming.net/blog/wp-content/uploads/2023/09/share-your-game-achievements-with-gamerzilla.png" alt="" class="wp-image-38810" /></a><figcaption class="wp-element-caption">Gamerzilla Controller menu</figcaption></figure>
<p>Unfortunately a bug prevents the shell extension from working right away. You need to logout and log back in again. Fixing this is high priority.</p>
<h2 class="wp-block-heading">Currently Supported Games</h2>
<p>Several games in the Fedora repository support Gamerzilla achievements. If you want to get one to try it out, I suggest Shippy 1984, Seahorse Adventures, or Anagramarama. Seahorse Adventures will store some progress as soon as you complete a single level. If you play Super Tux Kart, you may already have achievements. Simply starting the game will synch any previous completed achievements. Gamerzilla does not display any notification when achievements complete but games may implement it on their own.</p>
<h2 class="wp-block-heading">Going Forward</h2>
<p>Besides fixing the bug with connecting the first time, I want a local browser for achievements. That way you can view all your game achievements without forcing you to upload them.</p>
<p>Achievements do have negative aspects. Some people feel compelled to complete them. This can lead to negative play experience, if the achievements are very difficult. I understand this concern but some people enjoy these aspects as well. More importantly, to attract and retain players, I feel open source games need a game achievement system.</p>
<p>We need more games to implement Gamerzilla achievements. We need players to show their support for the system. I continue to add achievements to my games and other open source games I try out.</p>
</div>
https://www.sickgaming.net/blog/2023/09/...amerzilla/]]>
<div style="margin: 5px 5% 10px 5%;"><img src="https://www.sickgaming.net/blog/wp-content/uploads/2023/09/share-your-game-achievements-with-gamerzilla.png" width="645" height="582" title="" alt="" /></div><div><p>Gamerzilla is an open source game achievement system that stores and shares your game achievements. Games use libgamerzilla to easily add achievements. The Gamerzilla library is written in C but bindings exist for other languages.</p>
<p>Two years ago I described how to setup a <a href="https://fedoramagazine.org/open-source-game-achievements/" target="_blank" rel="noreferrer noopener">Gamerzilla server</a>. In addition to the .net implementation, php and python implementations are available. But you probably don’t want to run your own server. Here is an introduction to a public server and the Gnome interface.</p>
<p> <span id="more-38793"></span> </p>
<h2 class="wp-block-heading">Public server</h2>
<p>My web server now hosts an instance of <a href="https://identicalsoftware.com/trophy/" target="_blank" rel="noreferrer noopener">Gamerzilla</a> with public registration enabled. To create an account click on the <em>Sign In</em> link on the top right corner. From there click the <em>Register</em> link next to the <em>Login</em> button.</p>
<p>The user accounts collect very little information. Simply enter a username and password. You do not need to enter your real name or email address. As a result, forgotten password is not implemented.</p>
<p>Accounts start as invisible. If you want the public to see your achievements after login, click on your username on the top right of the page and select <em>Make Visible</em>. New users must be approved before they can upload achievements. Currently no indication appears whether you are approved or not.</p>
<h2 class="wp-block-heading">Getting an achievement</h2>
<p>Before you get your first achievement, you need to install the Gamerzilla gnome shell extension with:</p>
<pre class="wp-block-preformatted">sudo dnf install gnome-shell-extension</pre>
<p> After installation you will need to logout and log back in. The extension needs to be enabled with the the following:</p>
<pre class="wp-block-preformatted">gnome-extensions enable gamerzilla@gamerzilla.identicalsoftware.com </pre>
<p>The game controller icon appears in the top bar of the gnome shell.</p>
<p>Click on the controller icon and select <em>preferences</em>. On the resulting screen enter your gamerzilla url including the trailing slash but without the ‘trophy’ destination for the UI. If using my server, the value will be ‘<em>https://identicalsoftware.com/</em> ‘. Fill in your username and password. Click on save. By default Automatic Connect is enabled. If you don’t want to always connect disable this.</p>
<figure class="wp-block-image size-full"><a href="https://www.sickgaming.net/blog/wp-content/uploads/2023/09/share-your-game-achievements-with-gamerzilla.png"><img decoding="async" fetchpriority="high" width="645" height="582" src="https://www.sickgaming.net/blog/wp-content/uploads/2023/09/share-your-game-achievements-with-gamerzilla.png" alt="" class="wp-image-38810" /></a><figcaption class="wp-element-caption">Gamerzilla Controller menu</figcaption></figure>
<p>Unfortunately a bug prevents the shell extension from working right away. You need to logout and log back in again. Fixing this is high priority.</p>
<h2 class="wp-block-heading">Currently Supported Games</h2>
<p>Several games in the Fedora repository support Gamerzilla achievements. If you want to get one to try it out, I suggest Shippy 1984, Seahorse Adventures, or Anagramarama. Seahorse Adventures will store some progress as soon as you complete a single level. If you play Super Tux Kart, you may already have achievements. Simply starting the game will synch any previous completed achievements. Gamerzilla does not display any notification when achievements complete but games may implement it on their own.</p>
<h2 class="wp-block-heading">Going Forward</h2>
<p>Besides fixing the bug with connecting the first time, I want a local browser for achievements. That way you can view all your game achievements without forcing you to upload them.</p>
<p>Achievements do have negative aspects. Some people feel compelled to complete them. This can lead to negative play experience, if the achievements are very difficult. I understand this concern but some people enjoy these aspects as well. More importantly, to attract and retain players, I feel open source games need a game achievement system.</p>
<p>We need more games to implement Gamerzilla achievements. We need players to show their support for the system. I continue to add achievements to my games and other open source games I try out.</p>
</div>
https://www.sickgaming.net/blog/2023/09/...amerzilla/]]>
<div style="margin: 5px 5% 10px 5%;"><img src="https://www.sickgaming.net/blog/wp-content/uploads/2023/08/using-cockpit-to-graphically-manage-systems-without-installing-cockpit-on-them.png" width="1024" height="748" title="" alt="" /></div><div><p>It probably sounds too good to be true: the ability to manage remote systems using an easy to use, intuitive graphical interface – without the need to install extra software on the remote systems, enable additional services, or make any other changes on the remote systems. This functionality, however, is now available with a combination of the recently introduced Python bridge for Cockpit and the Cockpit Client Flatpak! This allows Cockpit to manage remote systems, assuming only SSH access and that Python is installed on the remote host. Read on for more information on how this works and how to get started.</p>
<p> <span id="more-38635"></span> </p>
<p>If you are not familiar with Cockpit, it is described on the <a href="https://cockpit-project.org/" target="_blank" rel="noreferrer noopener">project’s web site</a> as a web-based graphical interface for servers. Cockpit is intended for everyone, especially those who are:</p>
<ul>
<li><strong>new to Linux </strong>(including Windows admins)</li>
<li><strong>familiar with Linux </strong>and want an easy, graphical way to administer servers</li>
<li><strong>expert admins</strong> who mainly use other tools but want an overview on individual systems</li>
</ul>
<p>You can easily and intuitively complete a variety of tasks from Cockpit. These including tasks such as:</p>
<ul>
<li> expanding the size of a filesystem</li>
<li>creating a network bond</li>
<li>modifying the firewall</li>
<li>viewing log entries</li>
<li>viewing real time and historical performance information</li>
<li>managing Podman containers</li>
<li>managing KVM virtual machines</li>
</ul>
<p>and many additional tasks.</p>
<h2 class="wp-block-heading">Objections to using Cockpit on systems</h2>
<p>In the past, I’ve heard two main objections to using Cockpit on systems:</p>
<ol>
<li>I don’t want to run the Cockpit web server on my systems. Additional network services like this increase the attack surface. I don’t want to open another port in the firewall. I don’t want more HTTPS certificates in my environment to manage and maintain.</li>
<li>I don’t want to install additional packages on my systems. I don’t even have access to install additional packages). The more packages installed, the larger my footprint is, and the more attack surface there is. For me to install additional packages in a production environment, I have to go through a change management process, etc. What a hassle!</li>
</ol>
<p>Let’s address these one at a time. For the first concern, you have actually had several options for connecting to Cockpit over SSH, without running the Cockpit web server, for quite some time. These options include:</p>
<ul>
<li>The ability to set up a bastion host, which is a host that has the Cockpit web server running on it. You can then connect to Cockpit on the bastion host using a web browser. From the Cockpit login screen on the bastion host you can use the <em>Connect to</em><strong> </strong>option to specify an alternate host to login to (refer to the <em>LoginTo</em> cockpit.conf configuration option). Another option is to authenticate to Cockpit on the bastion host, and use the <em>Add new host</em> option. In either case, the bastion Cockpit host will connect to these additional remote hosts over SSH (so only the bastion host in your environment needs to be running the Cockpit web server).</li>
<li>You can use the Cockpit integration available with the upstream <a href="https://theforeman.org/plugins/foreman_remote_execution/1.7/index.html#3.6Cockpitintegration" target="_blank" rel="noreferrer noopener">Foreman</a>, or downstream <a href="https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/managing_hosts/index#Host_Management_and_Monitoring_Using_Cockpit_managing-hosts" target="_blank" rel="noreferrer noopener">Red Hat Satellite</a>, to connect to Cockpit on systems in your environment over SSH. </li>
<li>You can use the <a href="https://flathub.org/apps/org.cockpit_project.CockpitClient" target="_blank" rel="noreferrer noopener">Cockpit Client Flatpak</a>, which will connect to systems over SSH.</li>
<li>You can use the <a href="https://quay.io/repository/cockpit/ws" target="_blank" rel="noreferrer noopener">cockpit/ws</a> container image. This is a containerized version of the Cockpit web server that acts as a containerized bastion host</li>
</ul>
<p>For more information on these options, refer to the<a href="https://www.redhat.com/en/blog/connecting-rhel-web-console-part-1-ssh-access-methods" target="_blank" rel="noreferrer noopener"> Connecting to the RHEL web console, part 1: SSH access methods</a> blog post. This blog post focuses on the downstream RHEL web console, however, the information also applies to the upstream Cockpit available in Fedora. </p>
<p>This brings me to the second concern, and the main focus of this article. This is the concern that I don’t want to install additional packages on the remote systems I am managing. While there are several options for using the web console without the Cockpit web server, all of these options previously had a prerequisite that the remote systems needed to have at least the <em>cockpit-system</em> package installed. For example, previously if you tried to use the Cockpit Client Flatpak to connect to a remote system that didn’t have Cockpit installed, you’d see an error message stating that the remote system doesn’t have <em>cockpit-bridge</em> installed. </p>
<p>The Cockpit team has replaced the previous Cockpit bridge (implemented using C) with a new bridge written in Python. For a technical overview of the function of the Cockpit bridge, and how the new Python bridge was implemented, refer to the recent <a href="https://www.youtube.com/watch?v=ZAVUG6E0Xd4" target="_blank" rel="noreferrer noopener">Monty Python’s Flying Cockpit</a> DevConf presentation by Allison Karlitskaya and Martin Pitt. </p>
<p>This new Python bridge overcomes the previous limitation requiring Cockpit to be installed on the remote hosts. </p>
<h2 class="wp-block-heading">Using the Cockpit Client Flatpak</h2>
<p>With the Cockpit Client Flatpak application installed on a workstation, we can connect to remote systems over SSH and manage them using Cockpit.</p>
<h3 class="wp-block-heading">Installation</h3>
<p>In the following example, I’m using a Fedora 38 workstation. Install the Cockpit Client Flatpak by simply opening the GNOME Software application and searching for Cockpit. Note that you’ll need to have Flathub enabled in GNOME Software.</p>
<figure class="wp-block-image size-large"><a href="https://www.sickgaming.net/blog/wp-content/uploads/2023/08/using-cockpit-to-graphically-manage-systems-without-installing-cockpit-on-them-7.png"><img decoding="async" loading="lazy" width="1024" height="748" src="https://www.sickgaming.net/blog/wp-content/uploads/2023/08/using-cockpit-to-graphically-manage-systems-without-installing-cockpit-on-them.png" alt="" class="wp-image-38636" /></a></figure>
<h3 class="wp-block-heading">Using the Cockpit Client</h3>
<p>Once installed, you’ll see the following when opening the Cockpit Client:</p>
<figure class="wp-block-image size-large"><a href="https://www.sickgaming.net/blog/wp-content/uploads/2023/08/using-cockpit-to-graphically-manage-systems-without-installing-cockpit-on-them-11.png"><img decoding="async" loading="lazy" width="1024" height="570" src="https://www.sickgaming.net/blog/wp-content/uploads/2023/08/using-cockpit-to-graphically-manage-systems-without-installing-cockpit-on-them-1.png" alt="" class="wp-image-38637" /></a></figure>
<p>You can type in a hostname or IP address that you would like to connect to. To authenticate as a user other than the user you are currently using, you can use the user@hostname syntax. A list of recent hosts that you’ve connected to will appear, if this is not the first time using the Cockpit Client. In that case, you can simply click on a host name to reconnect</p>
<p>If you have SSH key based authentication setup, you’ll be logged in to the remote host using the key based authentication. With out SSH keys setup, you’ll be prompted to authenticate with a password. In either case, if it is your first time connecting to the host over SSH, you’ll be prompted to accept the host key fingerprint.</p>
<p>As a special case, you can log into your currently running local session by connecting to <em>localhost</em>, without authentication. </p>
<p>Once connected, you’ll see the Cockpit Overview page:</p>
<figure class="wp-block-image size-large"><a href="https://www.sickgaming.net/blog/wp-content/uploads/2023/08/using-cockpit-to-graphically-manage-systems-without-installing-cockpit-on-them-15.png"><img decoding="async" loading="lazy" width="1024" height="661" src="https://www.sickgaming.net/blog/wp-content/uploads/2023/08/using-cockpit-to-graphically-manage-systems-without-installing-cockpit-on-them-2.png" alt="" class="wp-image-38638" /></a><figcaption class="wp-element-caption">Cockpit overivew menu</figcaption></figure>
<p>Select the <em>Terminal </em> menu item in Cockpit to show that the remote system that I’m logged in to does not have any Cockpit packages installed:</p>
<figure class="wp-block-image size-full"><a href="https://www.sickgaming.net/blog/wp-content/uploads/2023/08/using-cockpit-to-graphically-manage-systems-without-installing-cockpit-on-them-3.png"><img decoding="async" loading="lazy" width="936" height="283" src="https://www.sickgaming.net/blog/wp-content/uploads/2023/08/using-cockpit-to-graphically-manage-systems-without-installing-cockpit-on-them-3.png" alt="" class="wp-image-38639" /></a><figcaption class="wp-element-caption">Cockpit Terminal view</figcaption></figure>
<h2 class="wp-block-heading">Prerequisites for connecting to systems with Cockpit Client</h2>
<p>There are several prerequisites for utilizing Cockpit Client to connect to a remote system. If you are familiar with managing remote hosts with Ansible, you’ll likely already be familiar with the prerequisites. They are the same:</p>
<ol>
<li>You must have connectivity to the remote system over SSH.</li>
<li>You must have a valid user account on the remote system that you can authenticate with.</li>
<li>If you need the ability to complete privileged operations in Cockpit, the user account on the remote system will need sudo privileges.</li>
</ol>
<p>If you are connecting to a remote system that doesn’t have Cockpit installed, there are a couple of additional prerequisites:</p>
<ol>
<li>Python 3.6 or later must be installed on the remote host. This is not usually an issue, with some exceptions, such as Fedora CoreOS which does not include Python by default.</li>
<li>An older version of Cockpit Client can not be used to connect to a newer operating system version. For example, if I installed Cockpit Client on my Fedora 38 workstation today and never updated it, it may not work properly to manage a Fedora 39 or Fedora 40 server in the future.</li>
</ol>
<h2 class="wp-block-heading">Frequently asked questions</h2>
<p>Here are some frequently asked questions about this functionality:</p>
<p><strong>Question:</strong> Cockpit is extendable via additional Applications. Which Cockpit applications are available if I use the Cockpit Client to connect to a remote system that doesn’t have Cockpit installed?</p>
<p><strong>Answer</strong>: Currently, Cockpit Client includes </p>
<ul>
<li><em>cockpit-machines </em>(virtual machine management) </li>
<li><em>cockpit-podman</em> (Podman container management) </li>
<li><em>cockpit-ostree </em>(used to manage rpm-ostree based systems)</li>
<li><em>cockpit-storaged </em>(storage management)</li>
<li><em>cockpit-sosreport</em> (for generating diagnostic reports)</li>
<li><em>cockpit-selinux</em><strong> </strong>(for managing SELinux)</li>
<li><em>cockpit-packagekit</em> (for managing software updates)</li>
<li><em>cockpit-networkmanager</em><strong> </strong>(network management)</li>
<li><em>cockpit-kdump</em> (kernel dump configuration) </li>
</ul>
<p>The Cockpit team is looking for feedback on what Cockpit applications you’d like to see included in the Cockpit Client. Post a comment below with your feedback. </p>
<p><strong>Question</strong>: I connected to a remote system that doesn’t have Cockpit installed, but I don’t see Virtual Machines or one of the other applications listed in the menu. I thought you just said these were included in the Cockpit Client Flatpak?</p>
<p><strong>Answer</strong>: When you login to a remote system that doesn’t have Cockpit packages installed, you’ll only see the menu options for underlying functionality available on the remote system. For example, you’ll only see Virtual Machines in the Cockpit menu if the remote host has the <em>libvirt-dbus</em> package installed. </p>
<p><strong>Question</strong>: Can Cockpit applications available in the Cockpit Client be used with locally installed Cockpit applications on the remote host? In other words, if I need a Cockpit application not included in the Cockpit Client, can I install just that single package on the remote host? </p>
<p><strong>Answer</strong>: No, you cannot mix and match applications included in the Cockpit Client flatpak and those installed locally on the remote host. For a remote host that has the<strong><em> </em></strong><em>cockpit-bridge</em> package installed, Cockpit Client will exclusively use the applications that are installed locally on the remote host. If the remote host does not have the <em>cockpit-bridge</em> package installed, Cockpit Client will exclusively use the applications bundled in the Cockpit Client Flatpak. </p>
<p><strong>Question</strong>: Can I use Cockpit Client to connect to the local host?</p>
<p><strong>Answer</strong>: Yes! Simply open Cockpit Client and type in <em>localhost</em> and you’ll be able to manage the local host. You don’t need to have any Cockpit packages installed on the local host if you use this method. You only need the Cockpit Client Flatpak. </p>
<p><strong>Question: </strong>What Linux distributions can I connect to using the Cockpit Client?</p>
<p><strong>Answer: </strong>Cockpit is compatible with a number of different Linux distributions. For more information, see the <a href="https://cockpit-project.org/running.html" target="_blank" rel="noreferrer noopener">Running Cockpi</a>t page. If connecting to a remote system that doesn’t have Cockpit installed, keep in mind the previously mentioned requirements regarding not connecting to newer OS’s from an older Cockpit Client. </p>
<p><strong>Question</strong>: Does the Cockpit team have any future plans regarding this functionality? </p>
<p><strong>Answer: </strong>The Cockpit team is planning on adding the ability to connect to remote hosts without Cockpit packages installed to the <a href="https://quay.io/repository/cockpit/ws" target="_blank" rel="noreferrer noopener">cockpit-ws container image</a>. See <a href="https://issues.redhat.com/browse/COCKPIT-954" target="_blank" rel="noreferrer noopener">COCKPIT-954</a> ticket for more info. </p>
<p>Have more questions not covered here? Ask them in the comments section below!</p>
<h2 class="wp-block-heading">Conclusion</h2>
<p>The new Python bridge, and the corresponding ability to use the Cockpit Client to connect to remote systems without installing Cockpit, makes it incredibly easy to use Cockpit in almost any circumstance.</p>
<p>Try this out! It’s easy to do. Simply install the Cockpit Client Flatpak, and use it to connect to either your localhost or a remote system. Once you’ve tried it, let us know what you think in the comments below.</p>
</div>
https://www.sickgaming.net/blog/2023/08/...t-on-them/]]>
<div style="margin: 5px 5% 10px 5%;"><img src="https://www.sickgaming.net/blog/wp-content/uploads/2023/08/using-cockpit-to-graphically-manage-systems-without-installing-cockpit-on-them.png" width="1024" height="748" title="" alt="" /></div><div><p>It probably sounds too good to be true: the ability to manage remote systems using an easy to use, intuitive graphical interface – without the need to install extra software on the remote systems, enable additional services, or make any other changes on the remote systems. This functionality, however, is now available with a combination of the recently introduced Python bridge for Cockpit and the Cockpit Client Flatpak! This allows Cockpit to manage remote systems, assuming only SSH access and that Python is installed on the remote host. Read on for more information on how this works and how to get started.</p>
<p> <span id="more-38635"></span> </p>
<p>If you are not familiar with Cockpit, it is described on the <a href="https://cockpit-project.org/" target="_blank" rel="noreferrer noopener">project’s web site</a> as a web-based graphical interface for servers. Cockpit is intended for everyone, especially those who are:</p>
<ul>
<li><strong>new to Linux </strong>(including Windows admins)</li>
<li><strong>familiar with Linux </strong>and want an easy, graphical way to administer servers</li>
<li><strong>expert admins</strong> who mainly use other tools but want an overview on individual systems</li>
</ul>
<p>You can easily and intuitively complete a variety of tasks from Cockpit. These including tasks such as:</p>
<ul>
<li> expanding the size of a filesystem</li>
<li>creating a network bond</li>
<li>modifying the firewall</li>
<li>viewing log entries</li>
<li>viewing real time and historical performance information</li>
<li>managing Podman containers</li>
<li>managing KVM virtual machines</li>
</ul>
<p>and many additional tasks.</p>
<h2 class="wp-block-heading">Objections to using Cockpit on systems</h2>
<p>In the past, I’ve heard two main objections to using Cockpit on systems:</p>
<ol>
<li>I don’t want to run the Cockpit web server on my systems. Additional network services like this increase the attack surface. I don’t want to open another port in the firewall. I don’t want more HTTPS certificates in my environment to manage and maintain.</li>
<li>I don’t want to install additional packages on my systems. I don’t even have access to install additional packages). The more packages installed, the larger my footprint is, and the more attack surface there is. For me to install additional packages in a production environment, I have to go through a change management process, etc. What a hassle!</li>
</ol>
<p>Let’s address these one at a time. For the first concern, you have actually had several options for connecting to Cockpit over SSH, without running the Cockpit web server, for quite some time. These options include:</p>
<ul>
<li>The ability to set up a bastion host, which is a host that has the Cockpit web server running on it. You can then connect to Cockpit on the bastion host using a web browser. From the Cockpit login screen on the bastion host you can use the <em>Connect to</em><strong> </strong>option to specify an alternate host to login to (refer to the <em>LoginTo</em> cockpit.conf configuration option). Another option is to authenticate to Cockpit on the bastion host, and use the <em>Add new host</em> option. In either case, the bastion Cockpit host will connect to these additional remote hosts over SSH (so only the bastion host in your environment needs to be running the Cockpit web server).</li>
<li>You can use the Cockpit integration available with the upstream <a href="https://theforeman.org/plugins/foreman_remote_execution/1.7/index.html#3.6Cockpitintegration" target="_blank" rel="noreferrer noopener">Foreman</a>, or downstream <a href="https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/managing_hosts/index#Host_Management_and_Monitoring_Using_Cockpit_managing-hosts" target="_blank" rel="noreferrer noopener">Red Hat Satellite</a>, to connect to Cockpit on systems in your environment over SSH. </li>
<li>You can use the <a href="https://flathub.org/apps/org.cockpit_project.CockpitClient" target="_blank" rel="noreferrer noopener">Cockpit Client Flatpak</a>, which will connect to systems over SSH.</li>
<li>You can use the <a href="https://quay.io/repository/cockpit/ws" target="_blank" rel="noreferrer noopener">cockpit/ws</a> container image. This is a containerized version of the Cockpit web server that acts as a containerized bastion host</li>
</ul>
<p>For more information on these options, refer to the<a href="https://www.redhat.com/en/blog/connecting-rhel-web-console-part-1-ssh-access-methods" target="_blank" rel="noreferrer noopener"> Connecting to the RHEL web console, part 1: SSH access methods</a> blog post. This blog post focuses on the downstream RHEL web console, however, the information also applies to the upstream Cockpit available in Fedora. </p>
<p>This brings me to the second concern, and the main focus of this article. This is the concern that I don’t want to install additional packages on the remote systems I am managing. While there are several options for using the web console without the Cockpit web server, all of these options previously had a prerequisite that the remote systems needed to have at least the <em>cockpit-system</em> package installed. For example, previously if you tried to use the Cockpit Client Flatpak to connect to a remote system that didn’t have Cockpit installed, you’d see an error message stating that the remote system doesn’t have <em>cockpit-bridge</em> installed. </p>
<p>The Cockpit team has replaced the previous Cockpit bridge (implemented using C) with a new bridge written in Python. For a technical overview of the function of the Cockpit bridge, and how the new Python bridge was implemented, refer to the recent <a href="https://www.youtube.com/watch?v=ZAVUG6E0Xd4" target="_blank" rel="noreferrer noopener">Monty Python’s Flying Cockpit</a> DevConf presentation by Allison Karlitskaya and Martin Pitt. </p>
<p>This new Python bridge overcomes the previous limitation requiring Cockpit to be installed on the remote hosts. </p>
<h2 class="wp-block-heading">Using the Cockpit Client Flatpak</h2>
<p>With the Cockpit Client Flatpak application installed on a workstation, we can connect to remote systems over SSH and manage them using Cockpit.</p>
<h3 class="wp-block-heading">Installation</h3>
<p>In the following example, I’m using a Fedora 38 workstation. Install the Cockpit Client Flatpak by simply opening the GNOME Software application and searching for Cockpit. Note that you’ll need to have Flathub enabled in GNOME Software.</p>
<figure class="wp-block-image size-large"><a href="https://www.sickgaming.net/blog/wp-content/uploads/2023/08/using-cockpit-to-graphically-manage-systems-without-installing-cockpit-on-them-7.png"><img decoding="async" loading="lazy" width="1024" height="748" src="https://www.sickgaming.net/blog/wp-content/uploads/2023/08/using-cockpit-to-graphically-manage-systems-without-installing-cockpit-on-them.png" alt="" class="wp-image-38636" /></a></figure>
<h3 class="wp-block-heading">Using the Cockpit Client</h3>
<p>Once installed, you’ll see the following when opening the Cockpit Client:</p>
<figure class="wp-block-image size-large"><a href="https://www.sickgaming.net/blog/wp-content/uploads/2023/08/using-cockpit-to-graphically-manage-systems-without-installing-cockpit-on-them-11.png"><img decoding="async" loading="lazy" width="1024" height="570" src="https://www.sickgaming.net/blog/wp-content/uploads/2023/08/using-cockpit-to-graphically-manage-systems-without-installing-cockpit-on-them-1.png" alt="" class="wp-image-38637" /></a></figure>
<p>You can type in a hostname or IP address that you would like to connect to. To authenticate as a user other than the user you are currently using, you can use the user@hostname syntax. A list of recent hosts that you’ve connected to will appear, if this is not the first time using the Cockpit Client. In that case, you can simply click on a host name to reconnect</p>
<p>If you have SSH key based authentication setup, you’ll be logged in to the remote host using the key based authentication. With out SSH keys setup, you’ll be prompted to authenticate with a password. In either case, if it is your first time connecting to the host over SSH, you’ll be prompted to accept the host key fingerprint.</p>
<p>As a special case, you can log into your currently running local session by connecting to <em>localhost</em>, without authentication. </p>
<p>Once connected, you’ll see the Cockpit Overview page:</p>
<figure class="wp-block-image size-large"><a href="https://www.sickgaming.net/blog/wp-content/uploads/2023/08/using-cockpit-to-graphically-manage-systems-without-installing-cockpit-on-them-15.png"><img decoding="async" loading="lazy" width="1024" height="661" src="https://www.sickgaming.net/blog/wp-content/uploads/2023/08/using-cockpit-to-graphically-manage-systems-without-installing-cockpit-on-them-2.png" alt="" class="wp-image-38638" /></a><figcaption class="wp-element-caption">Cockpit overivew menu</figcaption></figure>
<p>Select the <em>Terminal </em> menu item in Cockpit to show that the remote system that I’m logged in to does not have any Cockpit packages installed:</p>
<figure class="wp-block-image size-full"><a href="https://www.sickgaming.net/blog/wp-content/uploads/2023/08/using-cockpit-to-graphically-manage-systems-without-installing-cockpit-on-them-3.png"><img decoding="async" loading="lazy" width="936" height="283" src="https://www.sickgaming.net/blog/wp-content/uploads/2023/08/using-cockpit-to-graphically-manage-systems-without-installing-cockpit-on-them-3.png" alt="" class="wp-image-38639" /></a><figcaption class="wp-element-caption">Cockpit Terminal view</figcaption></figure>
<h2 class="wp-block-heading">Prerequisites for connecting to systems with Cockpit Client</h2>
<p>There are several prerequisites for utilizing Cockpit Client to connect to a remote system. If you are familiar with managing remote hosts with Ansible, you’ll likely already be familiar with the prerequisites. They are the same:</p>
<ol>
<li>You must have connectivity to the remote system over SSH.</li>
<li>You must have a valid user account on the remote system that you can authenticate with.</li>
<li>If you need the ability to complete privileged operations in Cockpit, the user account on the remote system will need sudo privileges.</li>
</ol>
<p>If you are connecting to a remote system that doesn’t have Cockpit installed, there are a couple of additional prerequisites:</p>
<ol>
<li>Python 3.6 or later must be installed on the remote host. This is not usually an issue, with some exceptions, such as Fedora CoreOS which does not include Python by default.</li>
<li>An older version of Cockpit Client can not be used to connect to a newer operating system version. For example, if I installed Cockpit Client on my Fedora 38 workstation today and never updated it, it may not work properly to manage a Fedora 39 or Fedora 40 server in the future.</li>
</ol>
<h2 class="wp-block-heading">Frequently asked questions</h2>
<p>Here are some frequently asked questions about this functionality:</p>
<p><strong>Question:</strong> Cockpit is extendable via additional Applications. Which Cockpit applications are available if I use the Cockpit Client to connect to a remote system that doesn’t have Cockpit installed?</p>
<p><strong>Answer</strong>: Currently, Cockpit Client includes </p>
<ul>
<li><em>cockpit-machines </em>(virtual machine management) </li>
<li><em>cockpit-podman</em> (Podman container management) </li>
<li><em>cockpit-ostree </em>(used to manage rpm-ostree based systems)</li>
<li><em>cockpit-storaged </em>(storage management)</li>
<li><em>cockpit-sosreport</em> (for generating diagnostic reports)</li>
<li><em>cockpit-selinux</em><strong> </strong>(for managing SELinux)</li>
<li><em>cockpit-packagekit</em> (for managing software updates)</li>
<li><em>cockpit-networkmanager</em><strong> </strong>(network management)</li>
<li><em>cockpit-kdump</em> (kernel dump configuration) </li>
</ul>
<p>The Cockpit team is looking for feedback on what Cockpit applications you’d like to see included in the Cockpit Client. Post a comment below with your feedback. </p>
<p><strong>Question</strong>: I connected to a remote system that doesn’t have Cockpit installed, but I don’t see Virtual Machines or one of the other applications listed in the menu. I thought you just said these were included in the Cockpit Client Flatpak?</p>
<p><strong>Answer</strong>: When you login to a remote system that doesn’t have Cockpit packages installed, you’ll only see the menu options for underlying functionality available on the remote system. For example, you’ll only see Virtual Machines in the Cockpit menu if the remote host has the <em>libvirt-dbus</em> package installed. </p>
<p><strong>Question</strong>: Can Cockpit applications available in the Cockpit Client be used with locally installed Cockpit applications on the remote host? In other words, if I need a Cockpit application not included in the Cockpit Client, can I install just that single package on the remote host? </p>
<p><strong>Answer</strong>: No, you cannot mix and match applications included in the Cockpit Client flatpak and those installed locally on the remote host. For a remote host that has the<strong><em> </em></strong><em>cockpit-bridge</em> package installed, Cockpit Client will exclusively use the applications that are installed locally on the remote host. If the remote host does not have the <em>cockpit-bridge</em> package installed, Cockpit Client will exclusively use the applications bundled in the Cockpit Client Flatpak. </p>
<p><strong>Question</strong>: Can I use Cockpit Client to connect to the local host?</p>
<p><strong>Answer</strong>: Yes! Simply open Cockpit Client and type in <em>localhost</em> and you’ll be able to manage the local host. You don’t need to have any Cockpit packages installed on the local host if you use this method. You only need the Cockpit Client Flatpak. </p>
<p><strong>Question: </strong>What Linux distributions can I connect to using the Cockpit Client?</p>
<p><strong>Answer: </strong>Cockpit is compatible with a number of different Linux distributions. For more information, see the <a href="https://cockpit-project.org/running.html" target="_blank" rel="noreferrer noopener">Running Cockpi</a>t page. If connecting to a remote system that doesn’t have Cockpit installed, keep in mind the previously mentioned requirements regarding not connecting to newer OS’s from an older Cockpit Client. </p>
<p><strong>Question</strong>: Does the Cockpit team have any future plans regarding this functionality? </p>
<p><strong>Answer: </strong>The Cockpit team is planning on adding the ability to connect to remote hosts without Cockpit packages installed to the <a href="https://quay.io/repository/cockpit/ws" target="_blank" rel="noreferrer noopener">cockpit-ws container image</a>. See <a href="https://issues.redhat.com/browse/COCKPIT-954" target="_blank" rel="noreferrer noopener">COCKPIT-954</a> ticket for more info. </p>
<p>Have more questions not covered here? Ask them in the comments section below!</p>
<h2 class="wp-block-heading">Conclusion</h2>
<p>The new Python bridge, and the corresponding ability to use the Cockpit Client to connect to remote systems without installing Cockpit, makes it incredibly easy to use Cockpit in almost any circumstance.</p>
<p>Try this out! It’s easy to do. Simply install the Cockpit Client Flatpak, and use it to connect to either your localhost or a remote system. Once you’ve tried it, let us know what you think in the comments below.</p>
</div>
https://www.sickgaming.net/blog/2023/08/...t-on-them/]]>
<div><p>The Fedora Project is pleased to announce the immediate availability of Fedora Linux 39 Beta, the next step towards our planned Fedora Linux 39 release at the end of October.</p>
<p>Get the the prerelease of any of our editions from our project website:</p>
<ul>
<li><a href="https://fedoraproject.org/workstation/download/">Fedora Workstation 39 Beta</a></li>
<li><a href="https://fedoraproject.org/server/download/">Fedora Server 39 Beta</a></li>
<li><a href="https://fedoraproject.org/iot/download/">Fedora IoT 39 Beta</a></li>
<li><a href="https://fedoraproject.org/cloud/download/">Fedora Cloud 39 Beta</a> </li>
<li><a href="https://fedoraproject.org/coreos/download/?stream=next">Fedora CoreOS “next” stream</a></li>
</ul>
<p>Or, try one of our many different desktop variants (like KDE Plasma, Xfce, or Cinnamon) from <a href="https://fedoraproject.org/spins/">Fedora Linux Spins</a>.</p>
<p>You can also update an existing system to the beta using <a href="https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/">DNF system-upgrade</a>.</p>
<h2 class="wp-block-heading"><strong>Beta release highlights</strong></h2>
<p>In some ways, this release might seem notable largely for what isn’t here. We’d planned to update the DNF package manager to a new, speedier version. We also hoped to showcase a long-awaited refresh to the user interface for Anaconda, our installation program. However, we decided these things just weren’t ready in time.</p>
<p>Don’t let this get you down, though — this is a healthy process at work. Years ago, we didn’t always have a good way to alter course once we’d accepted a change proposal. We often found ourselves in a situation where the only reasonable way forward was to forge ahead, even if we weren’t happy enough with the change for general users. Now, even though it’s somewhat disappointing, we’re recognizing that these big changes need more time to bake, and putting them back into the oven is a good thing.</p>
<p>I’ve got a kid that always wants to get 100% (or higher!) in every class. I keep telling her, “Really, you learn best when you’re right 80% of the time. Otherwise, you’re not getting enough of a challenge.” To keep up with Fedora’s commitment to innovation, we also need to take risks. If everything went according to plan, that would mean we’re not trying hard enough. At the same time, our process now allows us to take these risks while still making sure the Fedora Linux OS we ship for general use <em>is</em> of A+ quality.</p>
<p>We still plan to bring you these features in the near future, and if they’re of interest to you, please keep your eyes open for upcoming test announcements.</p>
<p>In the meantime, enjoy the many updates across all of Fedora Linux updates, ready for you to test in this new beta.</p>
<h2 class="wp-block-heading">Notable updates</h2>
<p>Fedora Workstation 39 Beta brings us GNOME 45 (itself also in beta). For everyone who needs a free and open source desktop suite, there’s LibreOffice 7.6.</p>
<p>Fedora Cloud images for AWS now default to less-expensive gp3 storage volumes.</p>
<p>We also have an update to the GNU Toolchain (gcc 13.2, binutils 2.40, glibc 2.38, gdb 13.2). Of course, developers appreciate that we include the latest tools, but these updates also include improvements to security and performance that will benefit everyone who uses Fedora Linux.</p>
<h2 class="wp-block-heading"><strong>Testing needed</strong></h2>
<p>Since this is a beta release, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora Quality team via the<a href="https://lists.fedoraproject.org/archives/list/test%40lists.fedoraproject.org/"> test mailing list</a> or in the<a href="https://chat.fedoraproject.org/#/room/#quality:fedoraproject.org"> #quality channel on Fedora Chat</a>. As testing progresses, common issues are tracked in the<a href="https://discussion.fedoraproject.org/tags/c/ask/common-issues/82/f39"> “Common Issues” category</a> on Ask Fedora.</p>
<p>For tips on reporting a bug effectively, read<a href="https://docs.fedoraproject.org/en-US/quick-docs/howto-file-a-bug/"> how to file a bug</a>.</p>
<h2 class="wp-block-heading"><strong>What is the beta release?</strong></h2>
<p>A beta release is code-complete and bears a very strong resemblance to the final release. If you take the time to download and try out the beta, you can check and make sure the things that are important to you are working. Every bug you find and report doesn’t just help you, it improves the experience of millions of Fedora Linux users worldwide! Together, we can make Fedora rock-solid. We have a culture of coordinating new features and pushing fixes upstream as much as we can. Your feedback improves not only Fedora Linux, but the Linux ecosystem and free software as a whole.</p>
<h2 class="wp-block-heading"><strong>More information</strong></h2>
<p>For more detailed information about what’s new on the Fedora Linux 39 Beta release, you can consult the<a href="https://fedoraproject.org/wiki/Releases/39/ChangeSet"> Fedora Linux 39 Change set</a>. It contains more technical information about the new packages and improvements shipped with this release.</p>
</div>
https://www.sickgaming.net/blog/2023/09/...x-39-beta/]]>
<div><p>The Fedora Project is pleased to announce the immediate availability of Fedora Linux 39 Beta, the next step towards our planned Fedora Linux 39 release at the end of October.</p>
<p>Get the the prerelease of any of our editions from our project website:</p>
<ul>
<li><a href="https://fedoraproject.org/workstation/download/">Fedora Workstation 39 Beta</a></li>
<li><a href="https://fedoraproject.org/server/download/">Fedora Server 39 Beta</a></li>
<li><a href="https://fedoraproject.org/iot/download/">Fedora IoT 39 Beta</a></li>
<li><a href="https://fedoraproject.org/cloud/download/">Fedora Cloud 39 Beta</a> </li>
<li><a href="https://fedoraproject.org/coreos/download/?stream=next">Fedora CoreOS “next” stream</a></li>
</ul>
<p>Or, try one of our many different desktop variants (like KDE Plasma, Xfce, or Cinnamon) from <a href="https://fedoraproject.org/spins/">Fedora Linux Spins</a>.</p>
<p>You can also update an existing system to the beta using <a href="https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/">DNF system-upgrade</a>.</p>
<h2 class="wp-block-heading"><strong>Beta release highlights</strong></h2>
<p>In some ways, this release might seem notable largely for what isn’t here. We’d planned to update the DNF package manager to a new, speedier version. We also hoped to showcase a long-awaited refresh to the user interface for Anaconda, our installation program. However, we decided these things just weren’t ready in time.</p>
<p>Don’t let this get you down, though — this is a healthy process at work. Years ago, we didn’t always have a good way to alter course once we’d accepted a change proposal. We often found ourselves in a situation where the only reasonable way forward was to forge ahead, even if we weren’t happy enough with the change for general users. Now, even though it’s somewhat disappointing, we’re recognizing that these big changes need more time to bake, and putting them back into the oven is a good thing.</p>
<p>I’ve got a kid that always wants to get 100% (or higher!) in every class. I keep telling her, “Really, you learn best when you’re right 80% of the time. Otherwise, you’re not getting enough of a challenge.” To keep up with Fedora’s commitment to innovation, we also need to take risks. If everything went according to plan, that would mean we’re not trying hard enough. At the same time, our process now allows us to take these risks while still making sure the Fedora Linux OS we ship for general use <em>is</em> of A+ quality.</p>
<p>We still plan to bring you these features in the near future, and if they’re of interest to you, please keep your eyes open for upcoming test announcements.</p>
<p>In the meantime, enjoy the many updates across all of Fedora Linux updates, ready for you to test in this new beta.</p>
<h2 class="wp-block-heading">Notable updates</h2>
<p>Fedora Workstation 39 Beta brings us GNOME 45 (itself also in beta). For everyone who needs a free and open source desktop suite, there’s LibreOffice 7.6.</p>
<p>Fedora Cloud images for AWS now default to less-expensive gp3 storage volumes.</p>
<p>We also have an update to the GNU Toolchain (gcc 13.2, binutils 2.40, glibc 2.38, gdb 13.2). Of course, developers appreciate that we include the latest tools, but these updates also include improvements to security and performance that will benefit everyone who uses Fedora Linux.</p>
<h2 class="wp-block-heading"><strong>Testing needed</strong></h2>
<p>Since this is a beta release, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora Quality team via the<a href="https://lists.fedoraproject.org/archives/list/test%40lists.fedoraproject.org/"> test mailing list</a> or in the<a href="https://chat.fedoraproject.org/#/room/#quality:fedoraproject.org"> #quality channel on Fedora Chat</a>. As testing progresses, common issues are tracked in the<a href="https://discussion.fedoraproject.org/tags/c/ask/common-issues/82/f39"> “Common Issues” category</a> on Ask Fedora.</p>
<p>For tips on reporting a bug effectively, read<a href="https://docs.fedoraproject.org/en-US/quick-docs/howto-file-a-bug/"> how to file a bug</a>.</p>
<h2 class="wp-block-heading"><strong>What is the beta release?</strong></h2>
<p>A beta release is code-complete and bears a very strong resemblance to the final release. If you take the time to download and try out the beta, you can check and make sure the things that are important to you are working. Every bug you find and report doesn’t just help you, it improves the experience of millions of Fedora Linux users worldwide! Together, we can make Fedora rock-solid. We have a culture of coordinating new features and pushing fixes upstream as much as we can. Your feedback improves not only Fedora Linux, but the Linux ecosystem and free software as a whole.</p>
<h2 class="wp-block-heading"><strong>More information</strong></h2>
<p>For more detailed information about what’s new on the Fedora Linux 39 Beta release, you can consult the<a href="https://fedoraproject.org/wiki/Releases/39/ChangeSet"> Fedora Linux 39 Change set</a>. It contains more technical information about the new packages and improvements shipped with this release.</p>
</div>
https://www.sickgaming.net/blog/2023/09/...x-39-beta/]]>
<div><p>Fedora test days are events where anyone can help make certain that changes in Fedora Linux work well in an upcoming release. Fedora community members often participate, and the public is welcome at these events. If you’ve never contributed to Fedora Linux before, this is a perfect way to get started.</p>
<p>There are several test periods in the upcoming weeks.</p>
<ul>
<li><strong>Thursday 21 September and Friday 22 September</strong>, is to test <strong>Passkey Auth</strong>.</li>
<li><strong>Sunday 24 September through Sunday 01 October, </strong>is to test <strong>Fedora IoT Edition</strong>.</li>
<li><strong>Monday 25 September through Monday October 02</strong>, focuses on testing<strong> Fedora CoreOS </strong>.</li>
</ul>
<p> <span id="more-38834"></span> </p>
<h2 class="wp-block-heading">Passkey Auth </h2>
<p>Passwordless authentication methods to log into Linux systems became a hot topic in the past few years. Various organizations started to mandate more secure methods of authentication, including governments and regulated industries. FIDO2 tokens, and smartcards, represent two passwordless authentication methods mandated by the US government in their Zero Trust architecture. </p>
<p>FreeIPA, and SSSD in Fedora 39, enable the capability to log-in to a desktop or a console terminal with a FIDO2-compatible device, for centrally managed users enrolled in Active Directory. This is supported by the libfido2 library. Additionally, for FreeIPA, once the user is authenticated with the FIDO2-compatible device, a Kerberos ticket may be issued . </p>
<p>As a part of this<a href="https://fedoraproject.org/wiki/Changes/Passkey_authentication_centrally_managed_users" target="_blank" rel="noreferrer noopener"> changeset </a>, we will be having <a href="https://fedoraproject.org/wiki/Test_Day:2023-09-21_Passkey_authentication_centrally_managed_users" target="_blank" rel="noreferrer noopener">test days</a> on <strong>Thursday 21 September and Friday 22 September. </strong>The idea is to run through test cases and submit results <a href="https://testdays.fedoraproject.org/events/168" target="_blank" rel="noreferrer noopener">here</a>.</p>
<h2 class="wp-block-heading">Fedora IoT</h2>
<p>For <a href="http://fedoraproject.org/wiki/Test_Day:2023-09-24_Fedora_39_IoT_Edition" target="_blank" rel="noreferrer noopener">this test week</a>, the focus is all-around; test all the bits that come in a Fedora IoT release as well as validate different hardware. This includes:</p>
<ul>
<li>Basic installation to different media</li>
<li>Installing in a VM</li>
<li>rpm-ostree upgrades, layering, rebasing</li>
<li>Basic container manipulation with Podman.</li>
</ul>
<p>We welcome all different types of hardware, but have a specific <a href="https://docs.fedoraproject.org/en-US/iot/reference-platforms/" target="_blank" rel="noreferrer noopener">list of target hardware</a> for convenience. This test week will occur <strong>Sunday 24 September through Sunday 01 October</strong>.</p>
<h2 class="wp-block-heading">Fedora 39 CoreOS Test Week</h2>
<p>The Fedora 39 CoreOS Test Week focuses on testing FCOS based on Fedora 39. The FCOS <strong>next</strong> stream is already rebased on Fedora 38 content, which will be coming soon to <strong>testing</strong> and <strong>stable</strong>. To prepare for the content being promoted to other streams the Fedora CoreOS and QA teams have organized test days from <strong>Monday, 25 </strong><strong>September</strong> <strong>through</strong> <strong> 2 October</strong>. Refer to the <a href="http://fedoraproject.org/wiki/Test_Day:2023-09-24_Fedora_39_IoT_Edition" target="_blank" rel="noreferrer noopener">wiki page</a> for links to the test cases and materials you’ll need to participate. The FCOS and QA team will meet and communicate with the community in async over multiple matrix/element channels. The announcements will be made 48 hours prior to the start of test week. Stay tuned to official Fedora channels for more info.</p>
<h2 class="wp-block-heading">How do test days work?</h2>
<p>Test days or weeks are an event where anyone can help make certain that changes in Fedora work well in an upcoming release. Fedora community members <a href="https://fedoramagazine.org/?s=test+days" target="_blank" rel="noreferrer noopener">often participate</a>, and the public is welcome at these events. Test days are the perfect way to start contributing if you not in the past.</p>
<p>The only requirement to get started is the ability to download test materials (which include some large files) and then read and follow directions step by step.</p>
<p>Detailed information about all the test days are on the wiki page links provided above. If you are available on or around the days of the events, please do some testing and report your results.</p>
</div>
https://www.sickgaming.net/blog/2023/09/...test-week/]]>
<div><p>Fedora test days are events where anyone can help make certain that changes in Fedora Linux work well in an upcoming release. Fedora community members often participate, and the public is welcome at these events. If you’ve never contributed to Fedora Linux before, this is a perfect way to get started.</p>
<p>There are several test periods in the upcoming weeks.</p>
<ul>
<li><strong>Thursday 21 September and Friday 22 September</strong>, is to test <strong>Passkey Auth</strong>.</li>
<li><strong>Sunday 24 September through Sunday 01 October, </strong>is to test <strong>Fedora IoT Edition</strong>.</li>
<li><strong>Monday 25 September through Monday October 02</strong>, focuses on testing<strong> Fedora CoreOS </strong>.</li>
</ul>
<p> <span id="more-38834"></span> </p>
<h2 class="wp-block-heading">Passkey Auth </h2>
<p>Passwordless authentication methods to log into Linux systems became a hot topic in the past few years. Various organizations started to mandate more secure methods of authentication, including governments and regulated industries. FIDO2 tokens, and smartcards, represent two passwordless authentication methods mandated by the US government in their Zero Trust architecture. </p>
<p>FreeIPA, and SSSD in Fedora 39, enable the capability to log-in to a desktop or a console terminal with a FIDO2-compatible device, for centrally managed users enrolled in Active Directory. This is supported by the libfido2 library. Additionally, for FreeIPA, once the user is authenticated with the FIDO2-compatible device, a Kerberos ticket may be issued . </p>
<p>As a part of this<a href="https://fedoraproject.org/wiki/Changes/Passkey_authentication_centrally_managed_users" target="_blank" rel="noreferrer noopener"> changeset </a>, we will be having <a href="https://fedoraproject.org/wiki/Test_Day:2023-09-21_Passkey_authentication_centrally_managed_users" target="_blank" rel="noreferrer noopener">test days</a> on <strong>Thursday 21 September and Friday 22 September. </strong>The idea is to run through test cases and submit results <a href="https://testdays.fedoraproject.org/events/168" target="_blank" rel="noreferrer noopener">here</a>.</p>
<h2 class="wp-block-heading">Fedora IoT</h2>
<p>For <a href="http://fedoraproject.org/wiki/Test_Day:2023-09-24_Fedora_39_IoT_Edition" target="_blank" rel="noreferrer noopener">this test week</a>, the focus is all-around; test all the bits that come in a Fedora IoT release as well as validate different hardware. This includes:</p>
<ul>
<li>Basic installation to different media</li>
<li>Installing in a VM</li>
<li>rpm-ostree upgrades, layering, rebasing</li>
<li>Basic container manipulation with Podman.</li>
</ul>
<p>We welcome all different types of hardware, but have a specific <a href="https://docs.fedoraproject.org/en-US/iot/reference-platforms/" target="_blank" rel="noreferrer noopener">list of target hardware</a> for convenience. This test week will occur <strong>Sunday 24 September through Sunday 01 October</strong>.</p>
<h2 class="wp-block-heading">Fedora 39 CoreOS Test Week</h2>
<p>The Fedora 39 CoreOS Test Week focuses on testing FCOS based on Fedora 39. The FCOS <strong>next</strong> stream is already rebased on Fedora 38 content, which will be coming soon to <strong>testing</strong> and <strong>stable</strong>. To prepare for the content being promoted to other streams the Fedora CoreOS and QA teams have organized test days from <strong>Monday, 25 </strong><strong>September</strong> <strong>through</strong> <strong> 2 October</strong>. Refer to the <a href="http://fedoraproject.org/wiki/Test_Day:2023-09-24_Fedora_39_IoT_Edition" target="_blank" rel="noreferrer noopener">wiki page</a> for links to the test cases and materials you’ll need to participate. The FCOS and QA team will meet and communicate with the community in async over multiple matrix/element channels. The announcements will be made 48 hours prior to the start of test week. Stay tuned to official Fedora channels for more info.</p>
<h2 class="wp-block-heading">How do test days work?</h2>
<p>Test days or weeks are an event where anyone can help make certain that changes in Fedora work well in an upcoming release. Fedora community members <a href="https://fedoramagazine.org/?s=test+days" target="_blank" rel="noreferrer noopener">often participate</a>, and the public is welcome at these events. Test days are the perfect way to start contributing if you not in the past.</p>
<p>The only requirement to get started is the ability to download test materials (which include some large files) and then read and follow directions step by step.</p>
<p>Detailed information about all the test days are on the wiki page links provided above. If you are available on or around the days of the events, please do some testing and report your results.</p>
</div>
https://www.sickgaming.net/blog/2023/09/...test-week/]]>
<div style="margin: 5px 5% 10px 5%;"><img src="https://www.sickgaming.net/blog/wp-content/uploads/2023/09/quick-fedora-shirt-update-and-sale-of-last-stock-with-the-old-logo.png" width="640" height="480" title="" alt="" /></div><div><p>There are some updates on <a href="https://www.hellotux.com/fedora" target="_blank" rel="noreferrer noopener">Fedora shirts and sweatshirts</a>.</p>
<p>Two years after the announcement of the current Fedora logo, we decided to clear our stock of shirts with the old logo. <strong>Soon our shirts will only be made and stocked with the new Fedora logo.</strong></p>
<p> <span id="more-37911"></span> </p>
<p>The Fedora jackets and hoodies are back again:</p>
<figure class="wp-block-image size-large"><a href="https://www.hellotux.com/fedora"><img decoding="async" src="https://www.sickgaming.net/blog/wp-content/uploads/2023/09/quick-fedora-shirt-update-and-sale-of-last-stock-with-the-old-logo.png" alt="" /></a></figure>
<figure class="wp-block-image size-large"><a href="https://www.hellotux.com/fedora"><img decoding="async" src="https://www.sickgaming.net/blog/wp-content/uploads/2023/09/quick-fedora-shirt-update-and-sale-of-last-stock-with-the-old-logo-1.png" alt="" /></a></figure>
<p>The old Fedora polo shirts are almost out of stock, so we have a new type with black buttons:</p>
<figure class="wp-block-image size-large"><a href="https://www.hellotux.com/fedora"><img decoding="async" src="https://www.sickgaming.net/blog/wp-content/uploads/2023/09/quick-fedora-shirt-update-and-sale-of-last-stock-with-the-old-logo.jpg" alt="" /></a></figure>
<p>We have improved delivery too. No more taxes and customs paperwork within the European Union, the United States and the United Kingdom.<br />If you have your own embroidery machine, the PES file for the Fedora embroidery is available <a href="https://www.hellotux.com/pub/fedora/fedora.pes" target="_blank" rel="noreferrer noopener">here</a>; for the Fedora Classic, <a href="https://www.hellotux.com/pub/fedora/fedora_classic.pes" target="_blank" rel="noreferrer noopener">here</a>.</p>
<p>Check out the<strong> <a href="https://www.hellotux.com/fedora">embroidered Fedora collection here</a></strong> and don’t forget to use the <strong>FEDORA5</strong> coupon code, for the <strong>$5 discount</strong> on every Fedora shirt and sweatshirt.</p>
<p>When ordering, note that the old logo style items are labelled “Fedora Classic”.</p>
</div>
https://www.sickgaming.net/blog/2023/09/...-old-logo/]]>
<div style="margin: 5px 5% 10px 5%;"><img src="https://www.sickgaming.net/blog/wp-content/uploads/2023/09/quick-fedora-shirt-update-and-sale-of-last-stock-with-the-old-logo.png" width="640" height="480" title="" alt="" /></div><div><p>There are some updates on <a href="https://www.hellotux.com/fedora" target="_blank" rel="noreferrer noopener">Fedora shirts and sweatshirts</a>.</p>
<p>Two years after the announcement of the current Fedora logo, we decided to clear our stock of shirts with the old logo. <strong>Soon our shirts will only be made and stocked with the new Fedora logo.</strong></p>
<p> <span id="more-37911"></span> </p>
<p>The Fedora jackets and hoodies are back again:</p>
<figure class="wp-block-image size-large"><a href="https://www.hellotux.com/fedora"><img decoding="async" src="https://www.sickgaming.net/blog/wp-content/uploads/2023/09/quick-fedora-shirt-update-and-sale-of-last-stock-with-the-old-logo.png" alt="" /></a></figure>
<figure class="wp-block-image size-large"><a href="https://www.hellotux.com/fedora"><img decoding="async" src="https://www.sickgaming.net/blog/wp-content/uploads/2023/09/quick-fedora-shirt-update-and-sale-of-last-stock-with-the-old-logo-1.png" alt="" /></a></figure>
<p>The old Fedora polo shirts are almost out of stock, so we have a new type with black buttons:</p>
<figure class="wp-block-image size-large"><a href="https://www.hellotux.com/fedora"><img decoding="async" src="https://www.sickgaming.net/blog/wp-content/uploads/2023/09/quick-fedora-shirt-update-and-sale-of-last-stock-with-the-old-logo.jpg" alt="" /></a></figure>
<p>We have improved delivery too. No more taxes and customs paperwork within the European Union, the United States and the United Kingdom.<br />If you have your own embroidery machine, the PES file for the Fedora embroidery is available <a href="https://www.hellotux.com/pub/fedora/fedora.pes" target="_blank" rel="noreferrer noopener">here</a>; for the Fedora Classic, <a href="https://www.hellotux.com/pub/fedora/fedora_classic.pes" target="_blank" rel="noreferrer noopener">here</a>.</p>
<p>Check out the<strong> <a href="https://www.hellotux.com/fedora">embroidered Fedora collection here</a></strong> and don’t forget to use the <strong>FEDORA5</strong> coupon code, for the <strong>$5 discount</strong> on every Fedora shirt and sweatshirt.</p>
<p>When ordering, note that the old logo style items are labelled “Fedora Classic”.</p>
</div>
https://www.sickgaming.net/blog/2023/09/...-old-logo/]]>
<div><p>Fedora test days are events where anyone can help make sure changes in Fedora Linux work well in an upcoming release. Fedora community members often participate, and the public is welcome at these events. If you’ve never contributed to Fedora Linux before, this is a perfect way to get started.</p>
<p>There are several test periods in the upcoming weeks. Here are the first two:</p>
<ul>
<li><strong>Sunday 10 Sept through Sunday 17 Sept </strong>, is to test <strong>Kernel 6.5</strong>.</li>
<li><strong>Thursday 14 Sept</strong> focuses on testing<strong> Toolbx</strong> .</li>
</ul>
<p> <span id="more-38818"></span> </p>
<h2 class="wp-block-heading">Kernel 6.5</h2>
<p>The kernel team is working on final integration for Linux kernel 6.5. This recently released version, will arrive soon in Fedora Linux. As a result, the Fedora Linux kernel and QA teams have organized a test week from Sunday, Sept 10, 2023 to Sunday, Sept 17, 2023. This <a href="http://fedoraproject.org/wiki/Test_Day:2023-09-10_Kernel_6.5_Test_Week" target="_blank" rel="noreferrer noopener">wiki page</a> contains links to the test images you’ll need to participate. This is also going to be the release Kernel for Fedora 39 and any help testing regression for this Kernel will be very helpful. </p>
<h2 class="wp-block-heading">Toolbx</h2>
<p>Recently, <a href="https://fedoraproject.org/wiki/Changes/ToolbxReleaseBlocker">Toolbx has been made a release-blocking deliverable and now has release-blocking test criteria</a>. Given <a href="https://containertoolbx.org/" target="_blank" rel="noreferrer noopener">Toolbx</a> is very popular and has a variety of usage, we would like to run a test day to ensure nothing is broken. This test day encourages people to use containers, run apps in them ; across all platforms ie <br />Workstation , KDE , Silverblue and CoreOS. The details are available on <a href="https://fedoraproject.org/wiki/Changes/ToolbxReleaseBlocker" target="_blank" rel="noreferrer noopener">this wiki </a>and results can be submitted in the <a href="https://testdays.fedoraproject.org/events/167">events page</a>. </p>
<h2 class="wp-block-heading">How do test days work?</h2>
<p>A test day is an event where anyone can help make sure changes in Fedora Linux work well in an upcoming release. Fedora community members often participate, and the public is welcome at these events. If you’ve never contributed before, this is a perfect way to get started.</p>
<p>To contribute, you only need to be able to download test materials (which include some large files) and then read and follow directions step by step.</p>
<p>Detailed information about all the test days is available on the wiki pages mentioned above. If you’re available on or around the days of the events, please do some testing and report your results. All the test day pages receive some final touches which complete about 24 hrs before the test day begins. We urge you to be patient about resources that are, in most cases, uploaded hours before the test day starts.</p>
<p>Come and test with us to make the upcoming Fedora Linux 39 even better.</p>
</div>
https://www.sickgaming.net/blog/2023/09/...-test-day/]]>
<div><p>Fedora test days are events where anyone can help make sure changes in Fedora Linux work well in an upcoming release. Fedora community members often participate, and the public is welcome at these events. If you’ve never contributed to Fedora Linux before, this is a perfect way to get started.</p>
<p>There are several test periods in the upcoming weeks. Here are the first two:</p>
<ul>
<li><strong>Sunday 10 Sept through Sunday 17 Sept </strong>, is to test <strong>Kernel 6.5</strong>.</li>
<li><strong>Thursday 14 Sept</strong> focuses on testing<strong> Toolbx</strong> .</li>
</ul>
<p> <span id="more-38818"></span> </p>
<h2 class="wp-block-heading">Kernel 6.5</h2>
<p>The kernel team is working on final integration for Linux kernel 6.5. This recently released version, will arrive soon in Fedora Linux. As a result, the Fedora Linux kernel and QA teams have organized a test week from Sunday, Sept 10, 2023 to Sunday, Sept 17, 2023. This <a href="http://fedoraproject.org/wiki/Test_Day:2023-09-10_Kernel_6.5_Test_Week" target="_blank" rel="noreferrer noopener">wiki page</a> contains links to the test images you’ll need to participate. This is also going to be the release Kernel for Fedora 39 and any help testing regression for this Kernel will be very helpful. </p>
<h2 class="wp-block-heading">Toolbx</h2>
<p>Recently, <a href="https://fedoraproject.org/wiki/Changes/ToolbxReleaseBlocker">Toolbx has been made a release-blocking deliverable and now has release-blocking test criteria</a>. Given <a href="https://containertoolbx.org/" target="_blank" rel="noreferrer noopener">Toolbx</a> is very popular and has a variety of usage, we would like to run a test day to ensure nothing is broken. This test day encourages people to use containers, run apps in them ; across all platforms ie <br />Workstation , KDE , Silverblue and CoreOS. The details are available on <a href="https://fedoraproject.org/wiki/Changes/ToolbxReleaseBlocker" target="_blank" rel="noreferrer noopener">this wiki </a>and results can be submitted in the <a href="https://testdays.fedoraproject.org/events/167">events page</a>. </p>
<h2 class="wp-block-heading">How do test days work?</h2>
<p>A test day is an event where anyone can help make sure changes in Fedora Linux work well in an upcoming release. Fedora community members often participate, and the public is welcome at these events. If you’ve never contributed before, this is a perfect way to get started.</p>
<p>To contribute, you only need to be able to download test materials (which include some large files) and then read and follow directions step by step.</p>
<p>Detailed information about all the test days is available on the wiki pages mentioned above. If you’re available on or around the days of the events, please do some testing and report your results. All the test day pages receive some final touches which complete about 24 hrs before the test day begins. We urge you to be patient about resources that are, in most cases, uploaded hours before the test day starts.</p>
<p>Come and test with us to make the upcoming Fedora Linux 39 even better.</p>
</div>
https://www.sickgaming.net/blog/2023/09/...-test-day/]]>
<div><div class="lcom-stacked__main">
<div class="panel-pane pane-entity-field pane-node-body">
<div class="field field-name-body field-type-text-with-summary field-label-hidden">
<div class="field-items">
<div class="field-item even">
<p>VMware today confirmed that it is in talks to acquire software development platform Pivotal Software, the service best known for commercializing the open-source Cloud Foundry platform. The proposed transaction would see VMware acquire all outstanding Pivotal Class A stock for $15 per share, a significant markup over Pivotal’s current share price (which unsurprisingly shot up right after the announcement). (Source: <a href="https://www.tfir.io/2019/08/14/vmware-all-set-to-acquire-pivotal/">TFiR</a>)</p>
</div>
</div>
</div></div>
</p></div>
<p><a href="https://www.linux.com/popup/nojs" class="ctools-use-modal ctools-modal-subscription-modal-style element-invisible" title>Click Here!</a> </p>
</div>
https://www.sickgaming.net/blog/2019/08/...e-pivotal/]]>
<div><div class="lcom-stacked__main">
<div class="panel-pane pane-entity-field pane-node-body">
<div class="field field-name-body field-type-text-with-summary field-label-hidden">
<div class="field-items">
<div class="field-item even">
<p>VMware today confirmed that it is in talks to acquire software development platform Pivotal Software, the service best known for commercializing the open-source Cloud Foundry platform. The proposed transaction would see VMware acquire all outstanding Pivotal Class A stock for $15 per share, a significant markup over Pivotal’s current share price (which unsurprisingly shot up right after the announcement). (Source: <a href="https://www.tfir.io/2019/08/14/vmware-all-set-to-acquire-pivotal/">TFiR</a>)</p>
</div>
</div>
</div></div>
</p></div>
<p><a href="https://www.linux.com/popup/nojs" class="ctools-use-modal ctools-modal-subscription-modal-style element-invisible" title>Click Here!</a> </p>
</div>
https://www.sickgaming.net/blog/2019/08/...e-pivotal/]]>
<div><p>This article introduces projects available in Flathub with installation instructions.</p>
<p><a href="https://flathub.org" target="_blank" rel="noreferrer noopener">Flathub</a> is the place to get and distribute apps for all of Linux. It is powered by Flatpak, allowing Flathub apps to run on almost any Linux distribution.</p>
<p>Please read “<a href="https://fedoramagazine.org/getting-started-flatpak/" target="_blank" rel="noreferrer noopener">Getting started with Flatpak</a>“. In order to enable flathub as your flatpak provider, use the instructions on the <a href="https://flatpak.org/setup/Fedora" target="_blank" rel="noreferrer noopener">flatpak site</a>.</p>
<p> <span id="more-38610"></span> </p>
<h2 class="wp-block-heading">Flatseal</h2>
<p><a href="https://flathub.org/apps/com.github.tchx84.Flatseal" target="_blank" rel="noreferrer noopener">Flatseal</a> is a graphical utility to review and modify permissions from your Flatpak applications. This is one of the most used apps in the flatpak world, it allows you to improve security on flatpak applications. However, it needs to be used with caution because you can make your permissions be too open.</p>
<p>It’s very simple to use: Simply launch Flatseal, select an application, and modify its permissions. Restart the application after making the changes. If anything goes wrong just press the reset button.</p>
<p>You can install “Flatseal” by clicking the install button on the web site or manually using this command:</p>
<pre class="wp-block-preformatted">flatpak install flathub com.github.tchx84.Flatseal</pre>
<p><strong><em>Also available as rpm on fedora’s repositories</em></strong></p>
<h2 class="wp-block-heading">Reco</h2>
<p><a href="https://flathub.org/apps/com.github.ryonakano.reco" target="_blank" rel="noreferrer noopener">Reco</a> is an audio recording app that helps you recall and listen to things you listened to earlier.</p>
<p>Some of the features include:</p>
<ul>
<li>Recording sounds from both your microphone and system at the same time.</li>
<li>Support formats like ALAC, FLAC, MP3, Ogg Vorbis, Opus, and WAV</li>
<li>Timed recording.</li>
<li>Autosaving or always-ask-where-to-save workflow.</li>
<li>Saving recording when the app quits.</li>
</ul>
<p>I used it a lot to help me record interviews for the <a href="https://fedoraproject.org/podcast/" target="_blank" rel="noreferrer noopener">Fedora Podcast</a></p>
<p>You can install “Reco” by clicking the install button on the web site or manually using this command:</p>
<pre class="wp-block-preformatted">flatpak install flathub com.github.ryonakano.reco</pre>
<h2 class="wp-block-heading">Mini Text</h2>
<p><a href="https://flathub.org/apps/io.github.nokse22.minitext" target="_blank" rel="noreferrer noopener">Mini Text</a> is a very small and minimalistic text viewer with minimal editing capabilities. It’s meant as a place to edit text to be pasted, it doesn’t have saving capabilities. It uses GTK4 and it’s interface integrates nicely with GNOME.</p>
<p>I found this to be very useful just to keep data that I want to paste anywhere, it doesn’t have unwanted and/or unneeded rich text capabilities, just plain text with minimal editing features.</p>
<p>You can install “Mini Text” by clicking the install button on the web site or manually using this command:</p>
<pre class="wp-block-preformatted">flatpak install flathub io.github.nokse22.minitext</pre>
<h2 class="wp-block-heading">Tagger</h2>
<p><a href="https://flathub.org/apps/org.nickvision.tagger" target="_blank" rel="noreferrer noopener">Tagger</a> is a tag editor for those of us that still save the music locally.</p>
<p>Some of the features are:</p>
<ul>
<li>Edit tags and album art of multiple files, even across subfolders, all at once</li>
<li>Support for multiple music file types (mp3, ogg, flac, wma, and wav)</li>
<li>Convert filenames to tags and tags to filenames with ease</li>
</ul>
<p>You can install “Tagger” by clicking the install button on the web site or manually using this command:</p>
<pre class="wp-block-preformatted">flatpak install flathub org.nickvision.tagger</pre>
</div>
https://www.sickgaming.net/blog/2023/09/...september/]]>
<div><p>This article introduces projects available in Flathub with installation instructions.</p>
<p><a href="https://flathub.org" target="_blank" rel="noreferrer noopener">Flathub</a> is the place to get and distribute apps for all of Linux. It is powered by Flatpak, allowing Flathub apps to run on almost any Linux distribution.</p>
<p>Please read “<a href="https://fedoramagazine.org/getting-started-flatpak/" target="_blank" rel="noreferrer noopener">Getting started with Flatpak</a>“. In order to enable flathub as your flatpak provider, use the instructions on the <a href="https://flatpak.org/setup/Fedora" target="_blank" rel="noreferrer noopener">flatpak site</a>.</p>
<p> <span id="more-38610"></span> </p>
<h2 class="wp-block-heading">Flatseal</h2>
<p><a href="https://flathub.org/apps/com.github.tchx84.Flatseal" target="_blank" rel="noreferrer noopener">Flatseal</a> is a graphical utility to review and modify permissions from your Flatpak applications. This is one of the most used apps in the flatpak world, it allows you to improve security on flatpak applications. However, it needs to be used with caution because you can make your permissions be too open.</p>
<p>It’s very simple to use: Simply launch Flatseal, select an application, and modify its permissions. Restart the application after making the changes. If anything goes wrong just press the reset button.</p>
<p>You can install “Flatseal” by clicking the install button on the web site or manually using this command:</p>
<pre class="wp-block-preformatted">flatpak install flathub com.github.tchx84.Flatseal</pre>
<p><strong><em>Also available as rpm on fedora’s repositories</em></strong></p>
<h2 class="wp-block-heading">Reco</h2>
<p><a href="https://flathub.org/apps/com.github.ryonakano.reco" target="_blank" rel="noreferrer noopener">Reco</a> is an audio recording app that helps you recall and listen to things you listened to earlier.</p>
<p>Some of the features include:</p>
<ul>
<li>Recording sounds from both your microphone and system at the same time.</li>
<li>Support formats like ALAC, FLAC, MP3, Ogg Vorbis, Opus, and WAV</li>
<li>Timed recording.</li>
<li>Autosaving or always-ask-where-to-save workflow.</li>
<li>Saving recording when the app quits.</li>
</ul>
<p>I used it a lot to help me record interviews for the <a href="https://fedoraproject.org/podcast/" target="_blank" rel="noreferrer noopener">Fedora Podcast</a></p>
<p>You can install “Reco” by clicking the install button on the web site or manually using this command:</p>
<pre class="wp-block-preformatted">flatpak install flathub com.github.ryonakano.reco</pre>
<h2 class="wp-block-heading">Mini Text</h2>
<p><a href="https://flathub.org/apps/io.github.nokse22.minitext" target="_blank" rel="noreferrer noopener">Mini Text</a> is a very small and minimalistic text viewer with minimal editing capabilities. It’s meant as a place to edit text to be pasted, it doesn’t have saving capabilities. It uses GTK4 and it’s interface integrates nicely with GNOME.</p>
<p>I found this to be very useful just to keep data that I want to paste anywhere, it doesn’t have unwanted and/or unneeded rich text capabilities, just plain text with minimal editing features.</p>
<p>You can install “Mini Text” by clicking the install button on the web site or manually using this command:</p>
<pre class="wp-block-preformatted">flatpak install flathub io.github.nokse22.minitext</pre>
<h2 class="wp-block-heading">Tagger</h2>
<p><a href="https://flathub.org/apps/org.nickvision.tagger" target="_blank" rel="noreferrer noopener">Tagger</a> is a tag editor for those of us that still save the music locally.</p>
<p>Some of the features are:</p>
<ul>
<li>Edit tags and album art of multiple files, even across subfolders, all at once</li>
<li>Support for multiple music file types (mp3, ogg, flac, wma, and wav)</li>
<li>Convert filenames to tags and tags to filenames with ease</li>
</ul>
<p>You can install “Tagger” by clicking the install button on the web site or manually using this command:</p>
<pre class="wp-block-preformatted">flatpak install flathub org.nickvision.tagger</pre>
</div>
https://www.sickgaming.net/blog/2023/09/...september/]]>
<div><div class="lcom-stacked__main">
<div class="panel-pane pane-entity-field pane-node-body">
<div class="field field-name-body field-type-text-with-summary field-label-hidden">
<div class="field-items">
<div class="field-item even">
<p>The Cloud Native Computing Foundation (CNCF), which sustains and integrates open source technologies like Kubernetes and Prometheus, today announced that its End User Community has grown to 100 members. The CNCF End User Community consists of enterprises and startups that are committed to accelerating the adoption of cloud native technologies and improving the deployment experience. (<a href="https://finance.yahoo.com/news/cloud-native-computing-foundation-reaches-100-end-user-160000884.html">Yahoo</a>!)</p>
</div>
</div>
</div></div>
</p></div>
<p><a href="https://www.linux.com/popup/nojs" class="ctools-use-modal ctools-modal-subscription-modal-style element-invisible" title>Click Here!</a> </p>
</div>
https://www.sickgaming.net/blog/2019/08/...y-members/]]>
<div><div class="lcom-stacked__main">
<div class="panel-pane pane-entity-field pane-node-body">
<div class="field field-name-body field-type-text-with-summary field-label-hidden">
<div class="field-items">
<div class="field-item even">
<p>The Cloud Native Computing Foundation (CNCF), which sustains and integrates open source technologies like Kubernetes and Prometheus, today announced that its End User Community has grown to 100 members. The CNCF End User Community consists of enterprises and startups that are committed to accelerating the adoption of cloud native technologies and improving the deployment experience. (<a href="https://finance.yahoo.com/news/cloud-native-computing-foundation-reaches-100-end-user-160000884.html">Yahoo</a>!)</p>
</div>
</div>
</div></div>
</p></div>
<p><a href="https://www.linux.com/popup/nojs" class="ctools-use-modal ctools-modal-subscription-modal-style element-invisible" title>Click Here!</a> </p>
</div>
https://www.sickgaming.net/blog/2019/08/...y-members/]]>
<div><p>The Workstation team is working on the final integration of <a href="https://fedoramagazine.org/anaconda-web-ui-storage-feedback-requested/">Anaconda WebUI Installer</a> for Fedora Linux Workstation. As a result, the Fedora Workstation Working Group and QA teams have organized a test week from Monday, Aug 28, 2023 to Monday, Sept 04, 2023. The wiki page in this article contains links to the test images you’ll need to participate. Please continue reading for details.</p>
<p> <span id="more-38780"></span> </p>
<h2 class="wp-block-heading"><strong>How does a test week work?</strong></h2>
<p>A test week is an event where anyone can help ensure changes in Fedora Linux work well in an upcoming release. Fedora community members often participate, and the public is welcome at these events. If you’ve never contributed before, this is a perfect way to get started.</p>
<p>To contribute, you only need to be able to do the following things:</p>
<ul>
<li>Download test materials, which include some large files</li>
<li>Read and follow directions step by step</li>
</ul>
<p>The <a href="https://fedoraproject.org/wiki/Test_Day:2023-08-28_Anaconda_Web_UI">wiki page</a> for the Anaconda WebUI test week has a lot of good information on what and how to test. After you’ve done some testing, you can log your results in the <a href="https://testdays.fedoraproject.org/events/165" target="_blank" rel="noreferrer noopener">test day web application</a>. If you’re available on or around the days of the event, please do some testing and report your results. We have <a href="https://docs.fedoraproject.org/en-US/quick-docs/kernel/howto-kernel-testday/" target="_blank" rel="noreferrer noopener">a document which provides all the necessary steps</a>.</p>
</div>
https://www.sickgaming.net/blog/2023/08/...rkstation/]]>
<div><p>The Workstation team is working on the final integration of <a href="https://fedoramagazine.org/anaconda-web-ui-storage-feedback-requested/">Anaconda WebUI Installer</a> for Fedora Linux Workstation. As a result, the Fedora Workstation Working Group and QA teams have organized a test week from Monday, Aug 28, 2023 to Monday, Sept 04, 2023. The wiki page in this article contains links to the test images you’ll need to participate. Please continue reading for details.</p>
<p> <span id="more-38780"></span> </p>
<h2 class="wp-block-heading"><strong>How does a test week work?</strong></h2>
<p>A test week is an event where anyone can help ensure changes in Fedora Linux work well in an upcoming release. Fedora community members often participate, and the public is welcome at these events. If you’ve never contributed before, this is a perfect way to get started.</p>
<p>To contribute, you only need to be able to do the following things:</p>
<ul>
<li>Download test materials, which include some large files</li>
<li>Read and follow directions step by step</li>
</ul>
<p>The <a href="https://fedoraproject.org/wiki/Test_Day:2023-08-28_Anaconda_Web_UI">wiki page</a> for the Anaconda WebUI test week has a lot of good information on what and how to test. After you’ve done some testing, you can log your results in the <a href="https://testdays.fedoraproject.org/events/165" target="_blank" rel="noreferrer noopener">test day web application</a>. If you’re available on or around the days of the event, please do some testing and report your results. We have <a href="https://docs.fedoraproject.org/en-US/quick-docs/kernel/howto-kernel-testday/" target="_blank" rel="noreferrer noopener">a document which provides all the necessary steps</a>.</p>
</div>
https://www.sickgaming.net/blog/2023/08/...rkstation/]]>
<div><div class="lcom-stacked__main">
<div class="panel-pane pane-entity-field pane-node-body">
<div class="field field-name-body field-type-text-with-summary field-label-hidden">
<div class="field-items">
<div class="field-item even">
<p>rideOS, a technology platform designed to accelerate the safe, global rollout of next-generation transportation fleets, today launched its new Ridehail Platform — including a Ridehail API and open-source mobile apps. The Ridehail API offers an easy way for automotive original equipment manufacturers (OEMs), autonomous vehicle (AV) companies, and transportation network companies (TNCs) to create and manage their own ridehailing network using rideOS’ underlying technology. (<a href="https://finance.yahoo.com/news/rideos-launches-devoted-platform-power-150000522.html">Yahoo</a>!)</p>
</div>
</div>
</div></div>
</p></div>
<p><a href="https://www.linux.com/popup/nojs" class="ctools-use-modal ctools-modal-subscription-modal-style element-invisible" title>Click Here!</a> </p>
</div>
https://www.sickgaming.net/blog/2019/08/...-platform/]]>
<div><div class="lcom-stacked__main">
<div class="panel-pane pane-entity-field pane-node-body">
<div class="field field-name-body field-type-text-with-summary field-label-hidden">
<div class="field-items">
<div class="field-item even">
<p>rideOS, a technology platform designed to accelerate the safe, global rollout of next-generation transportation fleets, today launched its new Ridehail Platform — including a Ridehail API and open-source mobile apps. The Ridehail API offers an easy way for automotive original equipment manufacturers (OEMs), autonomous vehicle (AV) companies, and transportation network companies (TNCs) to create and manage their own ridehailing network using rideOS’ underlying technology. (<a href="https://finance.yahoo.com/news/rideos-launches-devoted-platform-power-150000522.html">Yahoo</a>!)</p>
</div>
</div>
</div></div>
</p></div>
<p><a href="https://www.linux.com/popup/nojs" class="ctools-use-modal ctools-modal-subscription-modal-style element-invisible" title>Click Here!</a> </p>
</div>
https://www.sickgaming.net/blog/2019/08/...-platform/]]>