Problems with creating my own instance

I am currently trying to create my own Lemmy instance and am following the join-lemmy.org docker guide. But unfortunately docker compose up doesn’t work with the default config and throw’s a yaml: line 32: found character that cannot start any token error. Is there something I can do to fix this?

The section in question is


<span style="color:#323232;">{% for item in lemmy_env_vars %}
</span><span style="color:#323232;">{% for key, value in item.items() %}
</span><span style="color:#323232;">      - {{ key }}={{ value }}
</span><span style="color:#323232;">{% endfor %}
</span><span style="color:#323232;">{% endfor %}
</span><span style="color:#323232;">{% endif %}
</span>
snekmuffin,

This looks like a Jinja template, so definitely supposed so be populated by something else first. Yaml is basically just a prettier Json so it wouldn’t support something like that section on its own.

BlueEther,
@BlueEther@no.lastname.nz avatar
ptz,
@ptz@dubvee.org avatar

Try this docker-compose file: github.com/LemmyNet/lemmy/…/docker-compose.yml

Here’s the docs for pict-rs: git.asonix.dog/asonix/pict-rs/src/…/pict-rs.toml

Everything in the config file has an env var you can set. The most important one is the PICTRS__SERVER__API_KEY

Certainly_No_Brit,

as @walden already mentioned, the files in Lemmy’s documentation are the wrong ones. The correct file seems to be in https://github.com/LemmyNet/lemmy/blob/main/docker/docker-compose.yml.

The documentation won’t help you if you don’t want to use Ansible.

walden, (edited )

I’m not a pro at Docker, but I’ve spun up over 30 different services using Docker Compose so I’m more than a novice. I would say that Lemmy’s documentation is the worst I’ve ever seen.

The website points you at that compose file which is (I think?) designed for Ansible. I think there’s another example somewhere without all the jibbery joo, but I can’t search for it right now.

Edit: here it is github.com/LemmyNet/lemmy/…/docker-compose.yml

No idea why they don’t link to that one in the first place. I’d fix it if I knew how.

chiisana,
@chiisana@lemmy.chiisana.net avatar

If memory serves, the default docker compose expose the database port with a basic hard coded password, too. So imagine using the compose without reading too much, next thing you know you’re running a free Postgres database for the world.

Edit: yep, still publishing the db port with hard coded password…

SomeBoyo,

Thank you, I was wondering, what that stuff was

walden,

I just updated my comment above with more info, FYI.

hedgehog,

If you use that docker compose file, I recommend you comment out the build section and uncomment the image section in the lemmy service.

I also recommend you use a reverse proxy and Docker networks rather than exposing the postgres instance on port 5433, but if you aren’t familiar with Docker networks you can leave it as is for now. If you’re running locally and don’t open that port in your router’s firewall, it’s a non-issue unless there’s an attacker on your LAN, but given that you’re not gaining anything from exposing it (unless you need to connect to the DB directly regularly - as a one off you could temporarily add the port mapping), it doesn’t make sense to increase your attack surface for no benefit.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • selfhosted@lemmy.world
  • DreamBathrooms
  • everett
  • InstantRegret
  • magazineikmin
  • thenastyranch
  • rosin
  • Durango
  • ethstaker
  • Youngstown
  • slotface
  • khanakhh
  • kavyap
  • ngwrru68w68
  • osvaldo12
  • JUstTest
  • tacticalgear
  • cubers
  • cisconetworking
  • anitta
  • provamag3
  • modclub
  • mdbf
  • GTA5RPClips
  • tester
  • megavids
  • normalnudes
  • Leos
  • lostlight
  • All magazines