πŸ› οΈInstallation & Setup

Welcome to the part where everything actually comes together. This is where you install the DevPayr SDK for your environment, set it up properly, and prepare your app to start validating licenses like a professional.

Whether you're building a backend service, a frontend app, a Python tool, or a PHP/Laravel system, DevPayr gives you the flexibility to integrate however you prefer.

Let’s get everything installed and ready to go. πŸš€

🟦 Node.js β€” Installation & Basic Setup

If you're using Node.js (Express, Next.js, NestJS, CLI tools, or anything JavaScript-powered), installing DevPayr is straightforward.

Install Using npm

npm install @xultech/devpayr

Install Using yarn

yarn add @xultech/devpayr

Setup (Basic Example)

import { DevPayr } from '@xultech/devpayr';

DevPayr.bootstrap({
  license: 'YOUR_LICENSE_KEY',
  action: 'boot',
  onReady: (res) => console.log('SDK ready:', res)
});

🐘 PHP β€” Installation & Basic Setup

You can use DevPayr inside Laravel, Symfony, or even pure PHP scripts.

Install via Composer

Setup (Basic Example)

😌 Note: The PHP SDK plays extremely well with Laravel’s service container… but it also works fine in a lonely index.php file in a random folder. No judgment.


🟨 Frontend (Browser) β€” Installation & Setup

You have two options depending on how your project is structured.

Option 1: Browser (CDN)

Perfect for static sites, templates, themes, WordPress-like environments, and simple HTML/JS setups.

Option 2: Install via npm (for Webpack, Vite, Next.js, etc.)

Setup (Flexible Example)

You can name your config object anything β€” DevPayr will detect it.

πŸ’‘ Tip: Unlike backend SDKs, the frontend SDK lets you disguise or restructure your licensing code however you want. Helpful when you don't want users to simply "delete that one script" to bypass licensing.

🐍 Python β€” Installation & Setup

Great for automation scripts, CLI tools, backend services, or anything Python-powered.

Option 2: Install from Source

Setup (Basic Example)

🐍 Note: Python developers always love editable installs (pip install -e .) β€” just don’t delete the folder afterward… unless you enjoy debugging existential errors.

Last updated