Deployment documentation

Install your exported Node.js website on cPanel

A step-by-step guide for SigmaCanvas standalone Node.js exports. Publish your website and its included admin dashboard using your hosting account’s Node.js application manager.

Node.js 24 recommendedPrecompiled Next.jsPrivate SQLite storageNo deployment build

One package. One application.

The Node.js ZIP includes the compiled website, public assets, server entry points and private project database. For kits that include commerce or blog features, the storefront and admin use the same data. This export runs independently of the main SigmaCanvas Express/MySQL backend.

Your public addresshttps://example.com
cPanel routes HTTPS traffic

Private Node.js application/home/USERNAME/my-node-site
Website + included admin + SQLite

Choose the Node.js exportUse the exported Node.js ZIP, not the static HTML ZIP. This guide applies to packages containing app.js, server.js, .next and .data. Check your package’s CPANEL-README.txt for release-specific instructions.

1. Check your hosting

Your plan offers Setup Node.js App (CloudLinux) or Application Manager (cPanel/Passenger).
Node.js 22.13.0 or later is available. Prefer Node.js 24 for this export; check package.json → engines.
Your account has persistent writable disk storage and sufficient space for the extracted ZIP, installed dependencies, uploads and backups.
You can install npm dependencies through the panel or its Terminal/SSH environment.
Your domain or subdomain points to this hosting account and has a valid SSL certificate.

Confirm support before uploadingA PHP-only or static-only plan cannot run this package. If the Node.js feature or required runtime is missing, ask your provider to enable it. The provider must support this compiled Next.js runtime under Passenger; availability of a Node.js menu alone does not guarantee compatibility.

Use the domain at its URL root, for example https://example.com/ or https://shop.example.com/. Avoid deploying under /shop unless your export explicitly supports that base path.

2. Upload and extract the package

Create a private application directory
In cPanel → File Manager, open your account’s home directory and create my-node-site outside public_html. Replace USERNAME in this guide with your cPanel account name.
Upload your exported Node.js ZIP
Upload the ZIP into /home/USERNAME/my-node-site and extract it. If extraction creates an extra enclosing folder, use that folder as the application root or move its contents one level up.

Show hidden files and check the structure

Enable Settings → Show Hidden Files (dotfiles) in File Manager. The startup file and package manifest must sit directly inside the selected application root.

/home/USERNAME/my-node-site/
├── app.js
├── server.js
├── package.json
├── package-lock.json
├── next.config.js
├── CPANEL-README.txt
├── .next/                 # compiled application
├── .data/                 # private persistent data
│   └── content.sqlite
└── public/                # public website assets

Keep the application root privateDo not expose this directory as a static document root. It contains the database and server files. Keep .next and .data intact; uploading only public will not install the application. Dependencies must be installed on the Linux host, rather than copied from Windows.

3. Register the Node.js application

Use the section matching the feature available in your hosting account. Labels vary by provider.

Option A — CloudLinux “Setup Node.js App”

Open cPanel → Software → Setup Node.js App → Create Application.
Enter the following settings, then create the application.

Application settings
Field	Value
Node.js version	24.x preferred; minimum 22.13.0
Application mode	Production
Application root	`my-node-site` (relative to your account home)
Application URL	Your chosen domain or subdomain, at `/`
Application startup file	`app.js`

If your panel creates a sample startup page, retain the exported app.js and server.js in the application root. Do not replace them with the panel’s example code.

Option B — cPanel “Application Manager”

Open cPanel → Software → Application Manager → Register Application.
Choose a descriptive application name, your deployment domain and base application URL /.
Set the application path to my-node-site, relative to your home directory, and select Production.
Register the application. Passenger uses app.js by default; this export already includes it.

Some cPanel installations do not offer a Node.js version selector. Ask your provider to confirm which Node.js executable Passenger uses and ensure it satisfies the package’s version requirement.

Set the production environment

Add these values in your application’s environment-variable settings, save, and restart after completing the next step. If your panel does not expose environment variables, ask the provider to configure them for this Passenger application.

NODE_ENV=production
SIGMACANVAS_PUBLIC_ORIGIN=https://example.com

Replace the example origin with the exact browser-facing HTTPS origin, including www or the subdomain if used. Do not append a path. This setting supports admin login origin checks and secure cookies behind the hosting proxy. Use one canonical domain for the website and login.

Use the hosting-assigned portThe exported server reads PORT. Keep the supplied startup files and let the hosting platform manage routing. Visitors use your HTTPS domain without a :3000 suffix.

4. Install dependencies and start

In CloudLinux, use the application’s Run NPM Install action. In cPanel Application Manager, use Enable Dependencies where available. Alternatively, open Terminal/SSH and first run the exact environment activation command shown by your panel.

# First activate the Node.js environment shown in your hosting panel.
# Replace USERNAME with your cPanel account name.
cd /home/USERNAME/my-node-site
node --version
npm --version
npm ci --omit=dev

Confirm that node --version meets the requirement before installing. If your release has no lock file, follow its README and use npm install --omit=dev.

The production build is already includedDo not run npm run build or upload a source checkout. Keep the supplied .next directory. Dependency installation still requires network access and disk space.

Use the panel’s Start or Restart action. For cPanel Passenger installations without a restart button, create or update tmp/restart.txt inside the application root:

cd /home/USERNAME/my-node-site
mkdir -p tmp
touch tmp/restart.txt

Open your domain to trigger a request. Passenger manages the application process; use the panel rather than starting a second copy through PM2 or a background terminal command.

5. Secure and verify your website

Open the public website
Visit https://example.com/. Check the home page, other pages, images and navigation on desktop and mobile.
Sign in to the included dashboard
For exports with the native dashboard, visit https://example.com/admin/login. Current starter exports use the account below; confirm it in your package README.
```
Email:    admin@sigmacanvas.local
Password: SigmaCanvas@123!
```
Immediately change the starter password in dashboard Settings. Source account passwords and login sessions are not exported. Restrict public access during initial setup if your provider supports it.
Configure integrations when included
Enter your own SMTP and payment settings through the supported dashboard controls. Integration secrets are excluded from exports. Test email delivery and payment configuration before accepting real orders.
Verify shared data and persistence
Edit a test product or blog entry, confirm the public page updates, restart the application and confirm the change remains. For commerce kits, check cart, stock, variants and a clearly identified test order. Review sample-data notices and use the dashboard’s sample-removal action if provided.

Content editing and visual editingThe included admin can manage the content supported by your kit. Visual design editing remains in SigmaCanvas. The hosted /studio and AI/project editing endpoints are disabled; export again after design changes.

6. Backups and future updates

Use one application instance. Only one instance should write to the exported SQLite database.
Keep storage persistent and writable. The runtime uses .data/content.sqlite. Preserve the entire .data directory and any uploaded media.
Back up while stopped. Stop the application using the panel, copy the complete .data directory and uploaded media to a private backup location, then start again. Include SQLite journal/WAL files if present; do not copy only the main database from a running app.
Preserve live data before updates. A fresh ZIP may contain its own seeded database. Do not extract it over your live .data. Test the update in a separate private location and follow any release migration instructions.
Keep a rollback copy. Save the previous application, matching database backup and host environment settings before changing versions. Confirm content, login, orders and integrations after the update.

Keep backups and archives outside publicly served directories. Use account-owned writable folders; avoid granting blanket 777 permissions.

Common installation issues

503 or “application could not be started”

Read the application/Passenger error log using your panel or provider. Check runtime version, application root, app.js and dependency installation. Log locations vary by host.

Missing module or SQLite runtime error

Check Node.js is at least 22.13 in both Terminal and Passenger. Install dependencies in the host’s selected Node environment and restart. Do not upload Windows node_modules.

Images or pages return 404

Confirm public and the complete hidden .next directory were extracted. Check the domain mapping and deploy at URL root /.

Login fails or cookies do not persist

Verify SSL and the exact SIGMACANVAS_PUBLIC_ORIGIN, including www if used. Save settings, restart, and clear cookies for the site before retrying.

Read-only database or missing changes

Confirm the app user can write to .data and its files, storage persists, and disk quota is available. Ensure you have only one application instance.

The panel shows its sample page

Check the selected app root, domain mapping and startup file. Restore the exported app.js if overwritten, restart, and confirm DNS points to this account.

Final launch checklist

HTTPS works and the domain maps to the correct application.
The starter password has been changed.
Public pages and included admin work on desktop and mobile.
Admin changes survive an application restart.
Included checkout/email integrations have been configured and tested.
A private backup and update procedure are ready.

Hosting documentation

Panel features depend on your provider. See cPanel Application Manager, cPanel Node.js installation, CloudLinux Manager and Passenger restart instructions.

WebStudio - How to intalll Exported Project on own server or hosting #