intializing websockets not in working and implemented new file structure #5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… started working with websockets
Introduces websocket real-time collaboration with new socket handler and config files. Migrates Prisma schema and migrations from SQLite to PostgreSQL, updates dependencies to include pg and socket.io, and adjusts server startup to support websockets. Cleans up old migrations and aligns schema with new database provider.
feat: Add websocket support and migrate to PostgreSQL
version 2 in progress
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Implementing a new file structure for better workload management, and along with that, initializing websockets, which are still not in working condition till the next few commits.
This file structure has three routing systems or 3 pillars of backend design to harbour massive chunks of data easily and efficiently, and does not create data logging while multiple stroke entries.
@PreetinderSinghBadesha