• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Headless Wordpress and React App on same server - how?

flo

New Pleskian
I am pretty new in website and server stuff and i have a question:

I have an react app and it should be the main and only website I want to reach under www.example.com, and I want to use Wordpress just headless but on the same server. Server is managed by Plesk.

As far as I understood, Wordpress has to be installed in my servers document root, e.g. /httpdocs/.

But when I want to reach my react app under www.example.com, I have to deploy the build folder content also into /httpdocs/, which interfers with wordpress. In this case if I go to www.example.com, I get the wordpress site.

When I have my react app in another folder, e.g. /github/build/, and set this folder my document root, the page is accessible under www.example.com, but wordpress is not reachable anymore (www.example.com/wp-login.php not found).

The only ugly way it seems for me it can work is if I deploy the build folder into the wordpress root directory, but then the react app is only acessible under www.example.com/build (only guessing).

Is there a way to make it work as wanted?
 
I set the thread to resolved because the solution is simply to install wordpress in a sub folder, e.g. example.com/wp.
 
Back
Top