- Update run_daily.sh to use compose.yaml env var overrides if present on scheduled jobs, not just first run. Defaults back to config.json values if no override specified.
- update sample compose.yaml with volume mapping to keep config.json, accounts.json, and sessions folder persistent on local machine (e.g., to keep data persistent through updates).
* Improve env var handling, clarify instructions
updateConfig.js will update dist/config.json with any values specified in the docker compose file as environmental variables (env vars). If not specified it will use the default values in src/config.json (the 'usual' place where folks can customize their config).
A user can make changes to an env var (e.g., disabling Scroll Random Results), then docker compose up -d to quickly restart the container with the change.
* minor update to env vars in table
Make sure to change your compose so the updated flattened values work.
* TZ handling for cron runs of the script
docker logs netsky should now show the proper time zone for script runs that were initiated via cron schedule.
* Script will run on container start, and continue to run daily at 5:00 am.
The goal of this update was to add in-built cronjob support so that the script runs immediately on container start, then will schedule the script to run the daily at 5:00 am without requiring the user to manually create a cronjob. After starting the container and completing the first run, the container should remain active (running) but idle until the next scheduled run. Ideally, the next step will be to include support for environmental variables that will allow the user to customize when the script scheduled runs occur within the docker compose.yaml.
* added --build to docker compose command instructions
building/rebuilding the image (and the script) may reduce problems if folks make changes to their configs
* Updated the crontab default to run twice daily by default, 5am and 11am
* Update crontab
Newline needed
* Environmental variable support, custom scheduling
This is a massive update that includes docker environmental variable support for all config options. If specified, the custom env var value will supersede the default values in the config.json. You do not need to change the values in the config.json if you set a custom env var. For example, if you have headless=false in the config.json, but set it as true in the compose.yaml, it will run as HEADLESS=true. If you do not specify a particular env var, the script will automatically use the default value. Please test and contribute wherever possible!
* Fix scheduled runs, tidied up readme
* timezone support
Minor adjustment to attempt to fix timezone env var support
* Run on start, npm script env
Hopefully two fixes here, the container should again, by default, run on start, then continue per schedule. This defaults to true; however, can be optionally over-ridden in the compose.yaml with the env var RUN_ON_START=false. If set to false, the script should only run on the specified cron schedule. I also passed the TZ write into the npm start command, rather than just the container overall so it should show the proper time.
* Keep docker running after run_on_start to wait for cron
Accidentally set it up like a run_once, this should keep the container active after run_on_start to wait for the next schedule.
* improve order of cmd
This should (1) set time zone for script, (2) run once if set, then (3) idle for scheduled cron job. It was a little hacky before, this should be tidier.
* updated compose to auto-restart container
Noticed the container was exited this am, likely after automated updated to system, adding restart: unless-stopped to compose should keep container running in such circumstances.
* Update env vars in readme
- Fixed browser generating mobile browser after the first account
- Hopefully fixed script erroring after not finding parent promotions
- Added support for MacOS (Thanks @alecm858)
- Made some changes to search result scrolling
