Serve index.php from public folder

[donnikitos]

@donnikitos Hi, is there a way to change the project's root without altering the URLs of the assets? In my case, the entry file index.php is in the public folder, and the site is served from there, so in production, the asset URLs should be relative to this folder. That is, not /public/assets/style.css but /assets/style.css. I've tried everything for hours without success... I've already seen the starter repository, but it forces me to place index.php in the project root. My site is served from the public folder (and I want to keep the project's internal files out of it)...

An option would be to have the index.php in the root folder in development mode, and build it to dist/public/index.php folder, Keeping URLs relative to public...

Thanks.

Originally posted by @jonacio in #10

[donnikitos]

What is your project structure?

Maybe your could specify your config like:

usePHP({
	entry: ['public/index.php'],
});

Keep in mind you would
a) need to access your project during development with the path /public or
b) rewrite the URLs with the rewriteUrl?: (requestUrl: URL) => URL | undefined; option

[jonacio]

Im evaluating different structures, looking for the most appropriate one from my point of view, but what I definitely find essential is to isolate the internal files.

During development, the location of the files is not critical, but in production, a structure that seems appropriate to me is something like this:

site/  -->  *Project Root (DEV)*
├── dist/
│    ├── app/
│    │   └── <PHP Files>
│    ├── public/  -->  *Server Root (PROD)*
│    │   ├── assets/
│    │   │   ├── js/
│    │   │   ├── css/
│    │   │   └── img/
│    │   └── index.php
│    └── vendor/
└── vite.config.ts

In Dev mode I've gotten it to work quite well. I've set the entry to public/index.php and configured the rewriteUrl. The problem arises when compiling: the files in the public folder (including index.php) are moved to ./dist instead of ./dist/public, and the assets are also moved to ./dist If I force it to move them to ./dist/public (by modifying the rollupOptions config), the relative URL of the resources in the HTML is set to, for example, /public/asset.css instead of /asset.css (the root for prod server is ./public).

Clearly, the problem comes from Vite being designed to host all files in the root of the project. I've been investigating, and Laravel has a plugin for Vite that uses a very similar structure to the one I'm suggesting, and it works very well.

Sorry if it's not very clear, I'm already a little dizzy.

[lukasavic23]

I am having similar issue. I aim to have multiple "projects" inside of src/projects folder, where I would be able to create dev server and build those projects with a flag --project=PROJECT_NAME. Each project needs to have index.php instead of index.html as main entry point.

Before I did this (separated everything into projects), I had one project inside of the root directory with index.php as main index file, and everything was working fine with basic Vite and vite-plugin-php configs.

Right now, every index.php is inside project and when build I have issue where index.php.html file is created instead of index.php, when that file was in root.

I tried this in config

const gameRoot = `./src/projects/${project}`;

plugins: [usePHP({ entry: `${gameRoot}/index.php` })],

This generates index.php.html instead of index.php in dist when building. I don't know what could be causing this issue