Automating first setup

[emv33]

I am working on a Docker image to install aowow “automatically”. It looks like the php aowow --setup command is necessary to be run manually, and is not able to be automated. Can a feature be added so the data required can be read from environmental variables, or any other non-interactive method? Alternatively, can you tell me where the information required by this setup process can be put by an automatic process for aowow to read it?

[Helias]

I did some minor job about docker setup and, I did not run php aowow --setup, for the configuration I printed them into a config.php file https://github.com/Sarjuuk/aowow/pull/442/changes#diff-e6a664f5616e73ffd8d5cf11850c5c3cb20b7dfe4dafee8caeb94a29d16334f4R33

You can be inspired by the bash script and see how I run the setup without it

[emv33]

That's helpful. I am now generating it using that template. Still, you need to run the setup step to fill the aowow tables it seems. I was under the impression that aowow read TDB directly but it seems it does not.

[Sarjuuk]

Docker is on my todo list.

[emv33]

I am working on (and almost done) with a docker script that does everything with no user intervention beyond telling it where your wow client and TDB sql file are. But there are a few roadblocks to clear first.

[emv33]

Another issue with the setup process is that part of the setup process seems to involve trying to request "/robots.txt" and "/static/css/aowow.css". That's generally okay, but for more complex setups like reverse proxies this will fail. There should be a way of disabling this test.

[emv33]

Alright here it is https://github.com/emv33/aowow-docker

It works fine by itself, but if I could automate the --setup part then it would be extra sweet