Fix documentation links (#560)

* Fix documentation links

* Allow more time for test

Author: davidbrochart

docs/plugins/auth.md

@@ -1,4 +1,4 @@
-The auth plugin has a special place because almost every other plugin depends on it for security reasons. It is possible to use any auth plugin as long as it follows a defined [API](./#api). Jupyverse comes with three auth plugins: [fps-noauth](./#fps-noauth), [fps-auth](./#fps-auth) and [fps-auth-fief](./#fps-auth-fief).
+The auth plugin has a special place because almost every other plugin depends on it for security reasons. It is possible to use any auth plugin as long as it follows a defined [API](#api). Jupyverse comes with three auth plugins: [fps-noauth](#fps-noauth), [fps-auth](#fps-auth) and [fps-auth-fief](#fps-auth-fief).
 
 ## API
 

docs/plugins/login.md

@@ -1 +1 @@
-`fps-login` implements the login page for [fps-auth](../auth/#fps-auth)'s token authentication.
+`fps-login` implements the login page for [fps-auth](auth.md#fps-auth)'s token authentication.

docs/usage/multi_user.md

@@ -10,11 +10,11 @@ Jupyverse must then be launched in collaborative mode:
 ```bash
 jupyverse --set frontend.collaborative=true
 ```
-The collaborative mode will handle users through the [auth plugin](../../plugins/auth) you have installed, which will provide user identity.
+The collaborative mode will handle users through the [auth plugin](../plugins/auth.md) you have installed, which will provide user identity.
 
 ## Identity provider
 
-The real power of collaborative editing comes with proper user authentication and authorization. Jupyverse comes with several "auth plugins", that will be described below, but you can implement your own. It just has to follow a defined [API](../../plugins/auth/#api).
+The real power of collaborative editing comes with proper user authentication and authorization. Jupyverse comes with several "auth plugins", that will be described below, but you can implement your own. It just has to follow a defined [API](../plugins/auth.md#api).
 
 ### Using fps-auth
 
@@ -24,11 +24,11 @@ It can be enabled by launching:
 ```bash
 jupyverse --set frontend.collaborative=true --set auth.mode=token
 ```
-This uses the token authentication, the same as described in the [single user mode](../single_user/#token-authentication). This means that users don't get a "real" identity, since all they provide is the shared token. For this reason, we call them "anonymous users".
+This uses the token authentication, the same as described in the [single user mode](single_user.md#token-authentication). This means that users don't get a "real" identity, since all they provide is the shared token. For this reason, we call them "anonymous users".
 
 They can still be differenciated, and they will each get assigned a different name e.g. in JupyterLab, but they will all have full access to any resource. For instance, they will be able to open all documents and to execute any code.
 
-You can also disable token authentication in collaborative mode, just as in [single user mode](../single_user/#no-authentication):
+You can also disable token authentication in collaborative mode, just as in [single user mode](single_user.md#no-authentication):
 ```bash
 jupyverse --set frontend.collaborative=true --set auth.mode=noauth
 ```
@@ -43,7 +43,7 @@ In this mode, users have to be registered in a database before logging in. User
 
 ### Using fps-auth-fief
 
-[fps-auth-fief](../../plugins/auth/#fps-auth-fief) uses [Fief](https://www.fief.dev) to authenticate users. Fief itself can be hosted in the cloud or locally, but in any case it runs a separate server, and implements OAuth2 to access Jupyverse.
+[fps-auth-fief](../plugins/auth.md#fps-auth-fief) uses [Fief](https://www.fief.dev) to authenticate users. Fief itself can be hosted in the cloud or locally, but in any case it runs a separate server, and implements OAuth2 to access Jupyverse.
 
 Fief allows to manage users using a dashboard. It supports permissions and Role-Based Access Control (RBAC).
 

docs/usage/single_user.md

@@ -2,7 +2,7 @@ The single user mode is usually meant to run e.g. JupyterLab as a desktop applic
 
 Even though Jupyverse most often runs on a personal computer in this mode, it is not limited to this use case. For instance, if it runs on a network, it could be accessed by other people. It is thus important to limit access to the server, especially considering that Jupyter users can run potentially harmful code.
 
-This is why Jupyverse comes with built-in authentication. Please refer to the [auth plugins](../../plugins/auth) section for more details. The authentication mechanisms below make use of the [fps-auth](../../plugins/auth/#fps-auth) plugin.
+This is why Jupyverse comes with built-in authentication. Please refer to the [auth plugins](../plugins/auth.md) section for more details. The authentication mechanisms below make use of the [fps-auth](../plugins/auth.md#fps-auth) plugin.
 
 ## Token authentication
 
@@ -11,7 +11,7 @@ This is the default mode when launching Jupyverse, just enter in a terminal:
 jupyverse --open-browser
 # same as: jupyverse --set auth.mode=token --open-browser
 ```
-This should open a new window in a browser, and load JupyterLab or Jupyter Notebook, depending on the front-end you chose to install (see [Install](../../install)).
+This should open a new window in a browser, and load JupyterLab or Jupyter Notebook, depending on the front-end you chose to install (see [Install](../install.md)).
 
 If you look at the terminal, you should see among other things:
 ```

tests/test_server.py

@@ -225,7 +225,7 @@ async def connect_ywidget(url, guid):
         model_name = Text()
         ywidget_doc["_attrs"] = attrs
         ywidget_doc["_model_name"] = model_name
-        with anyio.fail_after(2):
+        with anyio.fail_after(3):
             while True:
                 await anyio.sleep(0.1)
                 if str(model_name) == "Switch" and str(attrs) == '{"value":true}':