Posted by Captain Paralytic on 08/30/07 15:19

On 30 Aug, 16:08, salmobytes <Sandy.Pittendr...@gmail.com> wrote:
> I'm working on a mini-micro CMS that amounts to
> a semi-automatic page-generation system that allows
> authorized users to manipulate an administrative menu.
>
> Once installed, the system is remarkably easy to use,
> even for non-html jokies.
>
> Installation is always a bit of adventure.
> On linux, mysql is usually but not always available.
> If mysql is available, a config file can be edited with a form.
> The user might need help from a sys-admin to get the
> db-user-name and password.
>
> If mysql is not available (if I could figure out a way to dynamically
> test for that) I could fall back on a form that sets up .htaccess and
> .htpasswd, so an admin user can gain access to the admin forms.
>
> But htpasswd etc, is only available (isn't this correct?) if the right
> stuff has been pre-set in /etc/httpd.conf
>
> If that isn't available, then my installation for dummies goal
> has hit a brick wall. What third-tier authorization tricks could
> my system try to fall back on, if and only if mysql and .htaccess
> has already failed (for the unsophisticated installer).

htaccess is only implemeted on Apache servers, not on IIS for instance.

[Back to original message]