while deploying the previous PR (#14) to an older client, ran into an issue with the bespoke postgres update script (the install user used to originally create the database was different than expected)
this PR fixes the issue, so I am merging now, in case anyone upgrading from a very old deployment also has this issue
but it raises the desire to get off of this bespoke upgrade script and instead use pgautoupgrade. as mentioned in the other PR, this is unfortunately currently incompatible with pgvector or any of the existing published discourse images that I know of (the best solution may require publishing our own discourse image that uses pgautoupgrade and does not depend on pgvector)
however, merging this for now as this is the most immediate fix to keep the upgrade path seamless
while deploying the previous PR (https://git.coopcloud.tech/coop-cloud/discourse/pulls/14) to an older client, ran into an issue with the bespoke postgres update script (the install user used to originally create the database was different than expected)
this PR fixes the issue, so I am merging now, in case anyone upgrading from a very old deployment also has this issue
but it raises the desire to get off of this bespoke upgrade script and instead use pgautoupgrade. as mentioned in the other PR, this is unfortunately currently incompatible with pgvector or any of the existing published discourse images that I know of (the best solution may require publishing our own discourse image that uses pgautoupgrade and does not depend on pgvector)
however, merging this for now as this is the most immediate fix to keep the upgrade path seamless
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
while deploying the previous PR (#14) to an older client, ran into an issue with the bespoke postgres update script (the install user used to originally create the database was different than expected)
this PR fixes the issue, so I am merging now, in case anyone upgrading from a very old deployment also has this issue
but it raises the desire to get off of this bespoke upgrade script and instead use pgautoupgrade. as mentioned in the other PR, this is unfortunately currently incompatible with pgvector or any of the existing published discourse images that I know of (the best solution may require publishing our own discourse image that uses pgautoupgrade and does not depend on pgvector)
however, merging this for now as this is the most immediate fix to keep the upgrade path seamless