Here is an example of a command line (where XXXX would be your port number), but don’t run it yet, it would be for later! jupyter lab -port XXXX -ip 0.0.0.0 -no-browserĪlternatively, you can put this directly into a configuration file and just run the command jupyter lab (or jupyter notebook): # Create a configuration file and edit it There are two ways to do this, either you specify all this in your command when you run Jupyter, or you create a configuration file: Command line
So you have to specify to Jupyter not to open a window on the server and to open Jupyter on a specific port (if needed). The problem with launching Jupyter on a server is that you will have to make an ssh bridge between your machine and the server to open Jupyter directly on your internet browser. This should replace the (base) with the name of your environment. To save and manage your environment, see at the end of this tutorial.įor simplicity, I also recommend that you add the line conda activate project_v0 to your bashrc so you don’t have to activate it every time. Here is an example of an environment I created for my Ph.D.:
Nb_conda_kernels package in each of your environments, which will allow you to switch from one environment to another, directly from your notebooks. Then install all the packages you need, especially jupyter (+ jupyterlab if you prefer from basic notebooks, which is my case). So here is how I work on my side, I create an environment with the name of my project and a version (for example project_v0): conda create -n project_v0 The problem is that when you are not familiar with the environment you don’t necessarily make a backup and it is sometimes difficult to get back to something functional! By experience, it happened to me several times to break this environment without being able to go back and to have to finally reinstall everything.
I do not recommend that you use your base environment. If you want to know more, click on the link in the title. conda config -add channels conda-forgeĬonda config -set channel_priority strict This step is completely optional, but it allows to facilitate the installation of future packages that would not be the basic channel of conda.
#How to install jupyter lab windows update#
Then you can start over or forget about Miniconda forever :pĬonda-forge and update your installation (optional but I recommend) If you are not happy, fucked up any step or you are scared… that happens… Just remove the folder miniconda3 ( rm -r /data/login/miniconda3 or the path you put at the installation step) and then remove the lines that were added in your bashrc.
0 kommentar(er)
