Skip to content
Snippets Groups Projects
Select Git revision
  • kbotor/docker-image-rename
  • bw_mr632_cleanup
  • develop default protected
  • bw_openapi_generation_fix
  • mi/new_gcc_warnings
  • mi/query_supervisor_crash
  • upgrade-postgres-to-17.4
  • jziebinski/bump-tt
  • remove-query-super
  • mi/vectors
  • master protected
  • mt-25-feb-rocksdb-update
  • debug-connection-closing-message
  • mi/pruning
  • split-hived-and-postgres-images
  • g-maintenance
  • mi/issue#245_slow_processing_alarm
  • mi/issue#272_remove_hive_rowid
  • mi/master_merge_with_develop
  • kbotor/permlink-logging
  • 1.27.11rc1 protected
  • 1.27.11rc2 protected
  • 1.27.10 protected
  • 1.27.9 protected
  • test-tag
  • 1.27.8 protected
  • 1.27.7rc16 protected
  • 1.27.7rc15 protected
  • 1.27.7rc14 protected
  • 1.27.7rc13 protected
  • 1.27.7rc12 protected
  • 1.27.7rc11 protected
  • 1.27.7rc10 protected
  • 1.27.6rc9 protected
  • 1.27.6rc8 protected
  • 1.27.6rc7 protected
  • 1.27.6rc6 protected
  • 1.27.6rc5 protected
  • 1.27.6rc4 protected
  • 1.27.6rc3 protected
40 results
Compare
Name Last commit Last update
..
haf-datadir
.env.dev
.env.prod
README.md
app.yaml
backend.yaml
haf_base.yaml
README.md

Using docker compose to run the HAF

Files used in the process:

  • haf_base.yaml (haf instance)
  • backend.yaml (backend application: pgadmin, phgero to preview and manage the database)
  • app.yaml (example of application: postgrest and swagger)

and environment files:

  • .env.dev (for the developer stage)
  • .env.prod (for the production stage)

The environment files specify the versions of images and ports used by applications, as well as the network definition, which varies depending on the version of the environment being run.

This example deployment assumes that haf-datadir local subdirecory can be directly used as HAF instance data directory, by specifying actual path in environment file. As usually, if you want to perform replay, you have to put a block_log file into haf-datadir/blockchain and specify --replay option to the Hived startup options (see ARGUMENTS variable definition in the example env files).

Launch example

1.start/stop naked HAF instance using prod environment

docker compose --env-file .env.prod -f haf_base.yaml up -d
docker compose --env-file .env.prod -f haf_base.yaml down

2.start/stop HAF instance with pgadmin and pghero in dev enviroment

docker compose --env-file .env.dev -f haf_base.yaml -f backend.yaml up -d
docker compose --env-file .env.dev -f haf_base.yaml -f backend.yaml down

3.start/stop HAF instance with pgadmin and pghero and some apps in dev enviroment

docker compose --env-file .env.dev -f haf_base.yaml -f backend.yaml -f app.yaml up -d
docker compose --env-file .env.dev -f haf_base.yaml -f backend.yaml -f app.yaml down