Web Mercator projection, EPSG:900913

[JimBacon]

Just an observation that the tip relating to correcting projection for PostgreSQL 13 remains true for PostgreSQL 15

"Tip If installing PostgreSQL 13, it may come with an incorrect projection for the Web Mercator projection, EPSG:900913. This will result in map data being recorded in the wrong location. To fix this, run the following query:"

Moved from Indicia-Team/warehouse#490

[benj-d]

I can't edit directly but could fork and create a pull request for amendments. As an aside while working through this the references to PHP 5.x were a bit misleading, it took me a while to work out which PHP version (8.0) i had to use to avoid compatibility/support issues with the PostgreSQL (15) and Drupal (9.5). Might be useful to have a a reference to that here?

Given the other PostgreSQL 15 related issue might also be worth recommending 13 or am i missing somewhere that version compatibilities with each other and Indicia are already listed?

Sorry, gone off piste a bit there but i did struggle quite a lot getting the environment right. Someone coming at this new (and outside Docker) is likely to face similar issues. That said i am not sure how it would be kept consistently up to date with development...

[JimBacon]

The documentation is not keeping up with the march of time. PHP5 is long dead and PHP8.0 is dead in a couple of months.

We list version compatibility at https://indicia-docs.readthedocs.io/en/latest/administrating/installation-requirements.html and it is out of date.

The only way to keep it up to date is to be able to invest the effort in continuously testing and managing the situation and we are too stretched to do that at present (and for the last N years). The next best thing is to update it whenever someone does a new install and bumps in to all the changes, just like you are doing.

It would therefore be really useful to capture all your observations.

If you are happy to fork the docs and submit a pull request with your amendments that would be most efficient from my perspective and super helpful. The alternatives are for you to raise lots of issues and for me to one day try to make the changes but it would be low priority. Another option would be for you to have write permissions on the repo if you are comfortable with that and no one else is uncomfortable.