add: local development setup instructions #29
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds setup instructions for local development. The issue here is that our production clickhouse database operates in "clustered" mode. This means we need to use the
Replicated
merge tree variants. You can see in the migration that we use theENGINE = ReplicatedMergeTree
. However, when running locally we cannot apply this migration because when we run a single Clickhouse instance we need to use the plaingMergeTree
engine.In this PR I just remove all occurences of the string
Replicated
with an empty string `` from the migrations and put the resulting files in alocal
subdirectory which is excluded from git. When running `local-migrate-up` go-migrate will look into this subdirectory and apply the migrations.I haven't found anything only how people deal with that.