Laravel Livewire Starter kit

@ojwando when you access the page locally, then you have npm run dev enabled, and the Vite server is running. Since you shouldn't use a Vite server in production, you need to build the js and css, and then upload them.

I take it with upload you mean ftp.

I would suggest moving to using some kind of CI that does the build during your deploy.

@Snapey my website is running. The problem is with styles. I've been wondering why app.js has nothing. When I add cdn link for tailwind the original format is back but wilh a vertical scrollbar. You have to scroll to see content but sidebar is just okay

@ojwando exactly. Yes, thats what we are trying to fix here.

When you load the site, with developer tools open, and network tab selected, you see broken uploads for your css.

@Ayoola32 the site is running. The problem is styles

@srushti_kansagara

` import { defineConfig } from 'vite'; import laravel from 'laravel-vite-plugin'; import tailwindcss from "@tailwindcss/vite";

export default defineConfig({

plugins: [
    laravel({
        input: ['resources/css/app.css', 'resources/js/app.js'],
        refresh: [`resources/views/**/*`],
    }),
    tailwindcss(),
],
server: {
    cors: true,
},

}); `

@srushti_kansagara ``

look at this, ignore the first one:import { defineConfig } from 'vite'; import laravel from 'laravel-vite-plugin'; import tailwindcss from "@tailwindcss/vite";

export default defineConfig({

plugins: [
    laravel({
        input: ['resources/css/app.css', 'resources/js/app.js'],
        refresh: [`resources/views/**/*`],
    }),
    tailwindcss(),
],
server: {
    cors: true,
},

});

``

@srushti_kansagara index.php

`<?php

use Illuminate\Foundation\Application; use Illuminate\Http\Request;

define('LARAVEL_START', microtime(true));

// Determine if the application is in maintenance mode... if (file_exists($maintenance = DIR.'/../storage/framework/maintenance.php')) { require $maintenance; }

// Register the Composer autoloader... require DIR.'/../../blog.edufocus.co.ke/vendor/autoload.php';

// Bootstrap Laravel and handle the request... /** @var Application $app */ $app = require_once DIR.'/../../blog.edufocus.co.ke/bootstrap/app.php';

$app->handleRequest(Request::capture());

`

@ojwando did you write this index.php on your own ??? also please provide the folder structure if you can

@srushti_kansagara i edited index.php and the file is the one i have already posted

@Vable i have run npm run build . I have public->build->assets/manifest and inside assets i have app-BlPSe9NK.css and app-l0sNRNKZ.js but app-l0sNRNKZ.js is empty

It's not what I can see here : https://blog.edufocus.co.ke/register Look at the source code. 👀

@Vable Does what you're seeing at https://blog.edufocus.co.ke/register suggest that I haven't run npm run build?

@Vable

` c:\xampp\htdocs\exam-gen>npm run build

build vite build

vite v6.2.0 building for production... ✓ 2 modules transformed. Generated an empty chunk: "app". public/build/manifest.json 0.27 kB │ gzip: 0.15 kB public/build/assets/app-B4CTIKUE.css 165.41 kB │ gzip: 24.19 kB public/build/assets/app-l0sNRNKZ.js 0.00 kB │ gzip: 0.02 kB ✓ built in 5.16s `

@ojwando did you change your .env to APP_ENV=local to APP_ENV=production and changed the APP_URL ? also please try Clearing Laravel cache, view, route etc

@ojwando Have a look in the public folder of your application to see if there’s a "hot" file.

If it is present, delete it. Perhaps you have run an npm run dev on your production server or inadvertently transferred the "hot" file. This starts the Vite development server.

At that moment, Laravel detects this development mode due to the presence of the public/hot file. (which results in a URL like http://[::1]:5173/@vite)

@srushti_kansagara any strategy which starts with zip your files is flawed and should no5 be followed.

@Snapey ohh i didn't know that ... in my company i always deploy with the ftp they gave me the all the credentials tho so i don't know