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
--
_______________________________________________
toaster mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/toaster
