OneShotLido

joined 1 year ago
[–] OneShotLido@lemmy.world 34 points 9 months ago (2 children)

Yet another reason to justify lower wages. This is right up there with "unskilled labor".

[–] OneShotLido@lemmy.world 1 points 9 months ago

This entire comment rings true to me. Get out of my head.

[–] OneShotLido@lemmy.world 6 points 9 months ago

This is such a great point that your voice gets heard. When I read that, it finally clicked with me. When I click through, it's rare that I don't read every comment. On Reddit, I rarely did because there were so many comments. Here, I'm usually reading them all. Your voice is being heard. Nice.

[–] OneShotLido@lemmy.world 2 points 9 months ago

Excellent, my friend. Thanks!

[–] OneShotLido@lemmy.world 3 points 9 months ago

Perfect. Thanks!

 

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?

[–] OneShotLido@lemmy.world 2 points 9 months ago

Thanks. I'll look into this.

[–] OneShotLido@lemmy.world 1 points 9 months ago (1 children)

Ok, very cool. I guess I should simply contact them and ask. Thanks!

 

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?

[–] OneShotLido@lemmy.world 8 points 9 months ago (4 children)

And immediately after posting, I found the link. Sorry for the bother!

 

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!

[–] OneShotLido@lemmy.world 6 points 9 months ago

You need to shake your memory box. It's broken.

[–] OneShotLido@lemmy.world 5 points 9 months ago

I've been away from Linux for about a decade. Currently setting up Docker, and struggling with subuid and subgid. I'll get there eventually, but man, this shit has really changed since I've been gone. Loving the challenge though.

view more: next ›