64 panel core

Core/Panel/Dockerfile

@@ -17,7 +17,7 @@
 
 # First stage
 
-ARG BASE_IMAGE=quay.io/enthought/edm-centos-7:3.4.0
+ARG BASE_IMAGE=quay.io/enthought/edm-centos-7:latest
 
 FROM $BASE_IMAGE as stage_one
 

Core/Panel/README.md

@@ -75,8 +75,7 @@ collecting environment variables set by Edge when the container is launched.
 
 When developing locally, it's also convenient to have an EdgeSession.  You
 can get the "ci" module to inject the appropriate environment variables, so
-that your ``EdgeSession()`` call will work with ``python -m ci run`` and
-``python -m ci preflight``.  
+that your ``EdgeSession()`` call will work with ``python -m ci run``.  
 
 To do so, follow this procedure:
 
@@ -85,8 +84,8 @@ To do so, follow this procedure:
   ``"https://edge.enthought.com/services/api"``.
 * Define EDGE_API_ORG in that file.  This is the "short name" displayed in
   the URL bar when you log into an organization, for example, ``"default"``.
-* Define EDGE_API_TOKEN.  You can get one of these by going to the
-  ``/hub/token`` endpoint on the Edge server.
+* Define EDGE_API_TOKEN.  You can get one of these from the ``My Profile``page
+  in the Edge UI.
 
 Be sure *not* to check the "dev_settings.json" file into source control, as it
 contains your API token.
@@ -105,9 +104,6 @@ the prefix from requests, handling the OAuth2 login flow, pinging JupyterHub
 for container activity, and more.  But, there are a few guidelines you will
 need to follow in your own Dockerfile.
 
-* Don't change the user to anything other than ``app`` (for example, by the 
-  Dockerfile ``USER`` command). If you need to run ``yum`` for some reason, 
-  use ``sudo``.
 * Your app should bind to ``127.0.0.1``, *not* ``0.0.0.0``, and it should serve
   on port 9000.  The Edge machinery will respond to requests on port 8888 and 
   forward them to your app.

Core/Streamlit/Dockerfile

@@ -17,7 +17,7 @@
 
 # First stage
 
-ARG BASE_IMAGE=quay.io/enthought/edm-centos-7:3.4.0
+ARG BASE_IMAGE=quay.io/enthought/edm-centos-7:latest
 
 FROM $BASE_IMAGE as stage_one
 

Core/Streamlit/README.md

@@ -76,8 +76,7 @@ collecting environment variables set by Edge when the container is launched.
 
 When developing locally, it's also convenient to have an EdgeSession.  You
 can get the "ci" module to inject the appropriate environment variables, so
-that your ``EdgeSession()`` call will work with ``python -m ci run`` and
-``python -m ci preflight``.  
+that your ``EdgeSession()`` call will work with ``python -m ci run``.  
 
 To do so, follow this procedure:
 
@@ -86,8 +85,8 @@ To do so, follow this procedure:
   ``"https://edge.enthought.com/services/api"``.
 * Define EDGE_API_ORG in that file.  This is the "short name" displayed in
   the URL bar when you log into an organization, for example, ``"default"``.
-* Define EDGE_API_TOKEN.  You can get one of these by going to the
-  ``/hub/token`` endpoint on the Edge server.
+* Define EDGE_API_TOKEN.  You can get one of these from the ``My Profile``page
+  in the Edge UI.
 
 Be sure *not* to check the "dev_settings.json" file into source control, as it
 contains your API token.
@@ -106,9 +105,6 @@ the prefix from requests, handling the OAuth2 login flow, pinging JupyterHub
 for container activity, and more.  But, there are a few guidelines you will
 need to follow in your own Dockerfile.
 
-* Don't change the user to anything other than ``app`` (for example, by the 
-  Dockerfile ``USER`` command). If you need to run ``yum`` for some reason, 
-  use ``sudo``.
 * Your app should bind to ``127.0.0.1``, *not* ``0.0.0.0``, and it should serve
   on port 9000.  The Edge machinery will respond to requests on port 8888 and 
   forward them to your app.