Skip to main content

Quick start

This guide will walk you through creating your first website with Webinoly, from installation to a working site.

Before you begin

Ensure you have:
  1. A fresh Ubuntu 24.04 or 22.04 server
  2. Root or sudo access
  3. At least 512MB RAM
  4. A domain name pointed to your server (optional but recommended)

Step 1: Install Webinoly

Install the complete LEMP stack:
wget -qO weby qrok.es/wy && sudo bash weby
This command:
  • Downloads the Webinoly installer
  • Installs NGINX, PHP 8.4, and MariaDB 11.8
  • Configures optimized settings
  • Takes 5-15 minutes to complete
The installation script will show progress messages. Wait for the “Webinoly installed successfully” message.

Step 2: Create your first site

Once installation is complete, you can create sites immediately.

Create a WordPress site

The fastest way to get started:
sudo site example.com -wp
This single command:
  • Creates the site structure
  • Installs NGINX configuration
  • Downloads WordPress
  • Creates a database and user
  • Sets up FastCGI cache
1

Create the site

Run the site creation command:
sudo site example.com -wp
Replace example.com with your actual domain name.
2

Note the credentials

Webinoly will display the database credentials:
Database: example_com
Username: example_com_user
Password: [random_password]
Save these credentials - you’ll need them for WordPress setup.
3

Complete WordPress installation

Visit your domain in a browser:
http://example.com
Complete the WordPress installation wizard using the database credentials from step 2.
4

Add SSL certificate

Once WordPress is installed, add a free SSL certificate:
sudo site example.com -ssl=on
Webinoly will automatically obtain a Let’s Encrypt certificate and configure HTTPS.
The first SSL certificate request may take a minute or two while Let’s Encrypt verifies domain ownership.

Create a PHP site

For a custom PHP application:
sudo site myapp.com -php
This creates:
  • Site directory: /var/www/myapp.com/htdocs/
  • PHP 8.4 support
  • Basic NGINX configuration
Upload your PHP files to /var/www/myapp.com/htdocs/.

Create an HTML site

For static HTML sites:
sudo site static.com -html
Upload your HTML files to /var/www/static.com/htdocs/.

Step 3: Manage your site

Webinoly provides powerful commands for site management.

View site information

sudo site example.com -info
Displays:
  • Site type (WordPress, PHP, HTML)
  • SSL status
  • Cache status
  • PHP version
  • Database details

Enable caching

For WordPress sites, enable FastCGI cache:
sudo site example.com -cache=on
FastCGI cache can dramatically improve site performance by serving cached pages from NGINX.

Clear cache

When you update your site:
sudo webinoly -clear-cache -domain=example.com

Common tasks

You can host multiple sites on one server:
sudo site site1.com -wp
sudo site site2.com -php
sudo site site3.com -html
Each site is completely isolated with its own directory and configuration.
Protect your site with username/password:
sudo httpauth example.com -add
You’ll be prompted to create a username and password.
Retrieve database credentials:
sudo webinoly -dbpass
Shows all database passwords including the root password.
Remove a site completely:
sudo site example.com -delete
Add -force-delete to skip confirmation prompts.

Working with databases

Webinoly automatically creates databases for WordPress sites. For other sites:

Create a database

WordPress sites get databases automatically, but you can create additional ones:
# Database is created with: sudo site example.com -wp
# Manual database creation via MySQL:
sudo mysql -u root

View database credentials

sudo webinoly -dbpass
Output shows:
Root password: [password]
Admin password: [password]
Keep database credentials secure. The root password provides full database access.

SSL certificates

Webinoly uses Let’s Encrypt for free SSL certificates.

Add SSL to a site

sudo site example.com -ssl=on

Wildcard certificates

For *.example.com:
sudo site example.com -ssl=on -wildcard
Wildcard certificates require DNS validation. You’ll need to add a TXT record to your domain’s DNS.

Force HTTPS redirect

sudo site example.com -force-redirect=www
# or
sudo site example.com -force-redirect=root
Options:

Server management

Check server status

sudo webinoly -info
Shows:
  • Webinoly version
  • NGINX version
  • PHP version
  • Database engine and version
  • Memory usage
  • Disk usage

Update Webinoly

sudo webinoly -update
Keeps your server up to date with the latest features and security patches.

Verify installation

sudo webinoly -verify
Checks for configuration issues and provides recommendations.

File locations

Knowing where files are stored helps with troubleshooting:
LocationPurpose
/var/www/[domain]/htdocs/Website files
/var/www/[domain]/logs/Access and error logs
/etc/nginx/sites-available/[domain]NGINX configuration
/opt/webinoly/webinoly.confWebinoly configuration
/etc/nginx/nginx.confMain NGINX config

Logs and debugging

View site logs

Access logs:
sudo tail -f /var/www/example.com/logs/access.log
Error logs:
sudo tail -f /var/www/example.com/logs/error.log

NGINX error log

sudo tail -f /var/log/nginx/error.log

PHP error log

sudo tail -f /var/log/php/[version]/fpm.log

Backup and restore

Webinoly includes comprehensive backup tools.

Backup a site

sudo webinoly -backup -domain=example.com
Creates a backup in /var/webinoly/backups/.

Restore a site

sudo webinoly -backup -restore -domain=example.com
Backups include website files, database, and NGINX configuration.

Advanced: Reverse proxy

Webinoly can proxy requests to applications like Node.js or Python apps.
sudo site api.example.com -proxy=http://localhost:3000
This creates a reverse proxy that forwards requests to your application running on port 3000.

Next steps

Now that you have a working site, explore more features:

Full documentation

Comprehensive command reference

WordPress multisite

Set up WordPress networks

Performance tuning

Optimize for maximum speed

Security hardening

Advanced security configurations

Getting help

If you encounter issues:
  1. Run sudo webinoly -verify to check for problems
  2. Check the documentation
  3. Visit the community forums
  4. Review server logs for error messages
Most common issues can be resolved by verifying firewall settings and DNS configuration.

Build docs developers (and LLMs) love