Historia

Neeraj Kashyap 76792ea983 scratch directory in db/		2022-10-14 21:01:39 -07:00
..
alembic	Mumbai blockchain support	2022-08-09 12:51:49 +00:00
configs	Moonstreamdb with read only	2022-03-09 11:40:34 +00:00
deploy	Changed 0.0.0.0 to localhost for db server	2021-10-14 11:06:06 +00:00
moonstreamdb	Black and fix version.	2022-08-25 20:17:30 +03:00
scripts	Add fixes remoce address_id from ethereum_labels_v2.	2021-10-19 23:59:16 +03:00
server	Getting polygon_block_latest_label_moonworm_alpha for status db	2022-04-13 16:29:21 +00:00
.dockerignore	Flag for db name in env generation script	2021-12-01 12:38:14 +00:00
.gitignore	scratch directory in db/	2022-10-14 21:01:39 -07:00
Dockerfile	Docker and docker compose setup for db and moonstream api	2021-11-30 14:29:10 +00:00
README.md	…
alembic.sh	Typo in import in moonstreamdb mmodule	2021-07-27 21:22:14 +00:00
migrate.sh	Docker and docker compose setup for db and moonstream api	2021-11-30 14:29:10 +00:00
mypy.ini	Added EthereumSmartContract model to database	2021-07-28 20:58:56 -07:00
scm.nix	Correct git path for scm mdp repo	2022-08-15 17:15:32 +00:00
setup.py	Removed specific versions at setup.py	2021-11-10 18:10:38 +00:00
sync_conf.yml	XDai schematic upgrade	2022-06-13 13:03:25 +00:00

README.md

moonstream db

Setting up moonstreamdb

Copy sample.env to a new file and set the environment variables to appropriate values. This new file should be sourced every time you want to access the database with the moonstreamdb application or any dependents.

To be able to run migrations, copy alembic.sample.ini to a separate file (e.g. ./secrets/alembic.dev.ini) and modify the sqlalchemy.url setting in the new file to point at your database.

Make sure your database is at the latest alembic migration:

alembic -c ./secrets/alembic.dev.ini upgrade head

Adding a new table to database

Add SQLAlchemy model in moonstreamdb/models.py

Import new model and add tablename to whitelist in alembic/env.py

Create a migration:

alembic -c <alembic config file> revision -m "<revision message>" --autogenerate

Always check the autogenerated file to make sure that it isn't performing any actions that you don't want it to. A good policy is to delete any operations that don't touch the tables that you created.

Then run the migration:

alembic -c <alembic config file> upgrade head