How to deploy an application with API, Frontend, and Admin

[comcduarte]

This is going to be my first production application using dotkernel, as I've used Laminas MVC in the past. I'm looking to deploy an app that utilizes the front-end for public access, Admin for power user administration, and API to allow for all endpoints to use a single set of methods.

I've successfully deploy API already. I have a couple of questions which all involve: can I do it, how do I do it, and should I do it?

1. After deploying API, how can I add front-end to the same application without deploying a completely separate site?
2. Same question goes for Admin. This is a fairly small application so there's no need to distribute functions across multiple sites and servers; it will use very few resources.

I like to find and follow best practices rather than figuring out a way to make it work myself; easier to maintain that way, and I'm hoping this sheds some light on the framework so others can benefit from it.

[arhimede]

1. For the moment, in Headless Platform are included only API and Admin, not a frontend.
   The main reason for that is , like the name Headless say, there is no frontend. This one is up to the user how to build it and using which tech stack.

2. Dotkernel Frontend is not yet part of the headless platform

3. If all you want is a simple website, then use Dotkernel Light, which is a minimal application built on top of Mezzio microframework, with very few extra libraries.

4. How to use API together with Admin ( best practice)

   • install API
   • move the folder /src/Core into its own repository, as submodule
   • install Admin
   • delete the folder /src/Core from Admin codebase
   • use in Admin the previously created submodule
   • use a common database
     The key point is that in Core there are all Entities , which will be common for API and Admin