UPDATE: I have checked app/Console/Kernel.php, and the schedule function only has the default comment. No scheduled jobs. I also went to the app directory at var/www/laravel where the app lives, and ran php artisan schedule:list which returned 'No scheduled tasks have been defined.' There is also nothing in /var/spool/cron/crontabs. This is all the clarity I can provide, thus why I am asking the question if someone else had a similar experience.
I Googled, I searched here, I didn't find my answer. If this is a duplicate to anyone, I apologize.
I have setup a Laravel application with a few different services that consume external APIs, does some basic transformations, then stores to a MySQL database, local to the server. Then, I also have some services that take that new data, transforms the data further, and adds to even more tables.
There's nothing wrong with any of these services, they work as intended, and currently are connected to buttons, via web routes, on a basic UI for testing. The plan is to move these to scheduled tasks, but I've not done anything with automating tasks so far.
However, this is where the question comes in. Does Laravel automatically run services in an app/services directory, by default in production?
I ask because I've never seen my database grow overtime automatically, in local Dev. However, once deployed to a DigitalOcean droplet, I am now seeing MySQL tables, that are connected to those services, growing on their own without my interaction. Again, I've done nothing directly with scheduling anything.
I'd show code, but there's no issues functionally. Just buttons connected to routes, routes to controllers, controllers calling services (app/services) and methods within those services... Any help would be appreciated.