Laravel - Blank canvas

Asked

Viewed 1,862 times

1

What I need

I want to check if a blank Laravel project is working properly on the development server, IE, I just want to see if at least it loads the view, and then I’ll do some tests.

What I did

I downloaded and installed Laravel locally, set up the app/path in config/app.php and passed the folder to the server. When accessing the folder "public" I received a blank screen, without any error. Below follows the code exchange I made in the route file. I changed it to play on the screen a Hello World and it worked.

OBS: It is running normally on my computer, calling the standard view of Laravel 5.

The tested code

Route::get('/', function()
{
    return 'Hello World';
});

The standard code

Route::get('/', 'WelcomeController@index');

Config/App.php

'url' => 'http://endereco_do_servidor/pasta/pasta_meu_projeto/',

Permission in folder

Just to let you know: the project is as follows on the server http://endereco_do_servidor/pasta/pasta_meu_projeto/',. I have the ip address of the development server, within it there are 3 folders with each type of project, within one of these folders there are other folders, each for different projects, and one of these is the project I just created.

I was informed that it was necessary to give the necessary permissions, so I asked them to give a chmod 775 for all the folders inside it.

find . -type d -exec chmod 775 {} \;
  • It could be many things, your server has the sufficient requirements? Try following the documentation instructions, as changing the url address in the app/config is only relevant for console commands.

  • @gmsantos Inside the folder I ran the command "find . -type d -exec chmod 775 {} ;" to release the permissions.

  • And that solved the problem?

  • Good, I still don’t understand where the question is! From what I read it’s all working...

1 answer

1


I don’t have direct access to the server, but I’ve been briefed on the procedure required for operation. When accessing the webserver files, Apache uses its own login, this login was not included in the owner’s group, so the 775 command did not work, but 777 (allowing full access and control by external users). The apache user was placed in the same group as the owner of the folders and was directed to permission find . -type d -exec chmod 775 {} \; to the folder Storage, leaving the Apache with full permissions, but external users with their limitations.

  • I may be talking nonsense, but I thought only data folders needed permission, but I have no experience with this to be sure.

  • @Guilhermenascimento Only the folder Storage requires permission.

  • It’s more or less what I meant, I didn’t understand the need of the user "apache" in the same group.

Browser other questions tagged

You are not signed in. Login or sign up in order to post.