So you have Etherpad installed and working? Now you want to allow users to have sub-domains and their own accounts? Maybe you want the privacy settings, I don’t know…
First off: Got your * dns wildcard in place? You are going to need it.
Then: Set up your smtp server
Finally: Remove the need for SSL
Oh yeah then: Fix the sign in link
I follow all the steps but when we go for pro a/c sign, we got the error : 404 not found: /ep/account/sign-in
Can you plz help us to troubleshoot this
skype johny_mac
John, I see you’ve done more than almost anyone to document Etherpad configuration, but I have yet to find a document explaining the basics, like what is Pro? What are superdomains? If I’m not running my own DNS server, is it even possible to have Team web sites? Are the Team web sites what are meant by Pro?
Etherpad was requested by one of our faculty. I’m just trying to get it installed and working in a reasonably secure manner, but I can’t even figure what the baseline requirements and features are, beyond very easy real time editing.
Pro is Professional editions for Teams. Basically it means you can manage a set of pads and set passwords on them. Etherpad has other pro functions which I won’t go into now but if you consider a class would have a pro account where the teacher would be the admin of the pro account that should clear it up?
Superdomains are the domains Etherpad wants to respond on, IE yourdomain.com or mydomain.com
If you are not running your own DNS server you can still run it in Pro mode. Just assign a Wildcard to the DNS entry on the hosted DNS server or local DNS structure. If you mean can you use team sites without a hostname attached then the answer for now is no.
Yes to your final question.
The main feature of Etherpad is very easy real time editing, we don’t want to lose track of the main focus of the tool. There are new plugins being developed every day, see the google groups and etherpad.org
Any more q’s just lemme know
Thanks, John.
There seems to be an assumption that Etherpad admins control their DNS records, but this isn’t my case. As far as I know, our organization does not accept wildcard entries. Sometimes we’re permitted to request limited alias records for a host, but in general we’re permitted just one record per host, and it’s not a wildcard entry. So I’ve got “hostname.domain.com”, and have to work with that.
It’s great that you share so much of your experience with the rest of us.