This is the enhancement of the Toaster start-up and configuration scripts to make it easy to (a) separately start and stop the Web service, and (b) easily attach and detach builds or projects to that shared database and initializing a new database as appropriate.
I am not sure what we actually need here - the bitbake/bin/toaster script, in execute (i.e. not sourced) mode, is just the combination of existing modular commands that django provides, for starting and stopping the web server, or for updates to the database I am not sure what "attach and detach builds or projects" implies.
David Reyna has mentioned this is no longer required for M1: moving to 1.8 so that he can give it a new milestone.
Alex asks: "I am not sure what "attach and detach builds or projects" implies." * Here is the "attach" scenario: (1) User creates or has existing projects that were not started with Toaster running. (2) User wishes to start tracking data on those projects with Toaster. (3) The issue is that those "outside" projects do not have a Toaster conf file, and thus will not add their build data to the Toaster database by bitbake. How can a user bring "outside" projects into Toaster, and thus "attach" them to Toaster? Is there a formal command? * Here is the "detach" scenario: (1) User has a project being tracked by Toaster (2) User wishes to stop tracking that project by Toaster Is there a formal command? Presumably the manual command is to delete that projects Toaster conf file?
The importing projects functionality (bug 6603) could somehow cover the 'attach' scenario. The 'detach' scenario could be covered as part of the delete functionality (bug 6238), or as part of some archive / restore functionality. In any case, I am not sure we'll get to this as part of 1.8.
I am withdrawing this defect because the team agrees that it is covered by bugs 6603 and bug 6238, as per Belen's comments.
Verified.