ohnotnow / cronmon Goto Github PK

Following containers fails to start:

• cronmon_app
• cronmon_migrations
• cronmon_queue
• cronmon_scheduler

Logs from container:
DNS fwd/rev mismatch: mysql != cronmon_mysql_1.cronmon_default
mysql [172.25.0.2] 3306 (?) open
Could not open input file: /var/www/html/artisan

Only just noticed I'd missed that facility out - oops. Should any member be able to delete a team they are on - or only admins, or only the person who created it? And should all the associated jobs be removed, or just have their team nulled but left in the system?

Hey, when I go to /admin/job or /admin/team and I see all Jobs/Teams, there is no button to create a new job or team. There is a button in the overview to create a new job and a button under my account for creating a new team. Are the other buttons just missing?

Hi how do you go about configuring a task to run a script?

thanks

If I try to run composer install with a newer (and supported) version of PHP, I get an error:

$ composer install
Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Your lock file does not contain a compatible set of packages. Please run composer update.

  Problem 1
    - Root composer.json requires php ^7.3 but your php version (8.0.13) does not satisfy that requirement.
  Problem 2
    - blastcloud/guzzler is locked to version 1.6.0 and an update of this package was not requested.
    - blastcloud/guzzler 1.6.0 requires php ^7.1 -> your php version (8.0.13) does not satisfy that requirement.
  Problem 3
    - fzaninotto/faker is locked to version v1.9.2 and an update of this package was not requested.
    - fzaninotto/faker v1.9.2 requires php ^5.3.3 || ^7.0 -> your php version (8.0.13) does not satisfy that requirement.

Also, your documumentation makes mention of SQLite3 support, but does not detail anywhere what combination of environment variables in .env will enable this functionality. I'd suggest that documenting all the values in .env would be a valuable exercise for letting new users know how to configure it.

Hi there!, this is a very useful tool!, I've been using it to monitor scheduled jobs from other Laravel apps and multiple scripts I have. One thing I haven't been able to do is to monitor jobs that run only on weekdays (w/o having to set up a grace period of 2 days).

Is there a way to do this?
Edit:
I'm on version 1.1.0