Hi There I have a query on how to setup a laravel project in a team that is connected to LAN, I am using xampp and i have successfully share my htdocs folder, phpmyadmin, so others can access though "filezilla" now I want to know how to share command prompt(cmd as windows users) because laravel project are more based on command line so i need to share my cmd or xampp shell
eg:- laravel command accessed through cmd :-
"php artisan make:migration create_users_table"
so server can execute the command successfully but what about other users who are connected to me through LAN
They just need to connect your computer through the command line using the IP, Port , username & password. Other thing is you need to set correct permission setting for the project folder.
Related
I was passed a laravel backend project that's already on cpanel, both the MySql database and the laravel project itself is already live on phpmyadmin.
I did some modifications on the files on my local machine such as on the models and adding new columns and I'm trying to migrate the changes on the live database. How do I go about this without messing with the live database?
I tried using ssh but I get even more confused on the whole process.
I tried setting my env file to the live database config but when I run migration on my local machine laravel terminal I get a series of errors.
How can I get out of this situation?
I took responsibility for a hughe project, a part of the project contains cronjobs to crawl data from a certain provider.
The project is written in Yii2 and it runs in Lando enviroment with docker desktop, on a windows10 machine with wsl2.
While working with the database container in phpmyadmin or in the browser everything connects nicely and runs fine. But if I try to call the cron from my windows or wsl console, I'm not able to connect to the database. (SQLSTATE[HY000] [1045] Access denied for user xxx#localhost, thrown by DB connector). The credentials are definitively valid, I'm using them all the time. The appserver container can communicate with the database.
I guess it has something to do with permissions windows host -> docker but I can't figure out where I have to change this this in docker or in lando (I'm not really experienced in docker unfortunately).
Any help or trick is welcome!
I have my staging site for a Laravel app hosted on a Google App Engine instance. The production site is hosted on Compute Engine and isn't a managed server so I am not as familiar with the set up on GAE - I wanted to try it out in order to eventually move our production site onto a managed server.
I'm having an issue where I can't figure out how to run php artisan commands on staging! I managed to use the google sdk and the cloud sql proxy in order to access the staging database, and I assumed I could use some kind of gcloud command to run the artisan command, like something like gcloud --compute="php artisan migrate" but I can't figure out the best way to do it.
I also have tried using GCP's in-app terminal to ssh into the instance, but it seems like I have no access to the actual project files within that ssh so I can't run the artisan commands.
Does anyone know best practices for running a migration on this type of server?
I'm also using an app.yaml file to build the instance, so I was thinking maybe I should figure out how to put the command there, but I'm not sure if that's the right move as the only information I have in that file is the env info and server resources info.
Please help! thank you :)
One way of running migrations to your laravel project that is hosted on Google App Engine would be to connect your local environment project to the project's Google Cloud SQL. From there you can just run the migrations from your local environment.
Like #TMK said, connect through the SQL proxy. It's simple.
Create an SQL instance using the instructions found here
Follow the instructions here
with that done, you can run your migration command right from your bash terminal
I am very new to the server side of development, and I am trying to implement the Koel music streaming service. Koel install. I have done everything up to the .env modification. I have modified it following this guide, I replaced the admin name, email, and password to fit my credentials. I am lost on what to do next, do I need to launch a localhost server, and then run the command php artisan koel:init?
I have a working Laravel application on my desktop. I am trying to deploy it to a godaddy server. The application has been copied and verified on the server in the same structure format as on my desktop. I have changed the database information in the config to the proper entries. When I run from the server I get the error:
FatalErrorException
Class 'name of the class' not found.
The error is generated in the Routes.php file.
Again this app works locally, any idea why it errors when deployed?
Assuming you have a VPS server running Apache (or whatever else) with a a properly configured vhost and terminal (ssh) access, if you want deploy a Laravel app there, you surely need to
Copy all project files, except for the vendor directory, from localhost to your server
Verify file ownage and access rights (chown/chmod)
Change all necessary config
run a composer update
run php artisan migrate to create the database scheme
clear cache php artisan cache:clear
Next thing is populating the database with your apps data from localhost. You can either do it manually (dump sql local, import it on server), or if you want Laravel for it you can use Seeding (Laravel docs).
There even is a nice package that let's you automaticaly generete Seeders from your current database content - so it's very useful for the purpose of moving the app to another server.
https://github.com/orangehill/iseed
Inverse seed generator (iSeed) is a Laravel 4 package that provides a
method to generate a new seed file based on data from the existing
database table.
EDIT
If you are using a shared hosting account, check out this guide
http://driesvints.com/blog/laravel-4-on-a-shared-host
This post from Laravel forum might also be of use
http://forums.laravel.io/viewtopic.php?id=9639