curate batteries-included docker image

[fisx]

It would be nice to have a README that lists a few steps to carry out in order to download and start aula in a way that is suitable for production use. This would require work on the README and on the docker image, but we should be able to use the same image for both ci and lightweight production deployment.

Here is what a new user had to do in order to get things partially to work (in German):

git clone --recursive https://github.com/liqd/aula
cd aula
./aula/docker/run.sh
apt-get update && apt-get install libicu-dev --fix-missing
stack install --install-ghc --fast --allow-different-user aula
aula-server
#Handarbeit: Jetzt sollte aula mit einer Fehlermeldung starten und einen
Inhalt für aula.yaml vorschlagen. Den in die Datei kopieren und die
_listenerInterface-Einträge von 127.0.0.1 auf 0.0.0.0 setzen.
export AULA_ROOT_PATH=/liqd/aula
mkdir -p dist/build
aula-init-state --admin=admin --admin-pwd=bla
--terms-of-use=null-terms-of-use.md
aula-server # Warten bis "[INFO] persistence: acid-state (memory)" in
aula.log erscheint.

Das Hauptproblem war, dass wir lange gebraucht haben um rauszufinden,
weshalb Dinge nicht funktionierten. Es gab wenig Rueckmeldung was gerade
warum gemacht wird und wie lange es brauche  wuerde.

[TobiGa]

Hello,

is this still an issue?

I wanted to give it a try and managed to get docker to run with the code above by adding

• tagged-0.8.5
• transformers-compat-0.5.0.4
  to extra-deps in the stack.yaml

Just now i cant login with the user i tried to create with aula-init-state.

I would add this to the README.md but i would want to fix this first.
Unfortunately i have no idea how to fix it, could you point me the right direction maybe?

[fisx]

First of all, see #1042

Having that said: cool that you are playing with this, and it can definitely be put to use even with the current project status.

As for your issue with aula-init-state, I would need more details. Can you paste a few more details of what you are doing and what is happening in response? Off the top of my head I think this approach should work fine.

[TobiGa]

I was running aula-init-state, then aula-server and it seemed like the user wasnt saved.

Anyhow, i got it to work like so:
I checked out v0.33.1 where the dependencies are correct, and when i got the aula-server running, make content did provide me with a username and password :)

Id also be interested in the current Project Status, for sure i think its a great idea!