Add a "None" frontend so that users can build session images where they bring their own frontend.
Typical use-case: app dashboards, e.g. streamlit
In this case, the project folder would contain a Procfile which defines the default web process to launch.
Why is this needed? The other frontend options add default = true to the launch configuration, so the custom frontend would need to be launched manually and would not be the default. With the explicit "none" frontend, we can let users define their own default process.
Add a "None" frontend so that users can build session images where they bring their own frontend.
Typical use-case: app dashboards, e.g. streamlit
In this case, the project folder would contain a
Procfilewhich defines the defaultwebprocess to launch.Why is this needed? The other frontend options add
default = trueto the launch configuration, so the custom frontend would need to be launched manually and would not be the default. With the explicit "none" frontend, we can let users define their own default process.