From: Bob Cochran <yocto@mindchasers.com>
To: "Wymore, Farrell" <Farrell.Wymore@windriver.com>,
"DAMIAN, ALEXANDRU" <alexandru.damian@intel.com>,
"Reyna, David" <david.reyna@windriver.com>,
"toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Re: Django user system and permissions
Date: Wed, 28 May 2014 22:59:50 -0400 [thread overview]
Message-ID: <5386A2A6.3040003@mindchasers.com> (raw)
In-Reply-To: <09A9B72E8E1E64419C95E3946F8A6709013A6401@ALA-MBA.corp.ad.wrs.com>
On 05/28/2014 04:35 PM, Wymore, Farrell wrote:
> I’ve attached a (short) working paper. This is fairly high level but
> outlines the main ideas and
>
> implementation plan. Everywhere the documents indicates a ‘build’,
> substitute ‘project’. Please
>
> let me know what you think. Thanks.
>
Hi Farrell,
I have a few questions about your document & Toaster in general:
Will the Toaster permissions correspond in any way to the actual build
folders, or is this just permissions to access specific web pages and
links (e.g., start build)?
A related question: Is the idea that a toaster user will never grab a
shell?
If a user has basic permissions, can a user create a new image recipe,
work directory, and bbappend files to create their own customized image?
If so, will the permission model also support the amount of storage
available to the user? You’ll probably want to prevent a user from
creating an infinite number of new projects until the disks are exhausted.
Why is the Django admin application not supported in Toaster? I just
started using Toaster (but am a long time user of Django). For local
server use, I'll want to patch in the admin app.
Lastly, Upon initial review & use, Toaster seems awesome!
Thank you,
Bob Cochran
next prev parent reply other threads:[~2014-05-29 3:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 19:34 Django user system and permissions Damian, Alexandru
2014-05-28 20:35 ` Wymore, Farrell
2014-05-29 2:59 ` Bob Cochran [this message]
2014-05-29 9:53 ` Barros Pena, Belen
2014-05-29 10:29 ` Damian, Alexandru
2014-05-29 17:46 ` Wymore, Farrell
2014-05-30 13:25 ` Bob Cochran
2014-05-30 16:51 ` Wymore, Farrell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5386A2A6.3040003@mindchasers.com \
--to=yocto@mindchasers.com \
--cc=Farrell.Wymore@windriver.com \
--cc=alexandru.damian@intel.com \
--cc=david.reyna@windriver.com \
--cc=toaster@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.