[SCM] postgis.net branch website updated. clarity-final-208-g530b023

git at osgeo.org git at osgeo.org
Wed Jul 29 11:50:58 PDT 2026


This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "postgis.net".

The branch, website has been updated
       via  530b023df14e44984a3968d67181d0cc483c46aa (commit)
       via  507501648ea9bfac51f7bf78b699f5fdef1608c3 (commit)
      from  ea0dc45cb56a87f3e7898aed38b23877a22e9de6 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 530b023df14e44984a3968d67181d0cc483c46aa
Merge: ea0dc45 5075016
Author: Darafei Praliaskouski <komzpa at gmail.com>
Date:   Wed Jul 29 11:50:57 2026 -0700

    Merge pull request 'Move Trac wiki guidance onto the website' (!15) from Komzpa/postgis.net:ai/trac-wiki-site-migration-20260729 into website
    
    Reviewed-on: https://gitea.osgeo.org/postgis/postgis.net/pulls/15


commit 507501648ea9bfac51f7bf78b699f5fdef1608c3
Author: Darafei Praliaskouski <me at komzpa.net>
Date:   Wed Jul 29 22:38:25 2026 +0400

    Move Trac wiki guidance onto website

diff --git a/content/development/bug_reporting.md b/content/development/bug_reporting.md
index e2f9dca..9d888a5 100644
--- a/content/development/bug_reporting.md
+++ b/content/development/bug_reporting.md
@@ -32,6 +32,9 @@ geekdocHidden: false
       SELECT version();
       SELECT postgis_full_version();
       ```
+    * If the issue is a crash, include a backtrace when possible. The
+      [testing and debugging guide](/development/docs/testing/#backtraces)
+      describes how to attach `gdb` to a PostgreSQL backend and capture one.
 <br/>
 
 ## Security Issues
diff --git a/content/development/getting_involved.md b/content/development/getting_involved.md
index d0d9ef3..f2714ab 100644
--- a/content/development/getting_involved.md
+++ b/content/development/getting_involved.md
@@ -33,6 +33,5 @@ If you've read all the above, and are ready to submit a patch, do the following:
     a pull request on one of the postgis [git mirrors or primary repo](../source_code/#source-code-repository).
 
 If your feature involves a new function/ feature, we expect documentation to accompany this.
-Details on how to prepare documentation are on [Submitting documentation for a new feature](https://trac.osgeo.org/postgis/wiki/DevWikiDocNewFeature)
-
+Details on how to prepare documentation are in the [manual documentation workflow](/development/docs/manual/#documenting-new-sql-features).
 
diff --git a/content/development/rfcs/rfc05.md b/content/development/rfcs/rfc05.md
index bfe44e6..f8b7850 100644
--- a/content/development/rfcs/rfc05.md
+++ b/content/development/rfcs/rfc05.md
@@ -38,7 +38,7 @@ New core contributors are responsible for having read, and understood this docum
 * To accomplish Guidelines standards, we have implemented the use of ​editorconfig. Our repo as of version 2.4 now contains a .editorconfig file which editors configured with editorconfig support abide by.
 * We ask all developers to work with an editor that has editorconfig support. Many editors have it or have it as plugins.
 * All source code in GIT should be in Unix text format as opposed to DOS text mode with possible exception of .bat files.
-* Each new/changed function should be documented in the official docs following our [Documentation Guidelines](https://trac.osgeo.org/postgis/wiki/DevWikiDocNewFeature)
+* Each new/changed function should be documented in the official docs following our [Documentation Guidelines](/development/docs/manual/#documenting-new-sql-features)
 
 # Repo Administrator
 One member of the Project Steering Committee will be designated as the Repo Administrator. That person will be responsible for giving write access to folks, updating the CREDITS, and other repo related management.
diff --git a/content/documentation/getting_started/install_ubuntu.md b/content/documentation/getting_started/install_ubuntu.md
index e1927c7..ea25d94 100644
--- a/content/documentation/getting_started/install_ubuntu.md
+++ b/content/documentation/getting_started/install_ubuntu.md
@@ -6,8 +6,60 @@ geekdocHidden: true
 geekdocHiddenTocTree: false
 ---
 
-* The best place to get the latest binaries for both PostgreSQL and PostGIS is from the [PostgreSQL download page Debian](https://www.postgresql.org/download/linux/ubuntu/) and [PostgreSQL download page Ubuntu](https://www.postgresql.org/download/linux/ubuntu/).
+* The PostgreSQL project documents the current Debian and Ubuntu package setup on
+  the [Debian download page](https://www.postgresql.org/download/linux/debian/)
+  and [Ubuntu download page](https://www.postgresql.org/download/linux/ubuntu/).
+  Follow those instructions for the PostgreSQL Apt Repository. The automated
+  repository setup is:
 
-* The PostgreSQL build team has packages for Debian and Ubuntu for several versions of PostgreSQL and PostGIS [APT repository](https://wiki.postgresql.org/wiki/Apt) for PostgreSQL builds.
+  ```sh
+  sudo apt install -y postgresql-common
+  sudo /usr/share/postgresql-common/pgdg/apt.postgresql.org.sh
+  ```
 
-* For specific PostGIS directions, see the [Ubuntu install guide](https://trac.osgeo.org/postgis/wiki/UsersWikiPostGIS3UbuntuPGSQLApt).
\ No newline at end of file
+* For source builds and contributor test environments, see the
+  [Ubuntu development environment guide](/development/docs/environment/ubuntu/).
+
+## PostgreSQL Apt Repository
+
+After configuring the PostgreSQL Apt Repository, replace `18` below with the
+PostgreSQL major you want to run:
+
+```sh
+sudo apt install postgresql-18 postgresql-18-postgis-3
+```
+
+Install the PostGIS command-line tools, such as `shp2pgsql` and `raster2pgsql`,
+with:
+
+```sh
+sudo apt install postgis
+```
+
+Debian-style PostgreSQL packages can install several PostgreSQL majors side by
+side. Check the active clusters and ports with:
+
+```sh
+pg_lsclusters
+```
+
+Create a user database before enabling extensions. Do not install PostGIS in the
+default `postgres` maintenance database:
+
+```sql
+CREATE DATABASE gisdb;
+\connect gisdb
+CREATE EXTENSION postgis;
+SELECT postgis_full_version();
+```
+
+Enable optional extensions only when you need them:
+
+```sql
+CREATE EXTENSION postgis_raster;
+CREATE EXTENSION postgis_topology;
+CREATE EXTENSION postgis_sfcgal;
+```
+
+Packages for related projects such as pgRouting follow the same PostgreSQL-major
+pattern, for example `postgresql-18-pgrouting`.

-----------------------------------------------------------------------

Summary of changes:
 content/development/bug_reporting.md               |  3 ++
 content/development/getting_involved.md            |  3 +-
 content/development/rfcs/rfc05.md                  |  2 +-
 .../getting_started/install_ubuntu.md              | 58 ++++++++++++++++++++--
 4 files changed, 60 insertions(+), 6 deletions(-)


hooks/post-receive
-- 
postgis.net


More information about the postgis-tickets mailing list