Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrate chat from upstream #611

Draft
wants to merge 1 commit into
base: frost
Choose a base branch
from
Draft

Integrate chat from upstream #611

wants to merge 1 commit into from

Conversation

TLSM
Copy link
Collaborator

@TLSM TLSM commented Jul 4, 2023

Substantially borrowed from upstream ref: 13a208ee88e55 (before they started editing generated artefacts instead of source).

Integrated, including:

  • Remove previously removed features: emoji, hats, and name colors
  • Compensate for lack of unified root template
  • Add React build process to Dockerfile and bootstrap/init.sh
  • Preliminary integration of chat websocket workers

For testing, modify supervisord.conf.dev to put chat on port 80 and the site service on some other port. Then visit: http://localhost/chat

Still to do:

  • Access control for specific small-groups (and admins probably): Set the values somewhere (site_settings.json? Redis?) and use for authorization in chat_is_allowed.
  • Proxying only /chat to the websocket workers
  • Chat persistence across restarts: either Redis devops or to DB

Substantially borrowed from upstream ref: 13a208ee88e55 (before they
started editing generated artefacts instead of source).

Integrated, including:
  - Remove previously removed features: emoji, hats, and name colors
  - Compensate for lack of unified root template
  - Add React build process to Dockerfile and `bootstrap/init.sh`
  - Preliminary integration of chat websocket workers

For testing, modify `supervisord.conf.dev` to put chat on port 80 and
the site service on some other port. Then visit: http://localhost/chat

Still to do:
  - Access control for specific small-groups (and admins probably):
    Set the values somewhere (site_settings.json? Redis?) and use for
    authorization in `chat_is_allowed`.
  - Proxying only /chat to the websocket workers
  - Chat persistance across restarts: either Redis devops or to DB
@TLSM TLSM marked this pull request as draft July 4, 2023 17:12
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.

None yet

1 participant