Fixed Documentation

Author: Freekers

README.md

@@ -8,16 +8,18 @@ Before you can use/run the image, you need to perform a one-time configuration,
 
 To do so, you first need to [download Statsgen 2 to your local computer](https://github.com/Freekers/statsgen/releases/download/v1.9.3/statsgen2_v1.9.3.zip). Statsgen2 can be run on Windows (native) or on Linux using Wine. If you're on Linux, you probably need to use `winetricks` to install `vcrun6`.
 
-- Unzip the contents of the zipfile to a known location, for example C:\statsgen2
+- Unzip the contents of the zipfile to a known location, for example C:\statsgen
 - Next, open statsgen2.exe and go to Run --> First Time Configuration and follow the onscreen prompts.
-- You can choose to either run the Statsgen2 Docker on the gameserver itself or FTP the logfiles over, if you're planning on running the Statsgen2 Docker on a remote ('homepc') machine.   
-Should you run this Docker container on the same machine as the gameserver, uncomment the volume mount pointing to your gameserver's logfile.
+- You can choose to either run the Statsgen Docker on the gameserver itself or FTP the logfiles over, if you're planning on running the Statsgen Docker on a remote ('homepc') machine.   
 - Make sure to complete the entire setup wizard, including the upload of the image packs.
 - Once the setup wizard is done, you return to the main application screen. Feel free to change the sttings more to your liking, for example change the run schedule. 
-- When you're done, close Statsgen 2.
+- When you're done, close Statsgen.
 - Now open the statsgen2.ini file with a text editor such as Notepad(++) and find/replace all directories with the following location: `Z:\root\statsgen\drive_c\statsgen`
-- Save the file and copy over the **entire** statsgen2 directory, i.e. C:\statsgen2, to your Docker host, for example `/opt/statsgen2`.   
+- Save the file and copy over the **entire** statsgen directory, i.e. C:\statsgen, to your Docker host, for example `/opt/statsgen`.   
 Make sure to update the path accordingly in the docker-compose.yml.
+- **Optional:** Should you run this Docker container on the same machine as the gameserver, then make sure to create a hardlink to your gameserver's logfile like so:  
+`ln /opt/cod2/main/games_mp.log /opt/statsgen/games_mp.log`  
+Mounting the logfile as a volume Docker container does not work for some reason (I tried). 
 
 # Run
 Use the included docker-compose.yml to start the container.
@@ -26,7 +28,7 @@ Use the included docker-compose.yml to start the container.
 If you need to change anything to your statsgen2.ini configuration file, make sure to stop the Docker container first before doing so.
 
 # Advanced Usage using crontab
-If you want, you can use cron to schedule Statsgen2 to run. To do so, add the following line to your docker-compose.yml: `command: -runonce`  
+If you want, you can use cron to schedule Statsgen to run. To do so, you'll have to build the Docker image yourself and add `-runonace` at the end of the `ENTRYPOINT`.   
 This will cause statsgen to start, perform a stats run, then exit and thus the container will stop.  
 Make sure to remove  `restart: always` from the compose file as well, else it will keep restarting infitenly.
 

docker-compose.yml

@@ -5,6 +5,5 @@ services:
     container_name: statsgen
     restart: always
     volumes:
-     - /path/to/statsgen:/root/statsgen/drive_c/statsgen
-     #Uncomment below if running on the same machine as the gameserver
-     #- /path/to/gameserver/games_mp.log:/root/statsgen/drive_c/statsgen/games_mp.log:ro
+     - /opt/statsgen:/root/statsgen/drive_c/statsgen
+     - /etc/localtime:/etc/localtime:ro