-
Notifications
You must be signed in to change notification settings - Fork 488
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
Support of Custom Domains for conferences #1599
Comments
Can the domain name be a domain with sub-domain?
What do you mean by that? |
Thanks, If the domain name added is
Currently we can focus on adding
Since, we will be sharing the user session in both the hosted version ( @lagartoflojo Please do let me know your suggestions. EDIT:
A root domain or 'naked' domain should not be added as a CNAME record therefore the custom domain should be a domain with third-level domain label present. Be it www or any other subdomain. I'll create a card to add the same in the written instructions for the custom domain. |
Sure, that sounds perfectly reasonable. Let's implement the simplest version first, and then we can look into the details. |
Yes, sure, I will create a card for this.
I was thinking, one way to maintain session can be to manually configure devise to pass a session token in the header while redirecting back to |
The idea is to allow an organizer of a conference to add his own domain name to the conference.
conference#show
orsplashpage
of a particular conference.Summary of changes to be required when using a custom domain :
For example:
osem.io/conferences/o3DW/schedule
will becomeo3DW.io/schedule
osem.io/conferences/o3DW/register/new
will becomeo3DW.io/register/new
Future Improvements:
The text was updated successfully, but these errors were encountered: