Where is vars/main.yaml ?

[fmuhamadaliev]

Where is vars/main.yaml and other configuration files (system.yml..)?

[fmuhamadaliev]

Now they are all moved to roles/common/defaults/ ?

[vitabaks]

Yes, with the next version (2.3.0), variables will be moved to the common role. See #903

[fmuhamadaliev]

commands for deploying and updating have not changed?

ansible-playbook deploy_pgcluster.yml -i inventory 
ansible-playbook config_pgcluster.yml 

[vitabaks]

Yes, It will work as before.

When using the source code directly (as in your case) or via Ansible Galaxy as a collection (details).

[jefferypalmer]

@vitabaks Nice project, just a quick point that the documentation doesn't refer to this new structure and there are broken links/instructions on pages like: https://autobase.tech/docs/deployment/your-own-machines

I will dig around in the new file structure and find what's needed, as I can't seem to find a working example for a "Your Machines" setup via command line.

Postgres version question, I see vars for PG 15, 16, 17, etc but not minor versions like 16.2 for example, can PG minor versions be defined?

One other quick documentation note is there's a bit of missing documentation on just running autobase. I have a fresh Rocky 9 install and having a quick start of how to build/run the project directly, packages required, etc, for any OS, is great.

Last documentation note, what's the process for upgrading autobase in docker (docker compose)? There's a database image so unsure what's the expectation for the autobase db image update and if those volumes are persistent, etc.

Cheers - jeff

[vitabaks]

the documentation doesn't refer to this new structure

Thanks! Fixed: vitabaks/docs@be770a3

I can't seem to find a working example for a "Your Machines" setup via command line.

Doc: https://autobase.tech/docs/deployment/your-own-machines

See "Command line" tab.

Postgres version question, I see vars for PG 15, 16, 17, etc but not minor versions like 16.2 for example, can PG minor versions be defined?

No, at least I haven’t tested it.

When installing packages from the repository on Debian-based systems, typically only the latest minor version is available — so we simply install whatever is the most recent.

The ability to control minor versions more precisely will become available once support for installing from Docker images is introduced (expected in Autobase 3.0).

One other quick documentation note is there's a bit of missing documentation on just running autobase

A UI, docker installer, and ansible collection are available. All this is written in the documentation https://autobase.tech/docs#getting-started

what's the process for upgrading autobase in docker (docker compose)? There's a database image so unsure what's the expectation for the autobase db image update and if those volumes are persistent, etc.

Just deploy with the new version tag. Goose is used for database schema versioning. And yes, we use persistent volume for the database.