Hello,
I am trying to setup guacamole in an automated way on kubernetes with
postgresql as a backend.
I've read https://guacamole.apache.org/doc/gug/postgresql-auth.html and
so far it looks like for running guacamole over longer time one would:
- A) one time extract the iniitdb
- B) on upgrades extract the schema changes from
https://guacamole.apache.org/releases/1.6.0/ and apply them
This is a bit in contrast to how I have seen other apps working with
databases which is usually:
- C) re-run a migrate script as an initContainer on every startup, which
checks the database schema version and apply updates as needed itself
From what I gathered, the steps in guacamole would be severely more
involved, as (A) needs some way to keep track of state that the schema
has already been applied (the script does not output SQL that can be
reapplied) and (B) needs some external logic to analyse which versions
have been skipped and manually apply the database schema changes.
Maybe I am missing something or is there a way to use one of the
guacamole containers to achieve (C) at the moment?
Best regards,
Nico
--
Renewable hosting with full IPv6 support. Checkout
www.datacenterlight.ch for details.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
