Star Trek
r/startrek: The Next Generation
Star Trek news and discussion. No slash fic...
Maybe a little slash fic.
New to Star Trek and wondering where to start?
Rules
1 Be constructive
All posts/comments must be thoughtful and balanced.
2 Be welcoming
It is important that everyone from newbies to OG Trekkers feel welcome, no matter their gender, sexual orientation, religion or race.
3 Be truthful
All posts/comments must be factually accurate and verifiable. We are not a place for gossip, rumors, or manipulative or misleading content.
4 Be nice
If a polite way cannot be found to phrase what it is you want to say, don't say anything at all. Insulting or disparaging remarks about any human being are expressly not allowed.
5 Spoilers
Utilize the spoiler system for any and all spoilers relating to the most recently-aired episodes, as well as previews for upcoming episodes. There is no formal spoiler protection for episodes/films after they have been available for approximately one week.
6 Keep on-topic
All submissions must be directly about the Star Trek franchise (the shows, movies, books etc.). Off-topic discussions are welcome at c/quarks.
7 Meta
Questions and concerns about moderator actions should be brought forward via DM.
Upcoming Episodes
| Date | Episode | Title |
|---|---|---|
| 11-28 | LD 5x07 | "Fully Dilated" |
| 12-05 | LD 5x08 | "Upper Decks" |
| 12-12 | LD 5x09 | "Fissue Quest" |
| 12-19 | LD 5x10 | "The New Next Generation" |
| 01-24 | Film | "Section 31" |
In Production
Strange New Worlds (2025)
Section 31 (2025-01-24)
Starfleet Academy (TBA)
In Development
Untitled comedy series
Wondering where to stream a series? Check here.
view the rest of the comments
@[email protected] I know you fixed this on our instance, any idea to help the lads here?
We're using the Ansible playbook deployment, and I ended up giving the
pictrsservice a restart through docker (docker restart <id>and you can get the id by usingdocker ps).It didn't seem to be out of space or even offline, it just locked up and stopped responding to both new uploads and existing image requests.
Our pictrs service seems stuck in a restart loop.
Not sure what kind of storage is backing it, but if you're using filesystem storage, the pictrs data directory and files need to be chown'd to 991:991 and/or match the uid/gid in the user line of the docker compose. 991:991 is what's in the documentation