Repository navigation
Cron Jobs UX Suggestion #1155
Closed
justiceakorede
started this conversation in
Ideas
Replies: 2 comments 1 reply
|
That's awesome, Good Job Stefan |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Another suggestion regarding the Cron Jobs section.
Currently, when creating a cron job, the user must first select a container:
“Select a container in which the script will be executed”
This may be confusing for users coming from other hosting panels such as cPanel or Plesk, where they generally just enter the cron command and schedule without having to think about containers.
For example, a customer may see options such as:
and not know which container they are actually supposed to choose.
I think the UX could be improved by making the container selection context-aware.
Since users currently can’t have multiple web servers configured per domain and the web server is configured at the account level, OpenPanel already knows which web server the account is using.
For example, if an account is configured to use Nginx, there may not be much value in showing OpenLiteSpeed/OpenResty web-server containers as possible choices for that account’s cron job.
The container list could therefore be filtered based on the account’s configuration, or OpenPanel could automatically select the appropriate container.
For example:
Account uses Nginx
Container: PHP 8.3
(Automatically selected based on the account configuration)
Instead of showing unrelated containers such as OpenLiteSpeed, OpenResty, etc.
If there are plans to eventually support selecting different web servers per domain, then showing those additional web-server containers could make sense in the future. But with the current account-level web-server configuration, I think the UI should reflect that and only present relevant choices.
Another approach could be to have a Simple and Advanced mode:
Simple
Advanced
There could also be a small “Which container should I choose?” guide on the page explaining the common scenarios.
For example:
Which container should I choose?
For WordPress/PHP cron jobs, OpenPanel will automatically select the PHP container configured for your account.
For custom applications, use Advanced Mode to select the container where the command and required runtime are available.
I think this would make the Cron Jobs feature much easier for normal hosting customers while still retaining the flexibility that OpenPanel’s container architecture provides.
It could also reduce support tickets, because customers wouldn’t have to understand OpenPanel’s container architecture just to create a normal WordPress/PHP cron job.
All reactions