Website Deployment Should Not Begin with Server Commands

For many people, the difficult part of a first Linux website is not the application itself. It is the combination of server commands, runtime versions, directory permissions, and database settings.

NNS Linux Web Hosting brings these tasks into one clear control panel. Users do not need server access or system administration knowledge. Upload the application, select PHP, create a database, bind a domain, and bring the website online.

Where Should Website Files Be Uploaded?

Public website files are stored in the web directory. The homepage, images, scripts, and frontend files should be placed in this directory or one of its subdirectories.

A website may also contain these system directories:

• web: the public website directory.
• log: website runtime logs for troubleshooting.
• private: non-public data that should not be used as a web directory.
• ssl: certificate-related files managed by the platform.
• backup: backup-related files, depending on the enabled service.
• tmp: temporary files that should not hold permanent business data.
• cgi-bin: a runtime directory for compatible applications.

These directories are part of the hosting environment. Unless the purpose is clear, do not delete, rename, or move the directories themselves.

From Uploading an Application to Opening the Website

A Linux website is usually deployed in this order:

1. Open the site's web directory through the browser file manager or FTP.
2. Upload and extract the website application.
3. Confirm that the application entry file is in the actual public directory.
4. Select the PHP version required by the application.
5. Create a database and database user, then enter the connection details in the application configuration.
6. Bind the primary domain and wait for DNS to become active.

If the default page is still shown, the application files are usually not in the correct public directory, or the domain has not been pointed to the selected node.

How Should You Choose a PHP Version?

Different applications require different PHP versions. Older applications may require an earlier runtime, while newer applications may require a newer environment.

NNS Linux Web Hosting provides multiple PHP versions. Customers can switch versions from the control panel according to application requirements.

Available versions depend on the selected product and node. Do not switch a running production website to the newest version without checking compatibility first.

Databases Are Not Created Automatically

A database is not created automatically when a website is activated. If the application needs one, open database management, create a database and database user, and enter the following details in the application:

• Database host
• Database name
• Database username
• Database password

Database quotas are controlled by the selected product. Creation is rejected when the allowed quantity or storage quota has been reached.

Primary Domains, Subdomains, and Alias Domains

The primary domain is the main address of the website. Subdomains can separate a blog, administration area, or another entry point. Alias domains allow multiple domains to access the same website.

After binding a domain, the required DNS records must also be configured. If the domain does not point to the selected node, the website configuration exists but external access will not work.

Rewrite Rules and Redirects

Websites that use clean URLs, hide entry files, or require redirects can configure rewrite rules and redirects in the website settings.

Common uses include:

• Redirecting an old URL to a new URL.
• Redirecting HTTP traffic to HTTPS.
• Hiding the application entry file from URLs.
• Sending requests to the application router.

Rules differ between applications. Use the application's documented rules. An incorrect rewrite rule can prevent the homepage, administration area, or static files from loading.

Browser File Management and FTP

The browser file manager is suitable for quick uploads, small file changes, and directory checks. FTP is better for uploading an entire application, managing many files, and ongoing development.

Both tools operate within the same hosting service file scope and do not expose another customer's website directory. For large uploads, check the local network, file-size limits, and the available storage quota.

Usage and Runtime Status

The client area synchronizes disk, traffic, and database usage. Usage is collected from the hosting node and updated by the platform, so a short delay may occur after a large upload or database operation.

When usage approaches the product quota, remove unnecessary files, logs, and temporary data, or choose a product with more suitable resources.

What Websites Are Suitable?

• Personal websites, blogs, and portfolios
• Business and product websites
• PHP content systems and business applications
• Website development and compatibility testing
• Small projects that need databases and file management

Service Boundaries

Linux web hosting is designed for website applications. It is not a standalone server with root access.

Applications that require permanent system processes, Docker, custom system services, or continuous high resource usage should not be deployed on a standard hosting service.

Making Website Deployment Simple

The value of NNS Linux Web Hosting is not exposing every server parameter to the customer. It is organizing a complex runtime environment into a clear website deployment process.

Upload the application, choose PHP, create the database, bind the domain, and configure the rules. When more capability is needed, SSL automation, node migration, offsite recovery, and NNS AI Security Shield can be activated according to the product entitlement.