https://github.com/paoliniluis/metabase-serialization

https://github.com/paoliniluis/metabase-serialization

Last synced: 7 days ago
JSON representation

• Host: GitHub
• URL: https://github.com/paoliniluis/metabase-serialization
• Owner: paoliniluis
• Created: 2022-07-19T16:43:41.000Z (over 2 years ago)
• Default Branch: main
• Last Pushed: 2023-11-21T13:02:25.000Z (about 1 year ago)
• Last Synced: 2024-11-07T06:47:34.595Z (about 2 months ago)
• Language: Shell
• Size: 1000 Bytes
• Stars: 0
• Watchers: 1
• Forks: 1
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
Contents of this docker-compose

===============================

This stack is to use serialization features. It is comprised of:

- an origin enterprise Metabase instance exposed in port 3001

- an origin postgres database as the application database of origin Metabase (not exposed, only seen by origin Metabase)

- a destination enterprise Metabase instance exposed in port 3002

- a destination postgres as the application database of destination Metabase (not exposed, only seen by destination Metabase)

The origin and destination Metabase applications see the folder "metabase_dump" that is the one where the origin dumps the data and the destination picks it up

Each stack (origin Metabase and destination Metabase) is on its own network (called metanet1 for origin and metanet2 for destination) so they are both isolated.

Serialization

=============

When you finish doing the questions/dashboards on the source instance (localhost:3001), from the command line do `docker exec -it metabase_origin java -jar /app/metabase.jar dump /target` to do the load from the source container and then `docker exec -it metabase_destination java -jar /app/metabase.jar load /target`