Unable to sync multiple geopackages from a single MM project
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 50/100
Research direction
No files or tests are named. Start by locating where db-sync creates the local project directory under $TEMP/dbsync and reproduce two connections targeting one MM project; done means multiple geopackages can sync independently without Docker containers or separate temporary-directory environment settings.
Written by the indexing model from the issue text.
Description
Right now, syncing multiple geopackages from a single MM project on a single computer does not work:
- if there's one config file with multiple connections (to the same MM project), these connections use the same working project directory (in
$TEMP/dbsync) - and that causes issues, because each connection should have its independent working directory - even if there are multiple db-sync daemons running, each with a separate config file, this is still not going to work because of the working project directory collision as above. There are two ways to avoid working directory collisions in this case:
- run db-sync in docker containers (each container has its own temporary directory); or
- set a different temporary dir (using env variable) for each db-sync run
Both of these cases should ideally work without any fiddling needed... Probably we could just fix the local project directory naming so that they are more unique (e.g. include gpkg name, db schema name?)
- Dominant language
- Python
- Stars
- 53
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MerginMaps/db-sync
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MerginMaps/db-sync#184 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
MerginMaps/db-sync#185 · 1 comment ·
-
db-sync enters an infinite drop/recreate loop when geodiff init fails on invalid source geometries Open
Difficulty 4/5 3-5 days Newbie friendliness 42/100
MerginMaps/db-sync#182 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
MerginMaps/db-sync#181 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
MerginMaps/db-sync#179 · 3 comments ·
All issues in MerginMaps/db-sync
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100