Installation

This guide explains how to install Paymery on both shared hosting and VPS environments. Please follow the steps carefully based on your hosting type.

Server Requirements

• PHP 8.x
• MySQL 5.7+ or MySQL 8.x
• Composer
• Apache or Nginx
• HTTPS recommended (required for Stripe checkout + webhooks)

Installation Steps

1. Upload all project files to your server
2. Create an empty MySQL database
3. Open your domain in the browser
4. Follow the installer flow:
   • Welcome
   • Requirements
   • Database
   • Migrate
   • Admin
   • Finish
5. After completion, the installer is automatically locked for security

Shared Hosting Installation (Important)

When installing Paymery on shared hosting, the document root usually points to public_html. Since Laravel applications must be served from the public directory, you need to create an .htaccess file inside public_html.

Create the file public_html/.htaccess with the following content:

<IfModule mod_rewrite.c>
RewriteEngine On

RewriteCond %{REQUEST_URI} !^/public/
RewriteRule ^(.*)$ public/$1 [L]
</IfModule>

This rule redirects all requests to the public directory, allowing the application to work correctly on shared hosting environments.

VPS Installation

If you are using a VPS (Nginx or Apache with custom virtual host configuration), you only need to point your server document root directly to the public directory. No additional .htaccess configuration is required.

Post-Installation Configuration (Recommended)

After installation and activation, it is recommended to review and adjust your environment configuration for better performance and stability.

Session Driver

By default, the application may use file-based sessions. For production usage, it is recommended to switch to a database or Redis session driver.

SESSION_DRIVER=database

Or, if Redis is available on your server:

SESSION_DRIVER=redis

Cache Configuration

You may also update the cache configuration in your .env file:

CACHE_DRIVER=database
CACHE_STORE=database

These values can be changed later depending on your hosting setup and performance needs.

Notes

• No database changes occur before database credentials are validated.
• Environment configuration is separated from migrations to prevent crashes.
• If you encounter server errors, please refer to the Troubleshooting section.