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 :)
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.
Are there any published guidelines on the server requirements for an instance? I have my own instance running, seems to be working fine. But I'm reluctant to open it publically without an idea of if I'm setting myself up for failure or not.
Related, is there a way to entirely disable image uploads to my instance? I'm ok with it being a "reader" instance, but don't want to be hosting content directly.
Ok, figured it out myself. For anyone else that needs it..
Run a shell within the postgres docker container:
docker exec -it _postgres_1 sh
Connect to the postgres service:
psql -U lemmy -h 127.0.0.1 -p 5432 -d lemmy
Connect to the lemmy database:
\c lemmy
Then the user table: \d local_user
Find the user ID of the account you want to manually toggle, probably #1:
SELECT * from local_user;
Then update the email_verified and _accepted_application flag on the first account:
UPDATE local_user SET email_verified = 't', accepted_application = 't' WHERE id = 1;
lemmy=# UPDATE local_user SET email_verified = 't', accepted_application = 't' WHERE id = 3; UPDATE 1 lemmy=# UPDATE local_user SET email_verified = 't', email_verified= 't' WHERE id = 3; UPDATE 1 lemmy=#
Thats what I figured... I just have no idea how to do it. Can you point me to any info on how to do that? :)
I didn't, I spun up an entirely new instance.