I pushed (bitbucket) a laravel 4 project from my imac and pulled it with another mac. What I get is a status 500 message if i try to visit /public.
I am using MAMP.
The strange thing is that every other laravel project is working fine. One project is even a copy of the project that doesn't work.
Any idea whats wrong?
Point Apache to a public directory instead of root one and use URLs without public in it.
Restart web server after that to make it work.
Related
Having some real problems installing a Laravel App on a Bluehost[ed] subdomain. I get a 500 error and checked a number of web-resources and tutorials.
Here's what I've tried:
A) A simple FTP of the MyGreatApp to the main domain root, copying the MyGreatApp public folder in the public_html/subDomainName/ as suggested by "Deploy Laravel To Shared Hosting The Easy Way" (but with sub domain thoughts) https://www.youtube.com/watch?v=6g8G3YQtQt4
But I get a http 500 error.
B) A similar method using SSH and cloning a git repository which contains the Laravel boiler plate.
In each case the boilerplate Laravel app doesn't run. I can echo out of the index.php to let me know what I get to in the PHP.
Many tutorials suggest changing the paths (for subdomains) in the index.php file too as the public folder of the subdomain is buried differently to the public_html of the main domain.
We are using PHP 7.1 on bluehost and Laravel 7
Any thoughts to get a stage beyond the 500 error?
EDIT: The error is thrown after attempting to execute this part of the code...
$response = $kernel->handle(
$request = Illuminate\Http\Request::capture()
);
Delete everything (backup the important files, I'm not responsible for any data loss)
Create folder laravelapp or whatever you want
Upload your laravel project to that folder
Create new subdomain and point to public_html/laravelapp/public
We figured it out. It related to a problem with the dev PHP environment and the prod. PHP environment. PHP(Dev) > PHP(Prod) and a version issue in Symfony. When we downgraded Symfony to the "right" level of PHP it's fine.
I've created my first full Laravel tool. (Yiehaaa).
I'm looking to host it somewhere for my customer as he wants to be able to use it from different PC's in his network.
Therefore I was thinking to put it on a Synology NAS (DS215j) which is already available.
I took following steps :
Install WebStation
Install PHP7
Install Nginx with MariaDB10
Imported all tables
My Webstation is up-and-running, telling Nginx is running with PHP7.
Under PHP settings, I enabled : mysqli, openssl and pdo_mysql.
In the end, I created a Virtual host PORT based (on port 85 for http and port 86 for https) and connected the main folder to "web/maintoolfolder/public".
As http back-end server Nginx is chosen, with PHP 7.0
When I now open following url http://nasname:85 , I get to see my index.php page without any problem ! So yeahhhhh...
But, whatever link I click which needs to open one of my routes, I always get the error message "404 page can not be found".
Strange thing is that this 404 page is not even the own created Laravel 404 page.
What am I doing wrong ? Why can't I move between the different pages?
Thanks in advance for any help.
best regards,
Davy
I am using laravel 5.2 to write services for a mobile app. all the calls are working fine. My project is deployed in ubuntu server.
Now I want to resize the uploaded images inorder to maintain same performance. I thought of trying intervention-image.
In local machine it worked fine. I installed intervention-image and set the provider and alias name, I included the alias name to controller. Once I do that and update the server, all the other calls are getting effected. I am getting 505 error.
It's the intervension-image which is causing this problem, I checked with previous upload and I am getting all the calls. Any suggestions?
I suggest you create a dev environment like your production , use vagrant . About error 505 check you error log file to have more detail about the bug
Strange problem: Have installed Laravels 'Valet' to serve sites from .dev locally. When I am in my 'code' directory where I parked valet and create say laravel new blog installed perfectly and spins up on blog.dev. However say I create laravel new test and visit test.dev I get 404 - nothing found ...? I removed everything and tried again but the same thing happens. Has anyone else had the same problem?
UPDATE
Interestingly, from that same directory 'code' If i run a ping on blog.dev I get returned packets and pings. However I do the same on test, I get bunch of help commands?
FURTHER UPDATE
So inside the project 'test' if I run php artisan serve I get a response of Laravel development server started: <http://127.0.0.1:8000> and If I visit the path bingo it works. But that confuses the issue even further for me...?
EVEN FUTHER UPDATES
So, I wish to add this iMac was a previous developers so the home folder is called Adam, I am a seperate user but also an Admin with my own folder sat next to it called 'Dan'but not a 'home' directory as such it is just in the sames 'Users' directory whenever I try to do anything I get errors like: ERROR: Notice: Undefined index: domain in /Users/Adam/.composer/vendor/laravel/valet/cli/valet.php on line 55 That was when trying to spin up laravel share
I'm new to AppHarbour and I'm trying to deploy my MVC app on a free account.
I keep getting a 404 error.
The app is coming from Bit-bucket and it was deployed successfully.
In my Hostnames section i see the following
so i have added the following to the Hosts file in my machine:
176.34.122.158 camelotfaultmanagement.apphb.com
but i still get a 404 ..
What am i doing wrong ?
And a follow-up question how can i edit one of the files to be able to edit the connection ?string to my DB?
It looks like you may not have any successful builds yet - You have to push to Bitbucket to trigger your first build. You can see a list of builds on the app dashboard: https://appharbor.com/applications/camelotfaultmanagement
To use the built-in .apphb.com domain, you don't have to mess with any DNS setup.