I didn’t, I spun up an entirely new instance.

Nah, part of the playbook sets up the initial Lets Encrypt certificate… so DNS needs to point to the new VPS. And the hostname needs to match the existing instance as it is referenced in the database.

Doesn’t matter now anyway, I went a different route :)

Thats a different issue to what I encountered. For me the nginx docker config had a reference to the host nginx config… I had no nginx installed so “docker-compose up” failed.

Then yes, as I said… no users on sopuli.xyz have subscribed to your community yet: Suomi@suppo.fi - 0 subscribers

Other replies here have provided more info :)

Content for communities you’ve created on your instance will only be visible on other instances if a user there has subscribed to the community.

Or do you mean yours posts to communities homed to other instances do not show up?

In the UI? Not that I know of. From the database… sure:

docker exec -it <instancename>_postgres_1 sh

psql -U lemmy -h 127.0.0.1 -p 5432 -d lemmy

SELECT * from local_user;

If your VPS is purely for Lemmy, I’d suggest blowing it away and using the ansible playbook referenced here. I found the current docker-compose does not function, there are broken references to external nginx configs.

Sure, its a bit wordy… lacking in images with step by step instructions. If I had time I’d put something together with screenshots and figure out git and submit a pull request… maybe eventually.

The icon on the left is “context”, on your home instance. On the right is the “fediverse” link, which takes you to the home instance of the poster.

Basically the same thing, one is local the other remote.

At least that is how I’ve come to understand them.

Surprisingly… its better than I had hoped for. I’m ~6-8 hours in, level 23 or so… and its been great.

Yeah sounds like an issue on your instance… not sure exactly what. I’m on my own instance, see multiple comments here from @jonah@lemmy.one and yourself.

Is there a newbie guide written up already somewhere? This is exactly the sort of things it needs, which should be linked to new signups.

Votes and edits makes sense, sounds like a good guess to me!

Thanks for digging that up. Had been one of my outstanding questions. I agree with the initial requestor of that issue; it will be a major source of friction for users migrating to Lemmy from Reddit.

I’d like to be able to at least manually trigger the retrieval of a set of posts/comments as a user. Otherwise as the requestor noted, its going to make interacting with “new” communities difficult and unintuitive if you can’t see comments from before when it was synced to your local instance.

Browser works fine. But I’m not always at my PC. Seems like a missing feature in Jerboa?

Maybe I’m dumb, I can’t find how to add a new community to my subscribed list in Jerboa.

Sorry mate, I’m out of ideas.

I’ve just taken a look at your instance… you’re running a slightly older version. I’m guessing the DB schema has changed.

Does “SELECT * from local_user.id;” get you a list of users? You may need to update the other references to match whatever the old DB schema is.

Not sure what to suggest, sorry I’m not a DBA :(

To make it clear, here is the command I ran enclosed with "

“UPDATE local_user SET email_verified = ‘t’, accepted_application = ‘t’ WHERE id = 1;”

Sorry Chris, I was figuring that out as I went. It looks like a postgres syntax error but the command matches what I used.

If you run “SELECT * from local_user;” do you get output showing your list of registered users? Perhaps you’re not attached to the lemmy database?