[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [atomic-devel] [Container-tools] AtomicApp/Nulecule Design and Workflow
- From: Nick Coghlan <ncoghlan gmail com>
- To: Charlie Drage <cdrage redhat com>
- Cc: container-tools <container-tools redhat com>, "atomic-devel projectatomic io" <atomic-devel projectatomic io>
- Subject: Re: [atomic-devel] [Container-tools] AtomicApp/Nulecule Design and Workflow
- Date: Mon, 16 Nov 2015 10:12:03 +1000
On 14 November 2015 at 04:19, Charlie Drage <cdrage redhat com> wrote:
> Personally I'm on the fence on whether or not we should have two
> different CLI's, however, as Dan Walsh pointed out. It's confusing
> having two similarly named CLIs.
I don't have any opinion at all on the technical details of this, but
I do want to *not have to care*. There are a lot of folks here that
care about handling complex multi-service setups, or supporting
Windows and Mac OS X users, and that's important, but the user
experience of installing a *single* application on Fedora/RHEL/CentOS
appears to have been lost in the shuffle.
I think Deis got this aspect right with Helm, as a relatively simple
use case ("Install Redis") is front and centre on Helm's home page:
https://helm.sh/
By contrast, I still don't know how to use Nulecule or AtomicApp to
*actually solve a development problem* (like installing a
containerised PostgreSQL rather than installing it directly on my host
workstation) despite following development since the original launch.
The Nulecule and Atomic App docs aren't much help either, as they
*describe the tool*, rather than *how to use* the tool:
* http://www.projectatomic.io/docs/nulecule/
* http://www.projectatomic.io/docs/atomicapp/
Regards,
Nick.
--
Nick Coghlan | ncoghlan gmail com | Brisbane, Australia
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]