Thanks to everyone for testing! We now have jupyterhub 0.8rc2 out with
several rough edges polished, and should be ready for a final release of
0.8 by the end of the month.

-Min

On Sun, Aug 20, 2017 at 3:00 PM, MinRK <[email protected]> wrote:

> JupyterHub 0.8 is preparing for release, an we would love your help
> testing.
>
> You can get the beta with:
>
> pip install --pre jupyterhub
>
> Always make sure to backup your database before upgrading JupyterHub.
>
> There are lots of bugfixes and improvements here. Probably most
> significant is the change to OAuth from cookies for authenticating access
> to single-user servers. This change means that it is important to upgrade
> the version of JupyterHub in both the singleuser context and the Hub
> context at the same time, if the two are different (e.g. in containers). If
> you are using a container-based image, ensuring you have the right version
> of JupyterHub should generally be as simple as:
>
> pip install jupyterhub==version
>
> in your Dockerfile.
>
> Other highlights include:
>
>    - support alternate proxy implementations, such as Kubernetes ingress
>    - enable persisting encrypted authentication state, such as
>    credentials from OAuth services to pass to single-user servers
>    - preliminary (API only) support for multiple named servers per user
>    - support token-authenticated access to single-user servers
>
> There are lots of other things to see in the changelog
> <https://jupyterhub.readthedocs.io/en/latest/changelog.html>.
>
> Thanks to everyone who helped out!
> ​
>

-- 
You received this message because you are subscribed to the Google Groups 
"Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jupyter/CAHNn8BXopQXob1iHK_g0qE6Kw%3D95wFOG1WQwObZfVQEow9uAyg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to