When installing PasarGuard with PostgreSQL, for example:
curl -fsSL https://github.com/PasarGuard/scripts/raw/main/pasarguard.sh -o /tmp/pg.sh \
&& sudo bash /tmp/pg.sh install --database postgresql
the installer asks the user to create/configure a local database name, username, and password.
This works for local databae setups, but not every user wants to use a local database. Some users may already have database running on another server, a managed database provider, or a separate database container.
It would be useful if the installer supported an external database option.
For example, the installer could ask;
- Do you want to use a local database or an external database?
- Database type
- Database host
- Database port
- Database name
- Database username
- Database password
- SSL mode, if needed
Desired example:
Database type: PostgreSQL
Database location: External
Host: db.example.com
Port: 5432
Database: pasarguard
Username: pasarguard
Password: ********
This would make deployments more flexible and cleaner for production environments.
Thanks.
When installing PasarGuard with PostgreSQL, for example:
curl -fsSL https://github.com/PasarGuard/scripts/raw/main/pasarguard.sh -o /tmp/pg.sh \ && sudo bash /tmp/pg.sh install --database postgresqlthe installer asks the user to create/configure a local database name, username, and password.
This works for local databae setups, but not every user wants to use a local database. Some users may already have database running on another server, a managed database provider, or a separate database container.
It would be useful if the installer supported an external database option.
For example, the installer could ask;
Desired example:
Database type: PostgreSQL Database location: External Host: db.example.com Port: 5432 Database: pasarguard Username: pasarguard Password: ********This would make deployments more flexible and cleaner for production environments.
Thanks.