mirror of
https://github.com/jupyterhub/jupyterhub.git
synced 2025-10-18 07:23:00 +00:00
further simplified the words in the document
I made changes to some of the words used by simplifying them to ensure that all users can easily understand the document.
This commit is contained in:

committed by
GitHub

parent
9c044e863a
commit
9fcaf8df52
@@ -140,7 +140,7 @@ By default, in a JupyterHub deployment, each user has one server only.
|
||||
JupyterHub can, however, have multiple servers per user.
|
||||
This is mostly useful in deployments where users can configure the environment in which their server will start (e.g. resource requests on an HPC cluster), so that a given user can have multiple configurations running at the same time, without having to stop and restart their own server.
|
||||
|
||||
To allow named servers, use this:
|
||||
To allow named servers, include this code snippet in your config file:
|
||||
|
||||
```python
|
||||
c.JupyterHub.allow_named_servers = True
|
||||
@@ -158,13 +158,13 @@ as well as the admin page:
|
||||
Named servers can be accessed, created, started, stopped, and deleted
|
||||
from these pages. Activity tracking is now per server as well.
|
||||
|
||||
To limit the number of **named server** per user by setting a constant value, use this:
|
||||
To limit the number of **named server** per user by setting a constant value, include this code snippet in your config file:
|
||||
|
||||
```python
|
||||
c.JupyterHub.named_server_limit_per_user = 5
|
||||
```
|
||||
|
||||
Alternatively, to use a callable/awaitable based on the handler object, use this:
|
||||
Alternatively, to use a callable/awaitable based on the handler object, include this code snippet in your config file:
|
||||
|
||||
```python
|
||||
def named_server_limit_per_user_fn(handler):
|
||||
|
Reference in New Issue
Block a user