Improve the agola demo by using docker compose:
* Use a dedicated bridged network
* Adapt the agola and gitea config for the new setup
* Also add a README.md (with the same contents of the tryit
documentation on the agola site, that will be updated).
The authentication won't return a jwt token but will use cookies.
The token auth will be used only for api calls with the admintoken or
user token.
Two cookies are returned, the primary auth cookie (httpOnly) and a
secondary cookie used for client side implementation of logout.
Also implement CSRF and use of secure cookies (with a config option to
disable them)
since the executor are usually run separately from the other "base" components,
make this explicit removing "all" and adding an "all-base" virtual component
that will start all the components except the executor.
* Delete the command and it's rule in the Makefile
* Don't use it inside gitserver and remove related config option (also from
examples)
* Remove webhook parsing from agolagit gitsource
Also if they are logically part of the runservice the names runserviceExecutor
and runserviceScheduler are long and quite confusing for an external user
Simplify them separating both the code parts and updating the names:
runserviceScheduler -> runservice
runserviceExecutor -> executor
`lts` was choosen to reflect a "long term storage" but currently it's just an
object storage implementation. So use this term and "ost" as its abbreviation
(to not clash with "os").
Simone Gotti