nextcloud / nextcloud/whiteboard

Add admin option to disable WebSocket warning for hosted instances

Open
#1,054 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
215
Forks
39
Avg merge
1d 3h
Merged PRs (30d)
32

Description

This is not a bug—just an improvement request for hosted instances where the warning is not actionable.

  • Steps to reproduce: Install Whiteboard app on a hosted Nextcloud without WebSocket server. Open admin settings.
  • Expected: Either an option to disable RT collaboration (no warning), or warning only if RT is enabled.
  • Actual: Warning is always shown and cannot be resolved on hosted instances.

Hi! Many people are currently using hosted Nextcloud providers, where they don’t have access to the underlying server configuration.

When installing the Whiteboard app without a WebSocket server, the admin/settings page shows this warning:

There are some errors regarding your setup.
WebSocket server URL is not configured. Real-time collaboration requires a separate WebSocket server. Basic whiteboard functionality works without it. For more details see the documentation

The problem for hosted installations is: users/admins often cannot run or configure a separate WebSocket server. In that case, the warning is permanent, even though basic whiteboard functionality works fine.

Could you add an admin setting in the app to:

  • explicitly disable real-time collaboration / WebSocket support, or
  • suppress this warning when no WebSocket server is intended to be used?

This would improve the experience for hosted Nextcloud users who only want the basic whiteboard features.
Thanks!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the warning on the admin/settings page when no WebSocket server is configured, then inspect the existing real-time collaboration configuration and warning path. Done means an admin can disable real-time collaboration or suppress the warning for hosted instances while basic whiteboard functionality continues to work.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.