TWikiRegistration default

HtpasswdFileNotUpdating reinforced my conviction that there should be no default TWikiRegistration page, or that if there is one it ought be what we currently call our TWikiRegistrationPub page.

I intend to update DevelopBranch thusly:

1. Rename the default TWikiRegistration page to TWiki.TWikiRegistrationIntranet
2. Rename current TWikiRegistrationPub page to TWiki.TWikiRegistrationInternet
3. Replace TWiki.TWikiRegistration with a note to the administrator telling them to replace the content of this page with a copy of the (raw) content either of the above, as appropriate.

Thoughts?

-- MartinCleaver - 20 Apr 2005

This is a good idea.

-- ArthurClemens - 20 Apr 2005

I've a better idea: Don't have the TWikiRegistration page at all.

As it stands, I have to keep rsurecting my custom copy every time I do a svn update and it gets clobbered.

Yes, have the note: but but it under "Instant Enhancements" soemwhere, or put a note at the opt of the intra/inter versions.

-- AntonAylward - 20 Apr 2005

in light of the MinimalTWiki idea, Registration should be an addon module to the TWikiKernel

-- SvenDowideit - 22 Apr 2005

What are the implications of leaving out registration?

-- ArthurClemens - 22 Apr 2005

I think there are specific implications. Specifically, that we are just making install & set-up of TWiki more obscure for the (I would venture) vaste majority of installations that will want authentication/registration. How many folks do we think will want every edit signed " TWikiGuest" as default?

I'm wondering if this discussion is really just being driven by frustration with failure to get registration code working and inability to reach some consensus about best default registration process?

Being as I mostly work with internet installs, it seems obvious to me that the default should be for internet installs. More seriously, I would propose that we rethink the steps of set-up for registration to make it simpler, NOT shove it under the rug thereby making setup more obscure.

In my recent notes on a simple installer I envisioned a setup wizard that asked whether installation is for a intranet or internet and then, based on that choice, creates the appropriate registration page and supporting authentication files. I know it's simplier to put out this kind of idea then it is to implement it, however, this discussion smacks to me of the development process driving the vision of where we want to go, rather than visa-versa as it should be. Let's rethink how to simplify the set-up process to meet needs of the majority of installations and design to that.

-- LynnwoodBrown - 22 Apr 2005

My 2p worth.

I don't care.

I want that sort of rot handled by the installation script ( script, not document ).

How much effort is it to

print "Are you installing a public server on the Internet? [y/n]";
if (<> =~ /^y/i ) {
    `cp TWikiRegistrationPub.txt TWikiRegistration.txt`
}

-- CrawfordCurrie - 22 Apr 2005

Exactly.

-- LynnwoodBrown - 22 Apr 2005

please consider a web based installer / configurator - the above example looks simple, until the user wants to change to using the other registration mech, or wants to turn it off..

-- SvenDowideit - 23 Apr 2005