\n| Cloudflare Workers (alternative)<\/th>\n | No server to manage<\/td>\n | No (Wrangler on your computer)<\/td>\n | Your computer<\/td>\n | Cloudflare Workers<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n For production sites with scheduled publishing, a server where you control the process (Path 3, or a Cloud VPS) is the safer choice. Shared hosting is suitable for a test site or a small site that does not rely on scheduled posts.<\/p>\n <\/i> Step 0: Build the Project Locally<\/h2>\nBuild and test the site on your own computer first. EmDash’s Node.js guide starts with the scaffolder, and the same project works on every path below.<\/p>\n \n- Check Node.js:<\/strong> run
node --version<\/code>. It must report v22.16.0 or later.<\/li>\n- Create the project:<\/strong> run
npm create emdash@latest<\/code>. When asked where you will deploy, choose Node.js. Choose the Starter template, which the docs show with Posts and Pages.<\/li>\n- Run it locally:<\/strong> run
npm run dev<\/code>, then open http:\/\/localhost:4321\/_emdash\/admin\/<\/code> and complete the setup wizard.<\/li>\n- Generate the encryption key:<\/strong> run
npx emdash secrets generate<\/code> and save the output. It encrypts plugin secrets. Keep a separate backup of it, because the docs say you cannot recover stored plugin secrets without it.<\/li>\n- Set the site URL:<\/strong> set
EMDASH_SITE_URL<\/code> to your public address, for example https:\/\/example.com<\/code>. It must be set at build time, or images are served unoptimised.<\/li>\n<\/ul>\n\n <\/i> Do not upload your .env file:<\/h3>\nThe scaffolder writes the encryption key to a .env file. Keep .env out of uploads and out of version control. Set the same variables in your hosting panel or server environment instead.<\/p>\n<\/div>\n <\/i> Steps Every Path Shares<\/h2>\nThese requirements come from EmDash’s Node.js deployment guide. They apply to every path.<\/p>\n \n \nEmDash runtime requirements, and where each one is set<\/caption>\n\n\n| Requirement<\/th>\n | Setting<\/th>\n | Notes from the docs<\/th>\n<\/tr>\n<\/thead>\n | \n\n| Node.js 22.16 or later<\/th>\n | Node version in the host, or your server<\/td>\n | Required. Check the version before you start.<\/td>\n<\/tr>\n | \n| Build step<\/th>\n | npm run build, with EMDASH_SITE_URL set<\/td>\n | Produces dist\/server\/entry.mjs.<\/td>\n<\/tr>\n | \n| Start command<\/th>\n | node .\/dist\/server\/entry.mjs<\/td>\n | Standalone Node entry. It does not read a .env file, so set variables in the environment.<\/td>\n<\/tr>\n | \n| Encryption key<\/th>\n | EMDASH_ENCRYPTION_KEY<\/td>\n | Required for plugin secrets. Generate with npx emdash secrets generate.<\/td>\n<\/tr>\n | \n| Database<\/th>\n | DATABASE_PATH, for example \/home\/you\/emdash\/data\/emdash.db<\/td>\n | SQLite needs persistent disk and write access to the folder.<\/td>\n<\/tr>\n | \n| Uploads<\/th>\n | Local directory .\/data\/uploads, or S3\/R2 storage<\/td>\n | Back up the upload folder with the database.<\/td>\n<\/tr>\n | \n| Address and port<\/th>\n | HOST and PORT (default 4321)<\/td>\n | On a panel, the app manager may assign the port. Follow its instructions.<\/td>\n<\/tr>\n | \n| HTTPS<\/th>\n | Reverse proxy, panel SSL, or Cloudflare<\/td>\n | Set EMDASH_SITE_URL so absolute URLs are correct.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/i> Path 1: cPanel Server or Shared Hosting (Node.js App)<\/h2>\nUse this path on a cPanel account with a Setup Node.js App tool. The menu labels below follow common cPanel wording. Your screen may differ, so match the steps to the fields you see.<\/p>\n \n- <\/i> Create the app.<\/strong> In Setup Node.js App, choose Create Application. Set the Node.js version to 22.16 or later. Set the application root to a folder such as
emdash<\/code>. Set the application URL to your domain or subdomain.<\/li>\n- <\/i> Set the startup file.<\/strong> Set it to
dist\/server\/entry.mjs<\/code>, which EmDash’s docs start with node<\/code>. If the manager rejects an .mjs file, ask UnderHost support whether it can run an ES module, and test before going further.<\/li>\n- <\/i> Upload the project.<\/strong> Upload your project folder through File Manager as a zip, then extract it in the application root. Do not upload node_modules or .env. Upload dist\/ only if you build on your computer.<\/li>\n
- <\/i> Install and build.<\/strong> Use Run NPM Install in the app manager if it is offered, then run the build. If the app manager cannot run the build, build on your computer and upload dist\/ and the packages it needs (see the note below).<\/li>\n
- <\/i> Set environment variables.<\/strong> Add EMDASH_ENCRYPTION_KEY, EMDASH_SITE_URL and DATABASE_PATH in the app manager. Add HOST if the manager asks for it. Do not set PORT yourself unless the manager tells you to, because it assigns the port.<\/li>\n
- <\/i> Create the data folders.<\/strong> In File Manager, create the folder for the database and the uploads folder. Make sure the app can write to them.<\/li>\n
- <\/i> Start the app.<\/strong> Restart it from the app manager. Then open your domain and check the checks in the section below.<\/li>\n<\/ul>\n
Build notes for cPanel:<\/strong> A build on a shared server can hit memory or time limits. Building on your computer avoids that. The packages in node_modules must work on the server’s Linux system, so if a native package fails, use the install step on the server instead. We have not tested either build route on UnderHost, so check the results before you rely on them.<\/div>\n<\/i> Path 2: UnderHost Shared Hosting Without SSH<\/h2>\nThis is the same app-manager route as Path 1, with shared-plan limits. UnderHost shared plans include Node.js and crontab and do not include SSH, so you do everything in cPanel and File Manager.<\/p>\n \n- Build on your computer.<\/strong> Without SSH, the build is the step most likely to fail on shared hosting. Build with
npm run build<\/code> on your computer, then upload dist\/ and the runtime packages.<\/li>\n- Test the process.<\/strong> Check whether the app stays running between visits. EmDash’s docs say scheduled publishing pauses when no process runs, so test a scheduled post before you rely on it.<\/li>\n
- Keep the data small.<\/strong> Shared plans have disk and bandwidth limits, and the SQLite file and uploads grow with content. Check your plan’s disk limit before you upload media.<\/li>\n
- Back up through File Manager.<\/strong> Download the database file and the uploads folder regularly. Restores need the process stopped, as the docs say.<\/li>\n<\/ul>\n
\n <\/i> When to move:<\/h3>\nIf the app goes idle, your scheduled posts do not run, or the build fails, move the site to a Cloud VPS (Path 3). Shared hosting is a reasonable place to test EmDash. Production with scheduled posts needs a process that stays up.<\/p>\n<\/div>\n <\/i> Path 3: Linux Server Without a Panel<\/h2>\nUse this path on a VPS or dedicated server with root or sudo access and no control panel, such as a fresh Ubuntu, Debian, AlmaLinux or Rocky Linux server. The commands below come from the EmDash Node.js guide. The process-manager step is general Linux practice, not part of EmDash’s docs.<\/p>\n \n- Install Node.js 22.16 or later.<\/strong> Use your distribution’s packages or a Node.js version manager. Confirm with
node --version<\/code>.<\/li>\n- Copy the project to the server.<\/strong> Use git, scp or sftp. Work in a directory your app user owns, for example
\/var\/www\/emdash<\/code>.<\/li>\n- Install and build.<\/strong> Run
npm ci<\/code> and then npm run build<\/code>, with EMDASH_SITE_URL<\/code> set in the environment first.<\/li>\n- Set the environment.<\/strong> Put EMDASH_ENCRYPTION_KEY, EMDASH_SITE_URL, DATABASE_PATH, HOST and PORT in the service environment. The standalone Node entry does not read a .env file.<\/li>\n
- Start the server.<\/strong> Run
node .\/dist\/server\/entry.mjs<\/code> to test it. Then keep it running with a service manager.<\/li>\n- Put a proxy in front.<\/strong> Use Nginx, Caddy or your panel’s proxy to serve HTTPS on your domain and forward to the EmDash port. Set EMDASH_SITE_URL to the public HTTPS address.<\/li>\n<\/ul>\n
<\/i> Keeping the Process Running<\/h2>\nEmDash’s docs say scheduled tasks run inside the Node process, so the process must stay up. On a server with systemd, a service file keeps it running and restarts it after a crash or reboot. The example below is general systemd practice and has not been tested with EmDash. Replace the paths and user with yours, and test it on a staging server first.<\/p>\n [Unit]\r\nDescription=EmDash CMS\r\nAfter=network.target\r\n\r\n[Service]\r\nUser=emdash\r\nWorkingDirectory=\/var\/www\/emdash\r\nEnvironmentFile=\/etc\/emdash\/emdash.env\r\nExecStart=\/usr\/bin\/node .\/dist\/server\/entry.mjs\r\nRestart=always\r\n\r\n[Install]\r\nWantedBy=multi-user.target<\/code><\/pre>\nDocker is also documented by EmDash. The docs include a Dockerfile that builds on node:22-alpine and a Compose file with a named volume for \/app\/data. Use it on a server where Docker is already set up.<\/p>\n <\/i> Checks Before You Send Traffic<\/h2>\nThese checks come from EmDash’s docs, which say to keep a new instance out of traffic until every applicable check passes. The migration check needs a terminal, so run it on your computer or a server with SSH. On shared hosting without SSH, the first request applies migrations automatically, and the admin test shows whether it worked.<\/p>\n \n- <\/i> Request \/health<\/strong> and one public page. Both must return a successful response. Create the health route before the build, at
src\/pages\/health.ts<\/code>, returning OK with status 200.<\/li>\n- <\/i> Run the migration check<\/strong> from the built project with
npx emdash migrate --check<\/code>, if you have a terminal. It must report no pending or unknown migrations.<\/li>\n- <\/i> Sign in to \/_emdash\/admin\/<\/strong>, create a disposable draft, publish it and confirm the public page changes.<\/li>\n
- <\/i> Upload a test media file<\/strong>, open its URL, then delete it.<\/li>\n
- <\/i> Test a scheduled post<\/strong> if you rely on scheduled publishing, and confirm it goes live.<\/li>\n
- <\/i> Check sandboxed plugins,<\/strong> if you use them. Invoke one plugin route and confirm the log has no sandbox or startup error.<\/li>\n<\/ul>\n
The health route only proves that the Node process can serve pages. It does not prove that the database, storage or plugin sandbox is healthy, so run the other checks as well.<\/p>\n <\/i> Backups<\/h2>\nEmDash’s docs say to back up both the SQLite file and the upload directory, and to stop the process before replacing either during recovery. Keep a copy of EMDASH_ENCRYPTION_KEY separately, because the docs say that restoring a database without the key leaves plugin secrets unreadable.<\/p>\n \n- Shared hosting and panels:<\/strong> download the database file and uploads folder from File Manager on a schedule.<\/li>\n
- Servers:<\/strong> copy the database and uploads with your normal backup tools, and keep at least one copy off the server.<\/li>\n
- Restore:<\/strong> stop the process, replace the files, then start it again and run the checks.<\/li>\n<\/ul>\n
<\/i> Updating EmDash<\/h2>\nEmDash’s update guide says to update the emdash and @emdash-cms\/cloudflare packages in one step, because they share a version and the Cloudflare package depends on the exact matching version. Plugin packages have their own versions and declare the minimum EmDash version they need. Back up before any update.<\/p>\n \n- Read the release notes.<\/strong> A major release can require changes to your project.<\/li>\n
- Update, build and restart.<\/strong> Update the package, run the build again with EMDASH_SITE_URL set, then restart the app.<\/li>\n
- Check the site.<\/strong> Run the checks above again before you send traffic.<\/li>\n
- Template files do not update automatically.<\/strong> Compare your layouts and configuration with the current template yourself.<\/li>\n<\/ul>\n
<\/i> Errors and Fixes<\/h2>\nThe table lists errors that EmDash’s docs describe. We have not found documented fixes for cPanel-specific errors, so those are marked as not documented.<\/p>\n \n \nErrors and fixes<\/caption>\n\n\n| Symptom<\/th>\n | Where<\/th>\n | Fix from the docs<\/th>\n<\/tr>\n<\/thead>\n | \n\n| ExperimentalWarning: SQLite<\/th>\n | Node 22<\/td>\n | Expected. It does not stop the database from opening.<\/td>\n<\/tr>\n | \n| Plugin secrets cannot be saved or read<\/th>\n | Any Node install<\/td>\n | Check EMDASH_ENCRYPTION_KEY is set and valid. Generate one with npx emdash secrets generate.<\/td>\n<\/tr>\n | \n| Images are not optimised<\/th>\n | Build<\/td>\n | Set EMDASH_SITE_URL before npm run build.<\/td>\n<\/tr>\n | \n| Scheduled posts do not publish<\/th>\n | Any Node install<\/td>\n | Keep at least one Node process running. The scheduler pauses when no process runs.<\/td>\n<\/tr>\n | \n| D1 or R2 binding not found<\/th>\n | Cloudflare<\/td>\n | Check the binding names in wrangler.jsonc match the EmDash configuration (DB and MEDIA in the template).<\/td>\n<\/tr>\n | \n| Migration or schema errors<\/th>\n | Cloudflare<\/td>\n | Run wrangler tail and reproduce the error to capture the logs.<\/td>\n<\/tr>\n | \n| App does not start on cPanel<\/th>\n | cPanel app manager<\/td>\n | Not documented by EmDash. Check the startup file path, Node version and the app log in the app manager. Ask UnderHost support if the log is unclear.<\/td>\n<\/tr>\n | \n| Build fails on shared hosting<\/th>\n | cPanel shared<\/td>\n | Not documented by EmDash. Build on your computer, then upload dist\/.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/i> Alternative: Cloudflare Workers<\/h2>\nIf you do not want to run a server, EmDash documents a Cloudflare route with Workers, D1 for the database and R2 for media. You log in with Wrangler on your computer, build, and deploy. The site then runs on Cloudflare, not on your hosting account.<\/p>\n \n- Run
pnpm wrangler login<\/code>, then pnpm build<\/code>, then pnpm wrangler deploy<\/code>. The first deploy creates the D1 database and R2 bucket.<\/li>\n- The template includes a Cron Trigger for scheduled publishing and maintenance.<\/li>\n
- Point your domain to the Worker in Cloudflare, and set SSL in your Cloudflare zone.<\/li>\n<\/ul>\n
Use the Cloudflare route when you want no server to manage. Keep your hosting account for other sites, and remember that the EmDash site and its data then live on Cloudflare.<\/p>\n \n <\/span>
\n ![\"\"](\"https:\/\/cdn.underhost.com\/android-chrome-192x192.webp\")
\n <\/span>\n<\/div>\n\n Need a Server That Keeps EmDash Running?<\/h2>\nA Cloud VPS gives you Node.js 22.16 or later, a process that stays up, and root access for backups and updates. Start with a test site, then move production when the checks pass.<\/p>\n View Cloud VPS Plans<\/a>Compare Shared Hosting<\/a>Ask @CustomerPanel<\/a>\n<\/div>\n\n Frequently Asked Questions<\/h2>\n\n Can I install EmDash on cPanel?<\/h3>\nYes, if the cPanel account has Node.js 22.16 or later and a Setup Node.js App tool. Use the cPanel path in this guide. Confirm the Node.js version first, because EmDash will not run on an older version.<\/p>\n<\/p><\/div>\n \n Do I need SSH to install EmDash?<\/h3>\nNo, not for the cPanel path. The app manager runs the server, and environment variables are set in cPanel. You do need a way to run the build: either the app manager’s install step, or building on your own computer and uploading the output. SSH makes the build and the checks easier on a server without a panel.<\/p>\n<\/p><\/div>\n \n Can I install EmDash on UnderHost shared hosting?<\/h3>\nYes, using the cPanel Node.js app path, on a plan with Node.js 22.16+. Shared hosting has memory and process limits, and a process that goes idle can pause scheduled publishing. Use a Cloud VPS for a production site with scheduled posts.<\/p>\n<\/p><\/div>\n \n What Node.js version does EmDash need?<\/h3>\nNode.js 22.16.0 or later, as stated in the EmDash deployment docs and the package engines field. Node 22 prints an ExperimentalWarning about SQLite. The docs say the warning does not stop the database from opening.<\/p>\n<\/p><\/div>\n \n How do I create the admin account?<\/h3>\nOpen \/_emdash\/admin\/ on your site. A new site redirects to the setup wizard. Enter a site title and your email, then register a passkey in the browser. The setup wizard runs once.<\/p>\n<\/p><\/div>\n \n Where is my content stored?<\/h3>\nOn a Node.js install with SQLite, content is in the database file set by DATABASE_PATH or the config, and uploads are in the upload directory. Back up both, and stop the process before restoring either.<\/p>\n<\/p><\/div>\n \n What if scheduled posts do not publish?<\/h3>\nEmDash’s docs say the scheduler runs only while a Node.js process is running, and pauses when every process stops or sleeps. Keep at least one process running in production. On shared hosting, test a scheduled post to see whether the app stays up.<\/p>\n<\/p><\/div>\n \n Can I install EmDash on Cloudflare instead?<\/h3>\nYes. Cloudflare Workers with D1 and R2 is a documented route that needs no server shell, because you deploy with Wrangler from your own computer. The site then runs on Cloudflare, not on your cPanel account.<\/p>\n<\/p><\/div>\n<\/div>\n
\n
|
| |