![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
@slay-pics/slay-q-server
Advanced tools
Slay Q Server is the server component of Slay Q, a queue and background job management system inspired by Inngest. It's in production use on https://slay.pics for managing all of our media processing, notifications and other services.
This is the server component of Slay Q.
This is a thin wrapper around the super awesome Graphile Worker which is doing all of the heavy lifting.
Install package:
# npm
npm install @slay-pics/slay-q-server
# yarn
yarn add @slay-pics/slay-q-server
# pnpm
pnpm install @slay-pics/slay-q-server
# bun
bun install @slay-pics/slay-q-server
Run:
npx slay-q-server /path/to/slay-config.json
Run without installing:
npx @slay-pics/slay-q-server@latest /path/to/slay-config.json
The first time you run the server, two migrations will be run:
graphile_worker
will be created. This schema is required for Graphile Worker to function.slayq
will be created. This contains all the tables and functions SlayQ
needs to do its housekeeping.public
schema. This is necessary for Supabase as you cannot access other
schemas with their js libs.You must have a few environment variables defined prior to launching slay-q-server
:
SLAY_Q_DATABASE_URL
- The connection string url for your postgres database.SLAY_Q_SECRET
- The secret used to sign events posted to your app's slay-q receiver endpoint.SLAY_Q_CRON_URL
- The URL to your slay-q receiver endpoint that will receive cron events.To run slay-q-server
, you need to create a config file first:
{
"queues": {
"mail": {
"concurrency": 4
},
"messaging": {
"concurrency": 6,
"alias": [
"dispatch",
"ready"
]
},
"interactions": {
"concurrency": 1,
"alias": [
"reconcile",
"discord"
]
},
"housekeeping": {
"concurrency": 2
},
"profile": {
"concurrency": 8
},
"general": {
"concurrency": 10
}
}
}
We are essentially defining a variety of queues and their level of concurrency (the number of tasks that can run at once in the queue). Additionally, we are specifying aliases for these queues. These aliases are only provided to help keep things organized on the client side of things.
Published under MIT License.
FAQs
Slay Q Server is the server component of Slay Q, a queue and background job management system inspired by Inngest. It's in production use on https://slay.pics for managing all of our media processing, notifications and other services.
The npm package @slay-pics/slay-q-server receives a total of 2 weekly downloads. As such, @slay-pics/slay-q-server popularity was classified as not popular.
We found that @slay-pics/slay-q-server demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.