Selfhosted OneShotLido • 9 months ago • 90%

Simply put, I can't get Audiobookshelf to respond to any port other than 80. I'm using the following Docker Compose (spacing may be off because I suck at formatting posts): >version: "3.7" >services: > audiobookshelf: > image: ghcr.io/advplyr/audiobookshelf:latest > network_mode: "host" > ports: > - 13378:80 > restart: unless-stopped > volumes: > - /media/Vault/ABS/audiobooks:/audiobooks > - /media/Vault/ABS/podcasts:/podcasts > - /media/Vault/ABS/config:/config > - /media/Vault/ABS/metadata:/metadata The way I understand it, externally the host should answer on port 13378 and the container on port 80. Just for kicks, I've tried the following variations: - 13378:80 - 80:13378 - 13378:13378 I've even tried it without the version statement. Regardless of these, Audiobookshelf will only answer on port 80. All my other containers work fine and answer on the port I designate. I do not have anything else listening on port 13378. What am I doing wrong?

Ereader OneShotLido • 9 months ago • 87%

I have a Kindle which has a 6.8 inch screen. I've been wanting to pick up another ereader, but I don't want a smaller screen. I'd prefer a 7 inch screen, since that seems to be closest to the Kindle. I've been looking at Boox and Kobo readers, but all their 7 inch screens have hardware buttons rather than touch. I have not found a 7 inch screen with touch. Does anyone have a recommendation, or am I stuck with hardware buttons?

Linux OneShotLido • 9 months ago • 92%

Apologies if this isn't the correct forum. A couple of days back, maybe a week, someone made a post asking if a certain pre-built SFF PC would run Linux. Several people responded that they run that same PC and that it works great. I'm planning to build a PC for my mother and this would be perfect for her needs. However, I can't find the post and I can't find anything relevant in my browser history. If anyone knows the post I'm talking about, please let me know. Thanks!