Remove testnet and cherry-pick docker-compose

Author: kderme

doc/building-running.md

@@ -19,11 +19,9 @@ they are both at the same level. eg:
 ├── cardano-db-sync
 ├── cardano-node
 ```
-To setup and run db sync node for testnet replace **mainnet** with **testnet** in all examples below.
 These instuction assume than only blocks and transactions for a single blockchain are inserted in
 the db. If you want to to use a single database for more than one chain, you will need to duplicate
-`config/pgpass` and provide a unique db name for each chain (ie mainnet uses `cexplorer`). An example
-testnet `PGPASSFILE` is at `config/pgpass-testnet`.
+`config/pgpass` and provide a unique db name for each chain (ie mainnet uses `cexplorer`).
 
 ### Set up and run a local node
 
@@ -92,34 +90,6 @@ PGPASSFILE=config/pgpass-mainnet db-sync-node/bin/cardano-db-sync \
     --schema-dir schema/
 ```
 
-### Run two chains with a single PostgreSQL instance
+### Network Configuration, Genesis and Topology Files
 
-By running two `cardano-node`s and using two databases within a single PostgresSQL instance it is
-possible to sync two (or more chains).
-
-The two nodes might be run in separate terminals using:
-```
-nix-build -A scripts.mainnet.node -o mainnet-node-remote && ./mainnet-node-remote
-```
-and
-```
-nix-build -A scripts.testnet.node -o testnet-node-remote && ./testnet-node-remote
-```
-and then the two `db-sync` process run as:
-```
-PGPASSFILE=config/pgpass-mainnet scripts/postgresql-setup.sh --createdb
-PGPASSFILE=config/pgpass-mainnet db-sync-node/bin/cardano-db-sync \
-    --config config/mainnet-config.yaml \
-    --socket-path ../cardano-node/state-node-mainnet/node.socket \
-    --state-dir ledger-state/mainnet \
-    --schema-dir schema/
-```
-and
-```
-PGPASSFILE=config/pgpass-testnet scripts/postgresql-setup.sh --createdb
-PGPASSFILE=config/pgpass-testnet db-sync-node/bin/cardano-db-sync \
-    --config config/testnet-config.yaml \
-    --socket-path ../cardano-node/state-node-testnet/node.socket \
-    --state-dir ledger-state/testnet \
-    --schema-dir schema/
-```
+The latest supported networks can be found at [world book](https://book.world.dev.cardano.org/environments.html)

doc/schema-management.md

@@ -28,7 +28,7 @@ order them in the correct order for applying to the database.
 Whenever the Haskell schema definition in `Cardano.Db.Schema` is updated, a schema migration can
 be generated using the command:
 ```
-export PGPASSFILE=config/pgpass-testnet
+export PGPASSFILE=config/pgpass-mainnet
 cabal run cardano-db-tool -- create-migration --mdir schema/
 ```
 which will only generate a migration if one is needed. It is usually best to run the test suite

docker-compose.yml

@@ -31,7 +31,7 @@ services:
         max-file: "10"
 
   cardano-node:
-    image: inputoutput/cardano-node:1.35.2
+    image: inputoutput/cardano-node:1.35.3
     environment:
       - NETWORK=${NETWORK:-mainnet}
     volumes:
@@ -52,7 +52,7 @@ services:
         max-file: "10"
 
   cardano-db-sync:
-    image: inputoutput/cardano-db-sync:13.0.2
+    image: inputoutput/cardano-db-sync:13.0.4
     environment:
       - NETWORK=${NETWORK:-mainnet}
       - POSTGRES_HOST=postgres