Lodion Now • 100%
I didn't, I spun up an entirely new instance.
Lodion Now • 100%
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 :)
Lodion Now • 100%
Thats what the "docker-compose down" is for in the second step :)
I'm planning to move my instance to a new VPS provider that will allow me to scale more simply. Has anyone done this already and can sanity check my plan? My current setup was spun up using the ansible playbook [here](https://github.com/LemmyNet/lemmy-ansible). Current plan is: Lower DNS TTL to 60 seconds (already done) Shutdown on current VPS: docker-compose down backup /srv/lemmy/<instance>/ and copy to new host sudo tar -zcvpf backup.tar.gz /srv/lemmy/<instance>/ scp backup.tar.gz user@newhost update dns A and AAAA records, wait 1 minute, verify DNS has updated run ansible script Shutdown on new VPS: docker-compose down restore backup to /srv/lemmy/<instance>/ Startup on new VPS with restored DB etc: docker-compose up -d test destroy old VPS Increase DNS TTL to 86400 Anything I've missed? :)
Lodion Now • 100%
I've only reached level 23, but have been thoroughly enjoying it so far. Usually end-game is the real test, but by most reports finishing the campaign is ~40 hours of gameplay alone. Given the hundreds of hours I sank into D3 it was an easy buy for me.
edit: also the in game shop is totally ignoreable. Currently it isn't shoved down your throat, you have to go looking for it. Given it is 100% cosmetics, I'm not fussed by it.
Lodion Now • 100%
I've found email verification is finnicky to say the least. The Lemmy UI has some issues with users being stuck with spinning icons at various points for a start.
In the back end... email is a pain. If you're using a public cloud VM and using the Lemmy provided docker/ansible postfix image, your users are unlikely to receive the verification emails as your server's IP address is likely n a DNSBL somewhere.
If you use a third party SMTP service you may have more luck... but even then you'll likely have issues.
I've disable email verification for these reasons, and rely on the answer to the signup question to vet applicants.
Lodion Now • 100%
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.
Lodion Now • 100%
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 :)
Lodion Now • 100%
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?
Lodion Now • 100%
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;
Lodion Now • 100%
As others have said, Jerboa is for android... I've heard mention of "mlem" for IOS, but have not seen it myself.
Lodion Now • 100%
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.
Lodion Now • 100%
Currently you have to start over.
Lodion Now • 100%
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.
Lodion Now • 100%
..that would defeat almost the entire point of being federated and decentralized.
Lodion Now • 100%
Surprisingly... its better than I had hoped for. I'm ~6-8 hours in, level 23 or so... and its been great.
Lodion Now • 100%
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.
Lodion Now • 100%
Not sure I'd say "careful"... more of "don't get too comfortable". As the dust clears I'd expect some/many of the new instances to shutdown. Likely due to hitting server resource limits, or admin motivation limits :)
I’ve hit an issue with Lemmy. Initial startup was fine… I created my admin user and logged in. Then I created this account. Third account I went to test with failed to login… then my other accounts also failed, so I rebooted. Now when I try to log into my admin account, it just spins forever. Checking logs, I see this: lemmy_server::api_routes_websocket: email_not_verified: email_not_verified Can anyone tell me how I can manually flag my admin account as having been email verified already?
I've hit an issue with Lemmy. Initial startup was fine.. I created my admin user and logged in. Then I created this account. Third account I went to test with failed to login.. then my other accounts also failed, so I rebooted. Now when I try to log into my admin account, it just spins forever. Checking logs, I see this: lemmy_server::api_routes_websocket: email_not_verified: email_not_verified Can anyone tell me how I can manually flag my admin account as having been email verified already?