Merge branch 'patch_1' into 'master'

Add more info on each option

See merge request !13

docs/site/ce_guide.md

@@ -11,7 +11,7 @@ This guide provides instructions on setting up JAliEn Computing Element (CE) by
 
 ## Option 1: Running from CVMFS
 
-This approach only requires CVMFS and a valid Grid certificate or a user/host token in ```~/.globus```.
+This approach only requires CVMFS and a valid Grid certificate or a user/host token in ```~/.globus```. It is the simplest approach for getting a CE up and running, but configuration is limited to the options given in the config files. 
 
 1. Ensure environment path for the proxy certificate is set. See output from ```voms-proxy-info -path``` to get the full path, for example:
 
@@ -25,6 +25,8 @@ This approach only requires CVMFS and a valid Grid certificate or a user/host to
     ~$ alienv enter JAliEn
     ```
 
+Note that it is assumed here that `alienv` is already in path. If not, it can be found at `/cvmfs/alice.cern.ch/bin/alienv`.
+
 3. Run the CE:
 
     ```console
@@ -44,8 +46,7 @@ Overview of the config files, and their default values, can be found [here](http
 !!! info "Requirements"
     This approach requires compile tools such as JDK11+ be available.
 
-This approach gives access to the latest CE changes without waiting for a new tag to be pushed to CVMFS (but note that JobAgents will still run from CVMFS). 
-It also allows for more overrides, such as for the agent startup script (at own risk).
+This approach gives access to the latest **CE** changes without waiting for a new tag to be pushed to CVMFS. JobAgents will still run from CVMFS, but their startup script may now be modified - allowing for changes such as what variables are exported, scripts are run before start, and containers may also be enabled/disabled as desired. Other in-code overrides are also possible (at own risk). As with the first option, a valid Grid certificate or a user/host token in ```~/.globus``` is required.
 
 1. Clone the JAliEn Git repository: