Download the PHP package rumenx/php-chatbot without Composer

php-chatbot

php-chatbot is a modern, framework-agnostic PHP package for integrating an AI-powered chat popup into any web application. It features out-of-the-box support for Laravel and Symfony, a flexible model abstraction for using OpenAI, Anthropic, xAI, Google Gemini, Meta, and more, and is designed for easy customization and extension. Build your own UI or use the provided minimal frontend as a starting point. High test coverage, static analysis, and coding standards are included.

Features

• Plug-and-play chat popup UI (minimal frontend dependencies)
• Laravel & Symfony support via adapters/service providers
• AI model abstraction via contracts (swap models easily)
• Customizable prompts, tone, language, and scope
• Emoji and multi-script support (Cyrillic, Greek, Armenian, Asian, etc.)
• Security safeguards against abuse
• High test coverage (Pest)
• Static analysis (phpstan) & coding standards (phpcs, Symfony style)

Supported AI Providers & Models

• OpenAI: gpt-4.1, gpt-4o, gpt-4o-mini, gpt-3.5-turbo, etc.
• Anthropic: Claude 3 Sonnet, 3.7, 4, etc.
• xAI: Grok-1, Grok-1.5, etc.
• Google: Gemini 1.5 Pro, Gemini 1.5 Flash, etc.
• Meta: Llama 3 (8B, 70B), etc.
• Free model (no API key required)

Installation

Laravel

• Package auto-discovers the service provider.
• Publish config: php artisan vendor:publish --provider="Rumenx\\PhpChatbot\\Adapters\\Laravel\\PhpChatbotServiceProvider"

Symfony

• Register the bundle in your bundles.php.
• Publish config: php bin/console chatbot:publish-config

Usage

1. Add the chat popup to your layout (see /resources/views for examples).
2. Configure your preferred AI model and prompts in the config file (src/Config/phpchatbot.php).
3. Optionally, customize the frontend (CSS/JS) in /resources.

API Keys & Credentials

Never hardcode API keys or secrets in your codebase.

• Use environment variables (e.g. .env file) or your infrastructure's secret management.
• The config file will check for environment variables (e.g. OPENAI_API_KEY, ANTHROPIC_API_KEY, etc.) first.
• See .env.example for reference.

Quick Start

Example .env

API Endpoint Contract

• Endpoint: /php-chatbot/message

• Request:

• Response:

Symfony Backend Example

Testing

Running Tests with Coverage

Static Analysis

Coding Standards

Security

• Input validation and abuse prevention built-in.
• Rate limiting and content filtering available via config.

Rate Limiting & Abuse Prevention

You can implement rate limiting and abuse prevention in your backend. For Laravel, use built-in middleware:

For plain PHP, you can use a simple session or IP-based limiter, or integrate a package like malkusch/lock or Redis.

JavaScript Framework Components

You can use the provided chat popup as a plain HTML/JS snippet, or integrate a modern component for Vue, React, or Angular:

• Vue: resources/js/components/PhpChatbotVue.vue
• React: resources/js/components/PhpChatbotReact.jsx
• Angular: resources/js/components/PhpChatbotAngular.html (with TypeScript logic)

JS Component Usage

1. Copy the component into your app's source tree.
2. Import and register it in your app (see your framework's docs).
3. Customize the backend endpoint (/php-chatbot/message) as needed.
4. Build your assets (e.g. with Vite, Webpack, or your framework's CLI).

Example (Vue)

Example (React)

Example (Angular)

• Copy the HTML, TypeScript, and CSS into your Angular component files.
• Register and use <php-chatbot-angular></php-chatbot-angular> in your template.

JS Component Customization

• You can style or extend the components as needed.
• You may add your own framework component in a similar way.
• The backend endpoint is framework-agnostic; you can point it to any PHP route/controller.

TypeScript Example (React)

A modern TypeScript React chatbot component is provided as an example in resources/js/components/PhpChatbotTs.tsx.

How to use:

1. Copy PhpChatbotTs.tsx into your React app's components folder.

2. Import and use it in your app:

3. Make sure your backend endpoint /php-chatbot/message is set up as described above.
4. Style as needed (the component uses inline styles for demo purposes, but you can use your own CSS/SCSS).

This component is a minimal, framework-agnostic starting point. You are encouraged to extend or restyle it to fit your app.

Backend Integration Example

To handle chat requests, add a route/controller in your backend (Laravel, Symfony, or plain PHP) that receives POST requests at /php-chatbot/message and returns a JSON response. Example for Laravel:

For plain PHP, use:

Frontend Styles (SCSS)

The chat popup styles are written in modern SCSS for maintainability. You can find the source in resources/css/chatbot.scss.

To compile SCSS to CSS:

1. Install Sass (if you haven't already):

2. Add this script to your package.json:

3. Compile SCSS:

Or use the Sass CLI directly:

To watch for changes automatically:

Only commit the compiled chatbot.css for production/deployment. For more options, see Sass documentation.

Customizing Frontend Styles & Views (Best Practice)

The provided CSS/SCSS and view files (resources/css/, resources/views/) are optional and basic. They are meant as a starting point for your own implementation. You are encouraged to build your own UI and styles on top of or instead of these defaults.

Do not edit files directly in the vendor/ folder or inside the package source.

How to Safely Override Views and Styles

• Copy the provided view files (e.g. resources/views/popup.blade.php or popup.php) into your own application's views directory. Update your app to use your custom view.
• Copy and modify the SCSS/CSS (resources/css/chatbot.scss or chatbot.css) into your own asset pipeline. Import, extend, or replace as needed.

• For Laravel/Symfony:

  • Publish the package views/config (see the Installation section above) and edit the published files in your app, not in vendor/.

  • Example (Laravel):

  • Example (Symfony):
• For plain PHP: Copy the view and style files to your public or template directory and reference them in your HTML.

Important: If you edit files directly in vendor/rumenx/php-chatbot/, your changes will be lost on the next composer update. Always override or extend in your own app.

Principle

• Treat the package's frontend as a reference implementation.
• Override or extend in your own codebase for all customizations.
• Never edit vendor files directly.

Best Practices

• Never edit files in vendor/
• Always copy views/styles to your own app before customizing
• Use environment variables for secrets
• Use the provided JS/TS components as a starting point, not as production code
• Keep your customizations outside the package directory for upgrade safety

What's Included

Questions & Support

For questions, issues, or feature requests, please use the GitHub Issues page.

Contributing

See CONTRIBUTING.md.

License

MIT. See LICENSE.md.