Open nanayaw-kirk opened 7 years ago
Did you do php artisan vendor:publish ?
yes
Are you testing with your web servers root set to the public folder?
@JayLancaster I realised that was the problem. I hard coded the path to assets and it works but I will very much appreciate some pointers to doing this dynamically so all my other projects don't suffer this fate ;) . I use xampp as my development server.
Currently the master layout is not published and realistically in production your environment would be set to have the public folder as your root for a laravel project as per the way the framework works. On that basis you will want to set up your dev environment to use that as web root. Your best bet is to use a Virtual machine to test (laravel homestead is a good choice)
It can be daunting at first to set up but more than worth the effort in terms of testing laravel projects. It tries to act as close to your production environment as possible and will smooth your workflow allot.
I am new to Laravel. I installed the Chatter forum package.
My directory structure on shared hosting is:
├── public_html/ │ ├── index.html (non-Laravel) │ └── assets └── project_name/ ├── public ├── index.php
When I visit http://www.mywebsite.com/project_name/ it shows me the page with the message "Laravel is a framework so it doesn't have a index page", and redirects me to http://www.mywebsite.com/project_name/public
After a lot of effort, I saw that the Chatter forum package was installed at http://www.mywebsite.com/project_name/public/forums
However, it failed to load the CSS and js, and permalinks are generated as "http://www.mywebsite.com/forums/discussion/general..." instead of "http://www.mywebsite.com/community/forums/discussion/general..."
Ideally, I'd like Chatter accessible at "http://www.mywebsite.com/community/forums"
I am using laravel 5.3 My app.blade.php
`<!DOCTYPE html>
````