Download the PHP package sergeybruhin/nova-supportrays without Composer
On this page you can find all versions of the php package sergeybruhin/nova-supportrays. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download sergeybruhin/nova-supportrays
More information about sergeybruhin/nova-supportrays
Files in sergeybruhin/nova-supportrays
Package nova-supportrays
Short Description Laravel Nova 4 tool for working SupportRays («Лучи Поддержки») tickets from the admin panel, as each Nova user's own SupportRays manager account
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package nova-supportrays
nova-supportrays
A Laravel Nova 4 tool for working SupportRays («Лучи Поддержки») helpdesk tickets without leaving the admin panel.
Every Nova user connects their own SupportRays manager account once. After that, each reply, internal note, status change or assignment is made under that person's name, and nobody shares a staff token. The host app can add its own records (the customer, their orders, deep links into its Nova) to every ticket's sidebar.
Used by qskn.ru and peptera.ru.
Features
- Inbox at
/nova/supportrays:- tabs «Ждут ответа», «Мои», «Без исполнителя» and «Все активные», with counts;
- search, and filters for status, priority and «Просрочено» (SLA breached);
- pagination; refreshes every 60 s.
- Ticket page at
/nova/supportrays/tickets/{uuid}:- the thread, with internal notes highlighted, delivery marks («Не доставлено клиенту: …») and attachment downloads;
- a reply or internal note, sent with an
Idempotency-Keyso a double click never posts twice; - status, priority, assignee, category, tags and watchers; the SLA timers; the change history;
- the SupportRays client card, the ticket's custom fields and links;
- the host's own sidebar cards (see Host context);
- «Открыть в Лучах Поддержки»; refreshes every 20 s.
- Menu badge: tickets awaiting a reply, cached 60 s per user. The call has a 3 s timeout, so a slow SupportRays never holds up a Nova page.
- Connecting:
- the login code is emailed to the Nova user's own address;
- the personal integration key is stored encrypted (
nova_supportrays_keys); - «Отключить» forgets it locally.
Requirements
- PHP 8.2+ and Laravel Nova 4.x (built and tested on 4.35).
- SupportRays API v0.2.0+, which adds integration keys (
/org/login/verifywithintegration) and/org/tickets/stats. - Every Nova user who works tickets must be an active SupportRays manager in the organization, with the same email as in Nova.
- The
ph-lifebuoymenu icon comes from a Phosphor icon set registered in the host's Nova. Without one, Nova shows its default icon.
Install
Register the tool in app/Providers/NovaServiceProvider.php:
Decide who may open it with the viewNovaSupportRays gate. Without the gate, every Nova user may,
and SupportRays still checks whether their email belongs to a manager.
Configure
The tool reads the same SUPPORTRAYS_* variables as a host integration that pushes tickets, so a
site that already has one needs nothing extra.
| Variable | Default | |
|---|---|---|
SUPPORTRAYS_BASE_URL |
https://api.supportrays.ru/api/v1 |
API root, including the version |
SUPPORTRAYS_PROJECT_UUID |
— | Required. The project the tool works with; every key is issued for it only |
SUPPORTRAYS_PORTAL_URL |
https://supportrays.ru |
For «Открыть в Лучах Поддержки» links |
SUPPORTRAYS_INTEGRATION_NAME |
APP_NAME Nova |
How the key is named in the manager's SupportRays profile |
SUPPORTRAYS_TIMEOUT |
10 |
Seconds per API call |
To change the menu label (Лучи Поддержки) or the badge cache time, publish the config:
Host context
Bind a SergeyBruhin\NovaSupportRays\Contracts\TicketContextProvider to put the host's own cards
and links in the ticket sidebar. It gets the SupportRays ticket and client, read with the current
user's key, so it only ever describes a ticket that user may see. Nothing comes from the browser.
Paths starting with / open inside Nova; other http(s) links open in a new tab.
How it works
- Connect:
POST /nova-vendor/supportrays/connection/codeasks SupportRays (/org/login/request) to email a code.POST /nova-vendor/supportrays/connectiontrades it (/org/login/verifywithintegration: {name, project_uuid}) for a long-lived key bound to one project and to ticket work only.
- Proxy: only the ticket-work roots
me,tickets,users,tags,clients,projectsandattachmentspass; attachment downloads stream through as files. Anything else is refused before it leaves the server. - Errors:
- a missing, expired or revoked key answers
409 not_connected, and the page shows the connect screen again; - SupportRays' own 401/403 never reaches the browser as such, because Nova's front end would read them as its session expiring or its forbidden page;
- SupportRays being down answers
503, and the page keeps what it has.
- a missing, expired or revoked key answers
- Disconnect: the key is deleted locally. Revoking it in SupportRays needs a full session login, so the user (or an organization owner) does that in the portal profile.
Develop
The pages live in resources/js/pages (Inbox.vue, Ticket.vue) and use Nova's own components.
Feature tests run in the host app, with Http::fake() against nova-supportrays.base_url.
Versioning
SemVer. Tags are vX.Y.Z; hosts require ^0.1.
License
MIT
