Show HN: Spodcast, a Spotify podcast to RSS proxy
github.com123 pointsby Ourgon37 comments
00:00.0 Host bridge: NVIDIA Corporation MCP79 Host Bridge (rev b1)
00:00.1 RAM memory: NVIDIA Corporation MCP79 Memory Controller (rev b1)
00:03.0 ISA bridge: NVIDIA Corporation MCP79 LPC Bridge (rev b3)
00:03.1 RAM memory: NVIDIA Corporation MCP79 Memory Controller (rev b1)
00:03.2 SMBus: NVIDIA Corporation MCP79 SMBus (rev b1)
00:03.3 RAM memory: NVIDIA Corporation MCP79 Memory Controller (rev b1)
00:03.4 RAM memory: NVIDIA Corporation MCP79 Memory Controller (rev b1)
00:03.5 Co-processor: NVIDIA Corporation MCP79 Co-processor (rev b1)
00:04.0 USB controller: NVIDIA Corporation MCP79 OHCI USB 1.1 Controller (rev b1)
00:04.1 USB controller: NVIDIA Corporation MCP79 EHCI USB 2.0 Controller (rev b1)
00:06.0 USB controller: NVIDIA Corporation MCP79 OHCI USB 1.1 Controller (rev b1)
00:06.1 USB controller: NVIDIA Corporation MCP79 EHCI USB 2.0 Controller (rev b1)
00:08.0 Audio device: NVIDIA Corporation MCP79 High Definition Audio (rev b1)
00:09.0 PCI bridge: NVIDIA Corporation MCP79 PCI Bridge (rev b1)
00:0a.0 Ethernet controller: NVIDIA Corporation MCP79 Ethernet (rev b1)
00:0b.0 SATA controller: NVIDIA Corporation MCP79 AHCI Controller (rev b1)
00:0c.0 PCI bridge: NVIDIA Corporation MCP79 PCI Express Bridge (rev b1)
00:15.0 PCI bridge: NVIDIA Corporation MCP79 PCI Express Bridge (rev b1)
00:16.0 PCI bridge: NVIDIA Corporation MCP79 PCI Express Bridge (rev b1)
02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96-XT [Mobility Radeon HD 4670]
02:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] RV710/730 HDMI Audio [Radeon HD 4000 series]
03:00.0 Network controller: Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express) (rev 01)
04:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express] (rev 01)
05:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] (rev 01)
There is some Broadcom as well - the Bluetooth controller, which works fine - as well as some Qualcomm - the wifi controller which, again, works fine. #!/bin/sh
export WINEARCH=win32
export WINEPREFIX=/home/username/.wine-sketchup
export WINE=$(which wine)
export sketchup_msi=/home/username/Downloads/SketchUp2016-x86.msi
export gecko_msi=/home/username/Downloads/wine_gecko-2.40-x86.msi
export vblank_mode=0
export DRI_PRIME=1
help () {
echo <<-END
use: $0 [-r] [-h]
-r: reset sketchup (does a complete reinstall)
-h: this help message
END
}
sketchup_reset () {
rm -rf $WINEPREFIX
winetricks win7
winetricks corefonts
winetricks vcrun2010
winetricks dotnet40
msiexec /i $gecko_msi
winetricks win7
msiexec /i $sketchup_msi
}
config () {
winecfg
}
while getopts "chr" OPTION
do
case $OPTION in
r)
sketchup_reset
;;
c)
config
exit
;;
h)
help
exit
;;
esac
done
$WINE "$WINEPREFIX/drive_c/Program Files/SketchUp/SketchUp 2016/SketchUp.exe"
- Proxmox to run all mentioned services
- Software router to bind them all together (OpenWRT in a container)
- Database services (Postgresql, Mysql, Redis) used for many of the mentioned services
- Backup services (rsnapshot, custom backup scripts)
- mail services (Exim, Dovecot, Spamassassin, greylistd, dovecot-managesieve)
- web-related things (first Apache, then lighttpd, then nginx) running:
- "Cloud" (first Owncloud, then Nextcloud) with functional equivalents of e.g. Google Docs (Nextcloud Office), Google Reader (Nextcloud News), Google Meet (Nextcloud Talk, Jitsi Meet), Gmail (Rainloop app in Nextcloud, Roundcube), Google Maps (OSM app in Nextcloud), Calendar etc.
- Wiki (first Twiki, then Mediawiki, now Bookstack)
- Media (mpd, Airsonic, Jellyfin, Peertube, Pixelfed)
- version control (first CVS, then Subversion, then Gogs, then Gitea)
- Search (Searx and Recoll)
- big-tech proxies (Invidious, Nitter, libreddit, Spodcast, searx (see Search))
- Video surveillance (Zoneminder)
- Remote application/desktop service (X2go, NoVNC, now experimenting with Kasm)
- P2P services (Transmission, IPFS, MLDonkey (when needed))
- "Chat" services (first Prosody, then ejabberd, then back to Prosody)
- Timelimit service + app on my daughter's phone to keep her screen time in check, I can remotely give her more time when required
- a "stable" and "development" build server (Debian running in containers)
- ...and a lot more
Basic services are divided over a few containers - base, mail, auth. Most services run on a single container - serve. Some get their own container because they are only started irregularly (bookcook, the bookkeeping service) or they should be separated from the rest - p2p, session (remote application/desktop services). I tend to shun docker, preferring to tailor services to my own needs. Currently the only services using docker are Kasm Workspaces [1] and some linuxserver.io instances which I'm experimenting with.
[1] ...with the database (postgresql) and cache (redis) services being redirected to the 'base' container which runs all database services