Date: Thu, 11 Nov 2010 10:32:30 +0000
From: Nathan Angelacos <nangel@alpinelinux.org>
To: Alpine Development <alpine-devel@lists.alpinelinux.org>
Subject: Re: [alpine-devel] Alpine 2.2
Message-ID: <20101111103230.492caad9@thx.my.domain>
In-Reply-To: <1289383750.18266.23.camel@ncopa-desktop.nor.wtbts.net>
References: <1289383750.18266.23.camel@ncopa-desktop.nor.wtbts.net>
Precedence: list
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Wed, 10 Nov 2010 11:09:10 +0100
Natanael Copa <ncopa@alpinelinux.org> wrote:

>=20
> * improve admin tools, setup-alpine, ACF, unattended installer etc

=46rom http://www.linuxbsdos.com/2010/08/23/alpine-linux-2-review/

Like a default installation of Alpine Linux, the Browser-based
management interface is very basic, lacking features needed to
configure aspects of some of the services and applications. Most of
what you will accomplish on Alpine will be from the command line
(console or remote access via ssh).
...

If you are a power user, or want to be one, the browser-based
management interface, while intuitive to use, will be a secondary
management tool. Most of the serious stuff you will be doing will be
from the command line.


ACF is now several years old, and still described as "Basic".=20

There are two basic types of ACFs:

Configuration (setting up networking, dnsmasq, etc)
Application (OpenSSL Certificate Authority)

Personally, like the author of the review, I use ssh for
configuration. But but use ACF for the applications.=20

I wonder if we go for a "less is more" approach on ACF, and provide the
something like the current "Expert" tab for all configuration.
Basically, give a web interface to the config files.

And then focus on ACF Applications (e.g. setup-alpine, setup-disk)












---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---