Getting started with Cakestack
Cakestack is a full-stack framework that pairs CakePHP on the backend with React on the frontend. It gives you a pre-configured setup so you are not stitching together two separate projects manually. The typical workflow is running the installer, creating a project, and then having both the API layer and the frontend app scaffolded and ready to go. If you want the download, you can find it on GitHub. The repository is public and the installation docs cover the basics. Clone it or use their installer command depending on what you are working with.
My experience actually using Cakestack in production
I ran into a specific issue when I was trying to run both the CakePHP backend and the React frontend in development mode at the same time. By default, the dev servers conflict over port 8080. The React dev server takes it, and the CakePHP built-in server chokes because it cannot bind. I fixed this by changing the React proxy config to point at a different backend port, and updating the CakePHP server to listen on 8765 instead. It took maybe twenty minutes to sort out once I realized what was happening. The framework separates concerns the way you would expect. Your API lives under the CakePHP side, typically in the src/Api directory or wherever the documentation says it should go. The React frontend sits on the other side, consuming that API. Build steps are usually handled by npm scripts or a mix of Composer and yarn/npm commands. There is no magic here. You run your build, your API starts, your frontend starts, and they talk to each other over HTTP. One thing beginners get wrong is assuming the full-stack part means you do not need to understand either framework individually. That is not true. You still need to know CakePHP routing, ORM, and authentication basics. And you still need to know React state management and component structure. Cakestack just removes the overhead of setting up the connection between them.
Practical walkthrough
Create a new project by running the installer. It will ask for a project name, database credentials if you are using one, and a few other defaults. After that, you will have a directory structure that looks something like this: a backend folder for CakePHP and a frontend folder for React. Start the backend with the usual CakePHP commands, start the frontend with the frontend dev server. If your frontend is making requests to localhost, configure the proxy so it hits the backend server on the correct port. When you are ready to deploy, you build the React app for production and serve it alongside the CakePHP application. Some people set up a reverse proxy with Nginx or Apache. Others just let the frameworks run independently. Both work, but the reverse proxy approach is cleaner for handling SSL and static assets.
Where Cakestack falls apart
I will be straightforward about the limitations. The framework is not suitable if you need a single integrated deployment model where the frontend and backend compile into one artifact. It also does not handle complex multi-tenant setups out of the box. If your application requires real-time communication through WebSockets, you are going to need additional tooling or a completely separate service. The React side is fairly vanilla, which is fine for simple apps but becomes limiting if you are building something with heavy state management requirements. You are better off reaching for something like Next.js or Remix in those cases. Another issue is that updates can be painful. When CakePHP releases a major version, you may need to manually adjust configuration files and migration scripts. The React dependencies also follow their own release cadence, and occasionally you will find yourself chasing broken builds because a package version conflict slipped through. If you are looking for a modern full-stack framework that handles routing, data fetching, and deployment in one package, Cakestack is not it. It is better described as a starter kit. For small teams building straightforward CRUD applications with a React frontend and a CakePHP API, it saves time. For anything more complex, you will spend more time working around its boundaries than you would have building from scratch.
