Cron

[nibra]

1. Summary

Currently there is no easy way to execute automated scripts in Joomla! without the proper server technology.

This proposal aims to define a way to enable integrators/administrators to manage cronjobs or cronjob-alike behaviours in the Joomla! backend.

2. Why Bother?

Having some kind of automation on web application is really helpful. Joomla! offers a CLI support but no way to execute this files in an automated way.

There are several approaches which put the burden on the developer but make it hard for the integrator/administrator to manage these scripts.

[brianteeman]

This is very out of date

[nibra]

Yes, and although it has been here for two years now, it was not the base for the scheduler. Shame on us.

[brianteeman]

well the whole way that the rfc is actually hidden inside a pull request is hardly very friendly

[nibra]

That's true.
We need an appealing user interface for the RFCs, ideally as a revival of the Idea Portal.

[brianteeman]

Way way too late. I was suprised that as j5 co-lead you didnt use this for j5. Honestly it was an interesting concept but if the production team dont/wont use it then just face it - its not the right tool

[HLeithner]

Honestly it was an interesting concept but if the production team dont/wont use it then just face it - its not the right tool

It's not true that production doesn't want to use it, but as we already found out it's not user friendly. Also you need a person who maintain all prs and find the point in time to bring it to a vote in production. External participation is also really limited looking at #29 it's the most important rfc or at least should be for people who want's a more restrictive cms further development but only a handful of people care.

[brianteeman]

only a handful of people care.

correction
only a handful of people know about the rfc site or how to read it

[HLeithner]

correction only a handful of people know about the rfc site or how to read it

It's hard to communicate this, iirc there was a magazine article there was production notes (and motion) for the rtc #29 I posted a link in every discussion where it would be relevant. But yeah a github repo is not the best please for discussion but in the end it's used by so many other projects I don't understand why we fail with this process.

[brianteeman]

always best to lead by example which is why I was suprised it wasnt used for the j5 planning. as it wasn't (for whatever reason) then this entire site should be closed as a "tried and failed". Nothing wrong with adopting a fail early, fail often policy