# Implement cookiecutter for squash-bokeh apps

XMLWordPrintable

#### Details

• Type: Story
• Status: Invalid
• Resolution: Done
• Fix Version/s: None
• Component/s:
• Labels:
None
• Story Points:
4.2
• Team:
SQuaRE

#### Description

I think this can be done relatively easy in the current infrastructure. We can have a cookiecutter to create new bokeh apps in the squash-bokeh repository creating a template based on
https://github.com/lsst-sqre/squash-bokeh/tree/master/app/monitor

The new apps can be organized by verification package in that repo, something like:

 squash-bokeh/apps/  /verify  /validate_drp  /code_changes  /AMx  /PAx  /jointcal  /sysver   /monitor  /camera  /opsim  /monitor 

NOTE: Depending on the number of bokeh apps and scalability required we might want to change the deployment architecture to run multiple bokeh servers, and at this point probably the cookie cutter would create a separate repository for each bokeh.

#### Activity

Hide
Angelo Fausti added a comment -

The QA Strategy Working group recommendation (see DMTN-085) was to drop the drill-down functionality from SQuaSH, and thus the bokeh apps we used to have. Cookie-cutter templates for creating bokeh apps used elsewhere are probably a good idea but this need should be captured in another context/ticket.

Show
Angelo Fausti added a comment - The QA Strategy Working group recommendation (see DMTN-085) was to drop the drill-down functionality from SQuaSH, and thus the bokeh apps we used to have. Cookie-cutter templates for creating bokeh apps used elsewhere are probably a good idea but this need should be captured in another context/ticket.

#### People

Assignee:
Angelo Fausti
Reporter:
Angelo Fausti
Watchers:
Angelo Fausti