I'm having trouble running telescope in an environment with apache + php 8.1 on a centos 8 server.
i would not like to install node on this machine to fix the problem, i kept the same folder name for publishing "/var/www/public"
I tried using php artisan vendor:publish --tag=telescope-assets --force but was unsuccessful.
the same project on my local machine runs normally
Related
I am building a laravel environment with docker.
I want to run the php artisan command.
Laravel v9 fails to run because it runs on the global 7.4 instead of the php version 8.1.4 running in the container.
How can I get php 8.1.4 to start?
Laravel is running from the following DLL image.
https://hub.docker.com/r/bitnami/laravel
I'm setting up a Laravel 6 project to use Homestead per-project, but running into a Catch-22 when cloning the repo on a machine without PHP 7.2 installed locally.
The issue is that Laravel 6 requires PHP 7.2 (I have 7.1 installed locally), which means composer update will not work locally:
This package requires php ^7.2 but your HHVM version does not satisfy that requirement.
which means I cannot vagrant up to get to the Homestead box (that includes PHP 7.2) without having run composer update:
Message: LoadError: cannot load such file -- /Users/.../.../vendor/laravel/homestead/scripts/homestead.rb
which means I cannot get anything working.
To get around this, I either have to a) upgrade my local machine to PHP 7.2 to be able to run composer update or b) install Homestead separately and run vagrant up from there, both of which bypass the benefit of a per-project set up.
Is there something I'm missing to get this configuration to work?
I want to run my older project after installing a new OS.
I have cloned that project in htdocs, but it is showing a 404 error in the browser.
I have run these commands:
composer install
composer update --no-script
php artisan key: generate
php artisan migrate
I successfully installed the latest Laravel framework on my Centos 7 VHost.
After the composer command was done installing it, I created a new Laravel project.
For that I went o /var/www/ and created a folder there called "great" , then I changed directory to enter it, so pwd showed me
/var/www/great/
Then I ran this command:
composer create-project laravel/laravel myproject
The last one, created (as expected) a new folder inside the "great" folder called "myproject"
According to the Laravel installation instructions, I changed my directory to be inside the myproject folder and when I run
php artisan -V
I get:
Laravel Framework version 5.0.16
then I ran the command
php artisan serve --host 192.168.1.60 --port 80
with 192.168.1.60 being my vhost's IP address. So i expect to be able to see the Laravel page from my other computer (windows) when I access the ip in my browser, but it's not happening. All I get in my browser is:
ERR_CONNECTION_TIMED_OUT
At first I tried it without specifying the host or the port... same result. Then I discovered that I need to specify the host in order to be able to access the project from locations other than localhost. So I tried accessing it by going for http://192.168.1.60:8000 (because that is it's default port). Same result.
I can ping the IP, on Centos side I do not get any error when I run the artisan serve....
What am I doing wrong?
I'm trying to deploy a locally working Laravel 4 project on a Strato server.
Locally I can execute the command php artisan migrate, but when I'm trying to execute this command on the server using PuTTY command line, it throws the following exception:
[InvalidArgumentException] Command "migrate" is not defined.
These have been my deployment steps:
Install basic laravel application locally, using composer (path variable)
Upload all files to the server. Now the warning, that a database column couldn't be found is visible. So I want to migrate the database.
Run the command php artisan migrate
When I run the command php artisan list there are a few methods listed like tail and workbench, but not the commands that I need.
PHP 5.5 and MCrypt are installed on the server.
Do I have to extend the artisan installation?
Update:
The problem seems to be the following:
Warning: Composer should be invoked via the CLI version of PHP, not
the cgi-fcgi SAPI
Futhermore there is this warning:
Warning: The lock file is not up to date with the latest changes in
composer.json. You may be getting outdated dependencies. Run update to
update them.
Running update doesn't work, because it tries to run a mising artisan argument.