Simulating traffic in localhost development environment

[Aramaech]

In my local development environment, I keep getting that good ol "background tasks are not running" warning. 

The go-to fix seems to be the cron job, which I'm capable of setting up, but the reason I haven't is that doing so requires giving terminal lots of permissions that I don't want to give it, out of general simplistic security concerns.  Not that it's pivotal or anything but part of me thinks it would be nice to have the local dev build run as closely to the production environment as possible.

So I've been tinkering with workarounds.  First I wrote an Applescript that just pops open the local site in a minimized browser window and keeps refreshing it every 3 seconds over and over for some amount of time that you can choose when the script starts.  I thought that would simulate traffic effectively enough, but it didn't seem to get rid of the warning message.

So next I tried going to the AdminCP > Advanced Settings > Tasks field and clicked on "Use cron" which presents you with 2 cron tasks that you're supposed to set to run once a minute.  So I tried making another Applescript that just ran those once a minute through the terminal in the background.  No dice.

Next I went back to the AdminCP > Advanced Settings > Tasks field and clicked on "Use web service".  It gives you a URL that you're supposed to have Easycron or some comparable site send out every minute.  Instead I just used another Applescript and had it pass that URL to a browser window once a minute. Still no go...

Does anyone know how to properly simulate traffic, or a cron job, or an Easycron url?
Are any of the things I'm doing supposed to work, and maybe just aren't because of an overlooked bug or misstep or something?
 
 

Edited March 20, 2020 by RobotMonkeyHæd

[bfarber]

Note that it can take some time for the message to go away once you switch to cron (or your traffic increases). It tells you this in the message, and suggests ignoring the message for a day once you've addressed the issue.

In other words, when you set up the cron (or a traffic simulator) the message doesn't just immediately go away on its own.

[Aramaech]

oooohhhh ok, so what I'm doing should actually be working then, it's just the message itself hanging around, which is easy.  Awesome, thanks!