Download the PHP package lan-software/lancore-client without Composer

On this page you can find all versions of the php package lan-software/lancore-client. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • 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.
Please rate this library. Is it a good library?

Example code of lan-software/lancore-client

Informations about the package lancore-client

lancore-client

The shared Composer package that every Lan* satellite application uses to talk to LanCore — HTTP transport, SSO authorization-code flow, webhook signature verification, and (opt-in) JWKS-backed ticket-validation.

Environment contract

Every satellite reads the same set of environment variables (defaults in config/lancore.php):

Variable Purpose
LANCORE_ENABLED Master kill-switch (true / false)
LANCORE_BASE_URL Browser-facing LanCore URL (SSO redirects)
LANCORE_INTERNAL_URL Server-to-server URL; falls back to LANCORE_BASE_URL
LANCORE_TOKEN Bearer token minted by LanCore
LANCORE_APP_SLUG Satellite identity (e.g. lanbrackets)
LANCORE_CALLBACK_URL OAuth callback URL registered on LanCore
LANCORE_WEBHOOK_SECRET HMAC-SHA256 key for incoming-webhook verification
LANCORE_ENTRANCE_ENABLED LanEntrance-only opt-in for the JWKS sub-client
LANCORE_SIGNING_KEYS_ENDPOINT JWKS endpoint URL
LANCORE_SIGNING_KEYS_CACHE_TTL JWKS cache TTL in seconds

These env vars are stable across provisioning paths — the package itself does not care how they were populated.

Declarative provisioning via LanCore config

When LanCore is deployed with the lan-software Helm umbrella chart, every satellite's LANCORE_TOKEN and LANCORE_WEBHOOK_SECRET are provisioned automatically from a shared seed Secret the umbrella emits (<release>-integrations-seed). The umbrella chart:

  1. Auto-generates a per-slug token + webhook secrets (via Helm lookup, stable across upgrades), OR honours operator overrides in global.integrations.<slug>.{token,announcementWebhookSecret,rolesWebhookSecret}.
  2. Mounts the full seed Secret into LanCore so config/integrations.php can read each slug's <SLUG>_LANCORE_TOKEN env var via env().
  3. Mounts each satellite's slice of the same Secret — LanCore's <SLUG>_LANCORE_TOKEN becomes the satellite's LANCORE_TOKEN, and <SLUG>_ROLES_WEBHOOK_SECRET becomes its LANCORE_WEBHOOK_SECRET.
  4. Runs php artisan integrations:sync as a pre-install/pre-upgrade Helm hook Job against LanCore, which reconciles config/integrations.php into the database — creating or updating each IntegrationApp row, seeding the config-seeded token (SHA-256-hashed), and refreshing the subscribed Webhook rows.

Operator effect: helm install lan-software produces a working fleet with no admin-UI clickthrough, no kubectl exec, no per-satellite token paste. Hostnames derive from global.domain + global.satelliteHostStyle (flat / prefixed / custom) so the whole fleet is hostname-agile.

See:

Local development (Docker Compose / Sail)

For local dev without the Helm chart, set the env vars directly in the satellite's .env file. LanCore ships an integration:setup-dev <slug> Artisan command that mints a dev token and prints the .env snippet to copy. Alternatively, run php artisan integrations:sync against LanCore with LANCORE_INTEGRATIONS_RECONCILE_ON_BOOT=true to pick up config/integrations.php at LanCore boot.

Using the client from a satellite

See the package source under src/ + tests under tests/ for the full API surface.

All versions of lancore-client with dependencies

PHP Build Version
Package Version
Requires php Version ^8.3
illuminate/http Version ^13.0
illuminate/support Version ^13.0
illuminate/contracts Version ^13.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package lan-software/lancore-client contains the following files

Loading the files please wait ...