Lodion

joined 1 year ago
[–] Lodion@lemmy.click 1 points 1 year ago

Each instance admin will do their own thing. Check the sidebar on the front page of your instance, usually it would be mentioned there.

To support development, click "Join Lemmy" at the bottom of the page, then scroll to the bottom. The devs have several methods to accept donations.

[–] Lodion@lemmy.click 1 points 1 year ago

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

[–] Lodion@lemmy.click 2 points 1 year ago (2 children)

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@lemmy.click 15 points 1 year ago (1 children)

Yeah, could do without the straw man arguments and deflective non-answers.

[–] Lodion@lemmy.click 4 points 1 year ago (1 children)

Thats what the "docker-compose down" is for in the second step :)

11
Instance relocation (lemmy.click)
submitted 1 year ago* (last edited 1 year ago) by Lodion@lemmy.click to c/lemmy@lemmy.ml
 

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.

Current plan is:

Lower DNS TTL to 60 seconds (already done)

Shutdown on current VPS: docker-compose down

backup /srv/lemmy// and copy to new host

sudo tar -zcvpf backup.tar.gz /srv/lemmy//

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//

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@lemmy.click 3 points 1 year ago* (last edited 1 year ago)

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@lemmy.click 2 points 1 year ago* (last edited 1 year ago)

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@lemmy.click 1 points 1 year ago

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@lemmy.click 12 points 1 year ago (2 children)
[–] Lodion@lemmy.click 3 points 1 year ago

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@lemmy.click 4 points 1 year ago (6 children)

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@lemmy.click 8 points 1 year ago

This seems to have more specifics.

 

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?

view more: next ›