silverstripe-queuedjobs | provides interfaces for scheduling jobs | Cron Utils library

by symbiote PHP Version: 5.0.0 License: BSD-3-Clause

X-Ray Key Features Code Snippets(3)Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | silverstripe-queuedjobs Summary

silverstripe-queuedjobs is a PHP library typically used in Utilities, Cron Utils applications. silverstripe-queuedjobs has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

The Queued Jobs module provides a framework for SilverStripe developers to define long running processes that should be run as background tasks. This asynchronous processing allows users to continue using the system while long running tasks proceed when time permits. It also lets developers set these processes to be executed in the future. The module comes with.

Support

Quality

Security

License

Reuse

Support

silverstripe-queuedjobs has a low active ecosystem.

It has 56 star(s) with 74 fork(s). There are 11 watchers for this library.

It had no major release in the last 12 months.

There are 47 open issues and 90 have been closed. On average issues are closed in 174 days. There are 7 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of silverstripe-queuedjobs is 5.0.0

Quality

silverstripe-queuedjobs has 0 bugs and 0 code smells.

Security

silverstripe-queuedjobs has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

silverstripe-queuedjobs code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

silverstripe-queuedjobs is licensed under the BSD-3-Clause License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

silverstripe-queuedjobs releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed silverstripe-queuedjobs and discovered the below as its top functions. This is intended to give you an instant insight into silverstripe-queuedjobs implemented functionality, and help decide if they suit your requirements.

Run a job
Add the fields to the CMS
Gets the edit form
List all tasks in the queue
Process the current page
Handles the beforeWrite event
Quote a field
Get the column content
Get the queue parameter
Completes the job

Get all kandi verified functions for this library.

silverstripe-queuedjobs Key Features

No Key Features are available at this moment for silverstripe-queuedjobs.

silverstripe-queuedjobs Examples and Code Snippets

Example

PHP

Lines of Code : 69

License : Permissive (BSD-3-Clause)

Copy


items = $items;
    }

    /**
     * @return string
     */
    public function getTitle(): string
    {
        return 'My awesome job';
    }

    public function setup(): void
    {
        $this->remaining = $this->items;

        // Set

YML config

PHP

Lines of Code : 33

License : Permissive (BSD-3-Clause)

Copy

SilverStripe\Core\Injector\Injector:
  Symbiote\QueuedJobs\Services\QueuedJobService:
    properties:
      defaultJobs:
        # This key is used as the title for error logs and alert emails
        ArbitraryName:
          # The job type should be

Default Jobs

PHP

Lines of Code : 18

License : Permissive (BSD-3-Clause)

Copy

ArbitraryName:
  type: 'ScheduledExternalImportJob'
  filter:
    JobTitle: 'Scheduled import from Services'

QueuedJobDescriptor::get()->filter([
  'type' => 'ScheduledExternalImportJob',
  'JobTitle' => 'Scheduled import from Services'
]);

Community Discussions

Trending Discussions on silverstripe-queuedjobs

How to fix installation of a package by Composer outside vendor folder

QUESTION

How to fix installation of a package by Composer outside vendor folder

Asked 2020-Mar-30 at 18:44

I am migrating a SilverStripe 3 website to SilverStripe 4 and in that process, I resorted to the silverstripe-ldap module. It comes with a dependency to symbiote/silverstripe-queuedjobs

The problem that I have is that symbiote/silverstripe-queuedjobs has its files installed by Composer in a queuedjobs folder at the same level than vendor, instead of being in vendor like all of the other dependencies.

Is it possible to force it to be installed in folder vendor?

...

ANSWER

Answered 2020-Mar-30 at 18:44

All SilverStripe 3 modules install into the root project folder, rather than into the vendor folder.

In SilverStripe 4 this is still supported, but by default most modules (including all core and supported modules) install into the vendor folder.

If you've still got one in your root folder, you probably are installing an incompatible SilverStripe 3 version of that module. You should check the module on Packagist to find which version is SilverStripe 4 compatible (use ^4.5) and update your Composer constraints.

Source https://stackoverflow.com/questions/60901451

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install silverstripe-queuedjobs

Now setup a cron job:.
To schedule a job to be executed at some point in the future, pass a date through with the call to queueJob The following will run the publish job in 1 day's time from now.

Support

To make sure your job works, you can first try to execute the job directly outside the framework of the queues - this can be done by manually calling the setup() and process() methods. If it works fine under these circumstances, try having getJobType() return QueuedJob::IMMEDIATE to have execution work immediately, without being persisted or executed via cron. If this works, next make sure your cronjob is configured and executing correctly. If defining your own job classes, be aware that when the job is started on the queue, the job class is constructed without parameters being passed; this means if you accept constructor args, you must detect whether they're present or not before using them. See this issue and this wiki page for more information. If defining your own jobs, please ensure you follow PSR conventions, i.e. use "YourVendor" rather than "SilverStripe".

Find more information at: