Problem with Mix manifest on shared hosting

In mix you can set

mix.setPublicPath('path/to/public');

mix.setResourceRoot('prefix/for/resource/locators');

You should be building the assets locally then publishing them

I would not be running npm on the production environment?

@michaloravec So if I understood in setPublicPath I should put '/..public_html/laravel-app'?

@snapey Actually I build the assets locally and after I load them to the hosting.

I think the problem is because the public folder is under public_html folder while all the app is outside so this change the path where to find the manifest

rename public to public_html in your development environment?

@snapey At the moment I change the AppServiceProvider like this and got it working

$this->app->bind('path.public', function() {
    return base_path() . '../../public_html/laravel-app';
});

So my guess is I have to set mix.setPublicPath('../../public_html/laravel-app'); next time I build my assets

@carpad88 So it works with mix.setPublicPath('../../public_html/laravel-app');?

Just out of curiosity, what's wrong with building assets in a production environment?

@michaloravec It works binding the public path on the AppServiceProvider I haven't try setting it up not he mix configuration.

I'll make another deploy trying that option to see if it works

@ktsubouchi I this case the app is deploy in a shared hosting where there is not possible to run npm so in order to get the app working I have to build my assets on local and upload them to the hosting.

Word to mention in local env all the app is out of the box in one folder while in production on this shared hosting just the public app is placed on the public_html while the other files are outside of public_html.