You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hosts have expressed that the runner/reporter install is tedious. The Hosting Team can try to lessen that with some short-term solutions while more automation is planned (like Lucas' SSH proposal). For example:
In the diff for PR 256 readme.md line 571 there's an example bash script. That bash script could be part of the runner codebase so hosts don't have to make their own, which reduces the install process by one step.
Some other ideas:
The first few install steps after creating a dir (clone repo, cd into dir, rename env.default to .env, edit .env) could be in a script instead of manual, with prompts for entering database creds and other variables rather than having folks edit it with vim.
creating the json and xml and running report.php could be condensed into one file along with cleanup.php
So there could be 3 files that are already in the repo, rather than hosts making the files themselves for cron jobs to call.
This could reduce the amount of steps required, simplify install and testing a little bit for hosts and reduce the amount of time required to set the runner/reporter up.
Thoughts? If folks are on board we can make 3 sub-issues for it.
I'm working on the first idea at today's Contributor Day: an interactive host-tools/setup.sh. It checks the requirements, creates .env from .env.default with prompts (no vim), and tests the database connection before the first run. The second idea, a one-step run and report script, is in #346 for #260.
Activity
iarif4u commentedon Oct 2, 2026
I'm working on the first idea at today's Contributor Day: an interactive
host-tools/setup.sh. It checks the requirements, creates.envfrom.env.defaultwith prompts (no vim), and tests the database connection before the first run. The second idea, a one-step run and report script, is in #346 for #260.Add host-tools/setup.sh to create .env with prompts (#348)