UPDATE: Here is what I got so far. Not sure if this is the correct way

Upgrading to 1.2.1 (Lemmy 0.18.5)

First, you need to regenerate your customPostgres.conf file from the examples/customPostgres.conf file. This is done to ensure the new configurations from the example file are applied.

If you don’t want to regenerate, you can manually update your existing customPostgres.conf file. You just need to add the following block to it:

listen_addresses = '*'```

This will allow your Postgres container to listen beyond localhost.

Upgrading to 1.2.0 (Lemmy 0.18.5)

Pull the latest version and checkout to the version you want to upgrade to, which is 1.2.0. You can do this using the following command in your terminal:
```git pull && git checkout 1.2.0```

Next, rename the Postgres password file to postgres.psk. You can do this using the following command:
```mv inventory/host_vars/{{ domain }}/passwords/postgres inventory/host_vars/{{ domain }}/passwords/postgres.psk```

Copy the example vars.yml file to your domain's vars.yml file. You can do this using the following command:
```cp examples/vars.yml inventory/host_vars/{{ domain }}/vars.yml```

Now, you can edit your variables in the newly copied vars.yml file as needed.

Finally, run your regular deployment command. For example:

```ansible-playbook -i inventory/hosts lemmy.yml --become```

Remember to replace {{ domain }} with your actual domain name.

Upgrading to 1.1.0 (Lemmy 0.18.3)

No major changes are required for this update according to the instructions provided.

Could you go to lemmyfi.com from your browser and tell me if it works for you?

I tried it but it didn’t work for me. I’m the instance admin btw. This is on my own instance.

they might be. but they won’t be able to log in to break stuff.

My modlog got spammed today by some script banning a lot of people for spam automatically. It’s getting wild. This was inevitable with the growth of Lemmy as a platform though.