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

Workspaces may be entered via Branded Domain #67

Merged
merged 3 commits into from
Aug 3, 2020

Conversation

zspencer
Copy link
Member

@zspencer zspencer commented Aug 3, 2020

See: #61, #61

Branded Domains allow Visitors to bypass hitting the /workspaces/:slug
path and drop them right in the Workspaces Lobby.

For example, convene-demo.zinc.coop is a branded domain for the

Convene Demo workspace. meet.zinc.coop is a branded domain for the
Zinc workspace.

Screen Shot 2020-08-02 at 4 48 46 PM

@zspencer zspencer requested a review from user512 August 3, 2020 00:00
@zspencer zspencer force-pushed the 61/workspaces-can-be-routed-to-by-fqdn branch from ccd60bf to 948ceb1 Compare August 3, 2020 01:28
@zspencer zspencer marked this pull request as draft August 3, 2020 01:40

ada = zincs_workspace.rooms.create(name: 'Ada', access_level: :unlocked, publicity_level: :listed)
ttz = zincs_workspace.rooms.create(name: 'Talk to Zee', access_level: :unlocked, publicity_level: :unlisted)
ada = zincs_workspace.rooms.find_or_create_by!(name: 'Ada'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
ada = zincs_workspace.rooms.find_or_create_by!(name: 'Ada'
ada = zincs_workspace.rooms.find_or_create_by!(name: 'Ada')

@@ -4,6 +4,9 @@ class Workspace < ApplicationRecord
# Which client owns the workspace
belongs_to :client

# The fully-qualified domain to enter the workspace
attribute :branded_domain, :string
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to add some unique constraint/ validation on branded_domain?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point! I've added a uniquness validation.

Copy link
Contributor

@user512 user512 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 I like it.

See: #61

Branded Domains allow Visitors to bypass hitting the `/workspaces/:slug`
path and drop them right in the Workspaces Lobby.

For example, `convene-demo.zinc.coop` is a branded domain for the
`Convene Demo` workspace. `meet.zinc.coop` is a branded domain for the
Zinc workspace.
Probably should think a bit more about this...
@zspencer zspencer force-pushed the 61/workspaces-can-be-routed-to-by-fqdn branch from 4835ff1 to 65414b4 Compare August 3, 2020 15:34
@zspencer zspencer marked this pull request as ready for review August 3, 2020 15:36
@zspencer zspencer merged commit 23009f7 into development Aug 3, 2020
@zspencer zspencer deleted the 61/workspaces-can-be-routed-to-by-fqdn branch August 3, 2020 16:00
@zspencer zspencer added this to the 1.0 - Andromeda milestone Aug 11, 2020
@zspencer zspencer removed this from the 1.0 - Andromeda milestone Nov 29, 2020
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