skadden

Yes it works

Yep. My instance just has me on it and posting elsewhere works without issue. Anything I upload goes to my instance and federates out. It's really quite great not having to worry about the instance drama when big ones defederate from each other. I also turned off NSFW so I don't have to worry about any of that content (legal or otherwise) even hitting my server.

Here's an image of me making this comment via Sync for Lemmy

Edit: I have community creation locked down to admins, which everything disables them on my instance.

Same

Device information

Sync version: v23.08.12-23:05    
Sync flavor: googlePlay    

Ultra user: true    
View type: Slides    
Push enabled: false    

Device: panther    
Model: Google Pixel 7    
Android: 13

There's an outside chance they just don't want to show their username, but yeah OP should make sure they're properly pathing to their creds

I've been running it behind Cloudflare with no issues. I'm also doing it a completely different way than the official docs and the ubergeek method. Mostly because I have a particular way I do my docker stuff.

Every time something has broken it's been 100% on me. My favorite way to learn is by breaking things though, so I also have an account on a different instance in case I break mine and have to wait a bit to fix it 😅

As someone else already said, automated backups should be up on the priority list.

But also maybe try out self hosting Lemmy. It's been a fun little journey and helped me flesh out my Caddy config more than I thought possible.

This may be what you're looking for

Settings shortcut: Post options > Default post sort

From Summit:

Everything working for me as expected on v0.2.1+13

@synae@lemmy.sdf.org is correct, you can pass the values through that part of the UI. I used to do it that way and had Portainer watching my main branch to auto pull/deploy updates but recently moved away from it because I don't deploy everything to 1 server and linking Portainer instances together was hit or miss for me.

Edit: I just deployed it like this (I hit deploy after taking the screenshot) and confirmed both inside the container that it sees everything as well as checking where Portainer drops the files on disk (it uses stack.env)

Stack settings

Environment vars in container

Portainer stack on disk

I don't know why I did all that, but do with it what you will lol

This looks great. Gonna give it a whirl this weekend

You can already do this. You can specify an env file or use the default .env file.

The compose file would look like this:

environment:
      PUBLIC_RADARR_API_KEY: ${PUBLIC_RADARR_API_KEY}
      PUBLIC_RADARR_BASE_URL: ${PUBLIC_RADARR_BASE_URL}
      PUBLIC_SONARR_API_KEY: ${PUBLIC_SONARR_API_KEY}
      PUBLIC_SONARR_BASE_URL: ${PUBLIC_SONARR_BASE_URL}
      PUBLIC_JELLYFIN_API_KEY: ${PUBLIC_JELLYFIN_API_KEY}
      PUBLIC_JELLYFIN_URL: ${PUBLIC_JELLYFIN_URL}

And your .env file would look like this:

PUBLIC_RADARR_API_KEY=yourapikeyhere
PUBLIC_RADARR_BASE_URL=http://127.0.0.1:7878
PUBLIC_SONARR_API_KEY=yourapikeyhere
PUBLIC_SONARR_BASE_URL=http://127.0.0.1:8989
PUBLIC_JELLYFIN_API_KEY=yourapikeyhere
PUBLIC_JELLYFIN_URL=http://127.0.0.1:8096

This is how I do all of my compose files and then I throw .env in .gitignore and throw it into a local forgejo instance.