Skip to content

POWERSYNC prototype: dev-postgres-powersync environment#94

Draft
Dieterbe wants to merge 41 commits intomasterfrom
feature/dev-postgres-powersync
Draft

POWERSYNC prototype: dev-postgres-powersync environment#94
Dieterbe wants to merge 41 commits intomasterfrom
feature/dev-postgres-powersync

Conversation

@Dieterbe
Copy link
Copy Markdown
Contributor

No description provided.

@Dieterbe Dieterbe changed the base branch from master to feature/development-environment July 29, 2024 16:23
Base automatically changed from feature/development-environment to master July 31, 2024 17:55
@Dieterbe Dieterbe force-pushed the feature/dev-postgres-powersync branch from d4a9b2f to a0f08c2 Compare August 2, 2024 19:39
@Dieterbe Dieterbe changed the title dev-postgres-powersync environment POWERSYNC prototype: dev-postgres-powersync environment Aug 2, 2024
Comment thread postgres/Dockerfile Outdated
Comment thread dev-postgres-powersync/docker-compose.yml Outdated
Comment thread dev-postgres-powersync/powersync-services/powersync.yaml Outdated
# Conflicts:
#	config/dev.env
#	config/prod.env
This would make the startup take several hours to complete
This information is now available on the exercise itself
This was preventing some syncs from happening
Common services can now be included instead of being duplicated on
each service. Changes to volumes, etc. can still be applied as needed.
This saves us the trouble of having to expose the PS service by itself and
makes updating instances much easier.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants