Slavi Pantaleev 8d186e5194 Fix Postgres import when Postgres had never started ... If this is a brand new server and Postgres had never started, detecting it before we even start it is not possible. This moves the logic, so that it happens later on, when Postgres would have had the chance to start and possibly initialize a new empty database. Fixes #82 (Github issue)		2019-01-21 07:32:19 +02:00
..
util	Split playbook into multiple roles	2019-01-12 18:01:10 +02:00
import_postgres.yml	Fix Postgres import when Postgres had never started	2019-01-21 07:32:19 +02:00
import_sqlite_db.yml	Make roles more independent of one another	2019-01-16 18:05:48 +02:00
init.yml	Make roles more independent of one another	2019-01-16 18:05:48 +02:00
main.yml	Make roles more independent of one another	2019-01-16 18:05:48 +02:00
migrate_postgres_data_directory.yml	Stop Postgres before finding files to move over	2019-01-12 18:16:08 +02:00
setup_postgres.yml	Make roles more independent of one another	2019-01-16 18:05:48 +02:00
upgrade_postgres.yml	Make roles more independent of one another	2019-01-16 18:05:48 +02:00
validate_config.yml	Make roles more independent of one another	2019-01-16 18:05:48 +02:00