Lemmy Support

4634 readers

4 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago

MODERATORS

dessalines@lemmy.ml

streamlined docker compose (lemmyhelp.tet42.org)

submitted 1 year ago* (last edited 1 year ago) by tet42@ka.tet42.org to c/lemmy_support@lemmy.ml

20 comments fedilink hide all child comments

I am working on writing up some quality help/instructions for Lemmy instance admins. This is targeted toward those that are newer to Lemmy and Docker, but even those that know a thing or two might learn something from me. I have been a sysadmin for over 20 years, so I know some things.

I thought I'd share the first complete page I have written. I'd love some feedback if you have any to share.

Be seeing you.

you are viewing a single comment's thread
view the rest of the comments

[–] BurningnnTree@lemmy.one 2 points 1 year ago* (last edited 1 year ago) (1 children)

I was expecting your document to be some kind of tutorial, but it seems like you wrote it for people who already know what they're doing. I would need to understand the "normal" way of doing it first before I would be able to understand what you're talking about in your document. (Note: I'm new to Docker, which is why I gave up on setting up my own Lemmy server. It would be nice if someone could write a tutorial specifically for people who are new to Docker.)

If you want to help people set up their instances, I don't think your document should have so much focus on the differences between your method and the official method, because that just adds to the confusion. It would be more helpful to just focus on your method and explain it in a way that noobs can understand.

[–] tet42@ka.tet42.org 2 points 1 year ago* (last edited 1 year ago)

I do appreciate your feedback, but I think at a minimum that anyone trying to run a Lemmy instance in Docker should know how to install docker and docker compose and how to run basic commands like docker compose up -d. There are many tutorials out there for doing just that and I'm not trying to reinvent the wheel. Once you have gotten that part done my document kicks in and picks up where the official documentation is currently lacking (in my opinion).

I do explain a lot, but I did my best to explain it in terms that most anyone could understand.

I will take your feedback to heart and maybe try to write a step by step tutorial for people who are completely new to Docker as well.