Server vs local

[fnattino]

Right now this repository needs to be cloned on both server and local sides. It would be ideal if one would have to dowload it only locally, so that users can tune parameters and scripts (dask configuration files, job submission scripts, environment file), with these being pushed to the supercomputer.

Also, right now it is not super clear which components are needed for the local setting and which for the remote:

• the environment requirements for the local system are not specified, and one can mistakenly assume the environment.yml is for local settings. For this, we should improve the packaging of the installation/deployment scripts and maybe place the environment file is some subdirectory.
• the platform config file (needed locally) is stored together with the config file of Dask/Jupyter (needed remotely)

[fnattino]

Related: the environment file here should probably only contain the minimal dependencies (Jupyter, Dask, dCache-related tools). User-specific packages could be added by modifying the local environment file, if this is then pushed to the remote for configuration. A different question is can we support multiple environments (#40 )?