Download the PHP package gitsbt/waylume-sdk without Composer
On this page you can find all versions of the php package gitsbt/waylume-sdk. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download gitsbt/waylume-sdk
More information about gitsbt/waylume-sdk
Files in gitsbt/waylume-sdk
Package waylume-sdk
Short Description Waylume SDK for adding multi-page navigation guides to PHP applications.
License proprietary
Homepage https://waylume.app
Informations about the package waylume-sdk
Waylume SDK — PHP
日本語
Add multi-page Waylume navigation guides to PHP-rendered websites, including Laravel, Symfony, WordPress, and plain PHP applications.
Requirements
- PHP 8.1 or newer
- JSON and Sodium extensions
- A Waylume site license for production use
Install
Local development without credentials
On localhost, 127.0.0.1, and the IPv6 loopback address, no Waylume license,
credentials, proof endpoint, or local Waylume server is required. Use
SdkMode::Auto with an internet connection.
Credentials and the proof endpoint in the next two sections are required only when the site is viewed on a non-local hostname.
1. Configure production credentials
Store the credentials issued in the Waylume dashboard on your server. Never expose the private key in HTML or browser JavaScript.
The dashboard exports private_key as the Base64 body only, without
-----BEGIN PRIVATE KEY----- / -----END PRIVATE KEY----- lines. Pass that
value directly to LicenseProofSigner; do not add PEM markers. The environment
variable names shown here are examples and may be changed to match your app.
2. Add a production proof endpoint
Create a server-side POST endpoint such as /api/waylume-proof:
Replace app.example.com with the licensed hostname stored in your existing
application configuration. Do not accept an arbitrary hostname supplied by the
browser.
3. Mark guide targets
The data-waylume value must match the flow step's target.
4. Define and register flows
Flows can also be loaded from JSON:
5. Publish the browser loader
Copy the packaged browser loader to a public directory during deployment.
6. Render the bootstrap
Render the bootstrap on every page that participates in a guide:
Place this before </body> in your shared layout:
7. Add a launcher or navigation trigger
Launcher listing every registered flow:
Trigger for one specific flow:
Pass only trusted markup to children; it is intentionally not escaped.
Multi-page flows
Set expectedUrlPattern on the first step and on steps that wait for
navigation. Only same-site paths beginning with / are accepted. Render the
bootstrap in the shared layout so the guide can resume after a full page load.
For Inertia, Livewire, or another client-side router, call this after a route change:
Main APIs
FlowFactory: define and validate flowsFlowRegistry: register and retrieve flowsLocaleResolver: resolve translated labels and instructionsWaylumeConfig: configure licensing, host, mode, and proof endpointLicenseProofSigner: create short-lived Ed25519 license proofsWaylumeRenderer: render the bootstrap, launcher, and navigation trigger
The browser emits waylume:step-change, waylume:flow-complete, and
waylume:flow-skip events.
License
Production use requires a Waylume site license. See LICENSE and waylume.app.
All versions of waylume-sdk with dependencies
ext-json Version *
ext-sodium Version *