FAQ
Installation & getting started
Do I need Docker?
Not by default. reactpress init uses embedded SQLite; the desktop client also needs no Docker.
Docker or a standalone database is only required when you configure embedded-docker or external MySQL in .reactpress/config.json.
What is the difference between init and dev?
In 4.0 global CLI, init already starts services — no separate dev. dev is removed from the global CLI; Monorepo contributors use pnpm dev.
Is Admin on 3000 or 3001/admin?
reactpress init default: http://localhost:3001/admin/ (Admin mounted on the same port as the visitor theme).
Monorepo local development may use a separate Admin Vite dev server at http://localhost:3000.
What is the default account?
First bootstrap: admin / admin. Change password immediately after login; in production update via .env or Admin.
Features & choosing ReactPress
Can I use my own frontend?
Yes. ReactPress provides Headless REST + API Key. Fork reactpress-theme-starter or integrate /api/article and other endpoints. See Headless API guide.
How is it different from WordPress?
Similar: Admin-driven content workflow, theme and plugin extensions.
Different: Default Next.js themes are faster, Headless path is clearer, no PHP theme baggage; plus Electron desktop for offline writing.
How does it compare to Strapi / Payload and other Headless CMS?
They primarily deliver a backend API; ReactPress delivers a full publishing platform (Admin + API + theme catalog + plugins + desktop) with one CLI, reducing assembly cost.
What kinds of sites is it good for?
Personal blogs, team knowledge bases, developer doc sites, marketing sites with Headless custom frontends, workflows needing offline writing, and more. See use cases in Introduction.
Can I migrate from WordPress?
Content can be exported and re-imported via scripts or integrated through the Headless REST API. PHP themes are not portable — rebuild the visitor frontend in Next.js or use reactpress-theme-starter. See Headless API guide and ReactPress vs WordPress.
Is ReactPress free?
Yes. ReactPress is open source under the MIT license. Install globally: npm i -g @fecommunity/reactpress@beta.
Versions & upgrades
Is 4.0 production-ready?
4.0 is in active beta. Before upgrading production, read 3.x → 4.0 migration and validate on staging. Core paths init / doctor are stable.
How do I upgrade from 3.x to 4.0?
See migration guide. 4.0 has no forced breaking changes; plugins and desktop are additive.
Can I still use @fecommunity/reactpress-server?
Deprecated. New projects should use @fecommunity/reactpress CLI bundled API or Monorepo source deployment.
Deployment & configuration
How do I fill in production .env?
Set CLIENT_SITE_URL to the public visitor domain and SERVER_SITE_URL to the public API domain (include protocol, no trailing slash). Database credentials similar to local or use managed MySQL. See Configuration.
Database won't connect — what do I do?
- Run
reactpress doctor - Check
.envmatchesconfig.json - For Docker MySQL:
pnpm docker:dev:status - See Troubleshooting
Port already in use?
reactpress doctor lists blocking processes. Change server.port / client.port in config.json then config --apply (Monorepo), or stop the conflicting process.
Themes & plugins
Visitor site blank / 404?
Usually install and enable a theme in Admin Appearance → Themes. API may be fine but :3001 has no theme process without an active theme.
Plugin changes not taking effect?
Monorepo dev requires pnpm run build:plugins then API restart. Confirm plugin is enabled in Admin and Hook names match plugin.json.
Getting help
reactpress doctorandreactpress logs- GitHub Issues
- GitHub Discussions
Before asking, read How To Ask Questions The Smart Way and include Node version, OS, doctor output, and relevant logs.