Eventually, the following opam pin add commands worked for me:
$ opam pin add eliom https://github.com/ocsigen/eliom.git
installed eliom.6.5.0
$ opam pin add ocsigen-toolkit https://github.com/ocsigen/ocsigen-toolkit.git
installed ocsigen-toolkit.2.0.0
$ opam pin add ocsigen-start https://github.com/ocsigen/ocsigen-start.git#master
installed resource-pooling.0.5.2
installed ocsigen-start.1.2.0
I didn’t find https://github.com/ocsigen/ocsigen-start/tree/1.1 , so I used https://github.com/ocsigen/ocsigen-start/tree/master , as the opam file indicates version: "1.2.0"
I could do the following:
$ eliom-distillery -name web1 -template os.pgocaml
$ make db-init && make db-create && make db-schema
But I could not get the application launched (see the let%server _ function in the in web1.eliom file):
$ make test.byte
js_of_eliom -w +A-4-7-9-37-38-39-41-42-44-45-48 -jsopt +base/runtime.js -ppx -ppx "ocsigen-i18n-rewriter Web1_i18n" -c -package lwt_ppx -package js_of_ocaml-ppx -package js_of_ocaml-ppx.deriving -package ppx_deriving.std -package ocsigen-start.client -package base -g web1.eliom
File "web1.eliom", line 81, characters 38-51:
Error: Unbound module Lwt_log
Makefile.os:284: recipe for target '_client/web1.cmo' failed
make: *** [_client/web1.cmo] Error 2
EDIT :
In the generated file web1.eliom (for app web1), I commented out the let%server _ function that seems related to debug, and I could have the make test.byte command working and a site accessible at localhost:8080 .
However, the menu is not enabled (exactly as the situation I described when I opened this topic).
…
Eventually, after some F5/refresh browser, or some magic, the menu has been enabled 
…
EDIT2
In fact, ESC stopped the tab process (locally or with the server) but it also froze the menu.
And I got no error message in browser console.
So I don’t know yet what really happened.
…
The problem with machine was when using a vpn to connect to (:8080).
There was no problem when doing the same make test byte directly on the machine (CLI and browser to get to localhost:8080).
Again it was not five minutes to get up and running but many hours instead.
However, it seems to work enough correctly with the last ocsigen-start.1.2.0 package and I can begin to learn how to customize this setup!
Thanks.
About the opam pin add commands
Previously, I tried to do the opam pin add commands you gave but it failed:
$ #opam 2.0.2
$ opam pin add -n -y eliom git@github.com:ocsigen/eliom.git#6.5.0
Processing: [eliom.6.3.0: git] # ???
[ERROR] Could not synchronize /home/test/.opam/4.06.1_ocsigen/.opam-switch/sources/eliom from
"git+ssh://git@github.com/ocsigen/eliom.git#6.5.0":
"/usr/bin/git fetch -q" exited with code 128
[ERROR] Error getting source from git+ssh://git@github.com/ocsigen/eliom.git#6.5.0:
- git+ssh://git@github.com/ocsigen/eliom.git#6.5.0
as well as for the other packages:
$ opam pin add -n -y ocsigen-toolkit git@github.com:ocsigen/ocsigen-toolkit.git#2.0.0
$ opam pin add -n -y ocsigen-start git@github.com:ocsigen/ocsigen-start.git#1.2.0
@Jean_Dutier
Where does the syntax of your commands come from?
What is the -n for? (the -y seems enough for installing packages)
Can you describe your setup that make them working?
About the current ocsigen-start package in the opam repository
Here are two tests I’ve done in parallel with the current package in the opam repository, which is the situation of any person trying to use ocsigen-start without all the information of this topic.
Setup: Linux Debian 8/Jessie with a fresh opam 2.0.2 setup on a 4.06.1 and a 4.07.1 switches.
Result : they both failed for different reasons (eliom or js_of_ocaml_compiler).
@Vincent_Balat and @Jean_Dutier: do you agree that it seems more than necessary to be able to put a flag on the ocsigen-start package in the opam repository and on the ocsigen-start website to indicate that opam won’t install correctly the ocsigen-start package and that the above commands should be used instead until the repository is updated?
@AltGr: do you know how to tweak opam 2.0.2 for doing that? Can the opam team consider to add this flag feature?
Details: Tests for installation of ocsigen-start with current ocsigen-start package in the opam repository
$ #Ocaml 4.07.1
$ opam switch create 4.07.1
$ opam depext ocsigen-start
$ opam install ocsigen-start
#=== ERROR while compiling eliom.6.3.0 ========================================#
# context 2.0.2 | linux/x86_64 | ocaml-base-compiler.4.07.1 | https://opam.ocaml.org#91c7f189
# path ~/.opam/default/.opam-switch/build/eliom.6.3.0
# command ~/.opam/opam-init/hooks/sandbox.sh build make
# exit-code 2
# env-file ~/.opam/log/eliom-27721-6cc03f.env
# output-file ~/.opam/log/eliom-27721-6cc03f.out
# ocamlfind: Package `lwt.ppx' not found
# Command exited with code 2.
# Makefile:7: recipe for target 'all' failed
# make: *** [all] Error 10
$ #Ocaml 4.06.1
$ opam switch create 4.06.1
$ opam install ocsigen-start
#=== ERROR while installing js_of_ocaml-compiler.3.3.0 ========================#
# path ~/.opam/4.06.1_ocsigen/.opam-switch/build/js_of_ocaml-compiler.3.3.0
# command /usr/bin/install -m 0644 /home/test/.opam/4.06.1_ocsigen/.opam-switch/build/js_of_ocaml-compiler.3.3.0/_build/install/default/lib/js_of_ocaml-compiler/js_of_ocaml_compiler.cma /home/test/.opam/4.06.1_ocsigen/lib/js_of_ocaml-compiler/js_of_ocaml_compiler.cma
# exit-code 1
# env-file ~/.opam/log/log-28544-0280a2.env
# output-file ~/.opam/log/log-28544-0280a2.out
