Is it safe to install jetstream for an existing laravel project? - php

I want to use jetstream for auth.
I create the project earlier and already worked on it. Now I want to use jetstream.
But in the official documentation of jetstream I found this warning:
"New Applications Only
Jetstream should only be installed into new Laravel applications. Attempting to install Jetstream into an existing Laravel application will result in unexpected behavior and issues."
Now I want suggestions that how I can use jetsteam without any issue in my existing project.

probably there should be no problem if you are using git . just commit your latest changes and add jet stream .
there is an issue on Jetstream GitHub page about it
Please, give red visible warning for peoples, that Jetstream will overwrite your existing work, and it is meant to be install only on fresh installations.
check it out
update :
well , I have added Jetstream to my existing project which working on it for four months , there was a problem with font awesome Vue version which deleted that and going to add it again with newer version
, there was some bugs but was easy to resolve , so if you backup your project its totally ok and works fine , but you have to setup your project again with previous tasks you have done before

Related

Laravel abandoned dependency issue

So I just took over a laravel 5.2 based project with some dependency hell.
The backend is build on a smarch/watchtower package which has been abandoned and laravel 5.3 is the highest version it supports.
tsawler/laravel-filemanager is one more abandoned package.
Now I would like to update the whole project to the latest version of laravel to enjoy the new features, bug fixes and security patches and add the possibility to use other packages.
What are the best practices in such a situation?
Should I go with hijacking the abandoned packages one at a time and update them,
find similar packages with strong community support and replace the abandoned ones,
build the whole project from the start on a fresh copy of laravel 6
or accept the truth and continue on the old version?
any other suggestions?
Links to abandoned packages:
smarch/watchtower
tsawler/laravel-filemanager
Typically, I use packages from vendors that I know will be kept updated (such as Spatie packages). In place of Watchtower, you could use [laravel-permission] https://github.com/spatie/laravel-permission. However, tsawler/laravel-filemanager did install on Laravel v6.x. Though it says use https://github.com/UniSharp/laravel-filemanager so I'd install that instead.
From there you can upgrade from 5.2 to 6.x yourself or have a service like Laravel Shift do it for you. I create a new laravel instance and diff the directories to see what files changed. Also, make sure you read the upgrade guide: https://laravel.com/docs/6.x/upgrade. This might help as well: https://laracasts.com/discuss/channels/laravel/laravel-52-to-6?page=1

How to upgrade existing project from Laravel 5.3 to Laravel 5.5?

I am new in Laravel. I want to upgrade my existing Laravel project (a web with Laravel 5.3) to Laravel 5.5 because Laravel 5.3 have different structure than 5.5. If will upgrade all my files will be automatically follow there new directory or I have to made changes to my files to work properly.
It actually depends on your project size, since the estimated upgrade duration is 1-2 Hours, you might simply wish to copy almost all your files (one by one of course) to a newly installed Laravel 5.7, since it's the current latest version. Otherwise you should do it for every version by following the documentation.
https://laravel.com/docs/5.4/upgrade
https://laravel.com/docs/5.5/upgrade
https://laravel.com/docs/5.6/upgrade
https://laravel.com/docs/5.7/upgrade
I usually copy my files over to a new project if the project is small.
Otherwise I simply follow the guide.
Please follow the steps:
open composer.json file and change the version 5.3 to 5.5 and also upgrade the PHP version to at least 7.0
Delete composer.lock file
Delete Vendor Folder
Open Terminal and run the command (composer update).

Configure Laravel project in Netbeans 8.2

I am using Netbeans 8.2 and I want to use it for Laravel project. I know it is possible to create a Laravel project in Netbeans without going to cmd (This is what I am trying to achieve) I have followed these steps to create a Laravel project
Install Composer on your system
Installer the Composer plugin for Netbeans (It's in the plugins menu, under the PHP category).
New Project > PHP Application
Go though the wizard, and setup your project. the last step should be named Composer
In the last step,search (under Token:) for laravel
Select laravel/laravel: The Laravel Framework. and move it to the selected frameworks on the right
Click Finish, and you're Done!
Everything went fine! and I am able to create a laravel project from wizard unfortunately as I can see some folders and files (which are always there in Laravel ), I have spend some some hrs searching for a guide on how to integrate Laravel in Netbeans without success. Please help what is wrong with my steps?
My Netbeans project structure

What files and folders to copy when moving Laravel Project

I'm kinda still finding my way around the Laravel development framework. I want to use a Sample Project Here for my learning
Now the project was done in Laravel 5 and i'm trying to use the Latest 5.5 Laravel.
How do i go about this and what files and folders do i have to copy to my Laravel 5.5 project to get this working.
The file and code structure has changed quite a lot from Laravel 5.0 to Laravel 5.5.
If you are wanting to use that project on Laravel 5.5 then you would need to go through the update process for each version until you reached Laravel 5.5. These can all be found in the Laravel documentation for the respective version.
An easy, and better approach, would just be to incorporate this into your project manually.
SB Admin is just a theme based on Bootstrap and so you can just incorporate it into your app as you would Bootstrap.
You can download the source for SB Admin here - https://startbootstrap.com/template-overviews/sb-admin/
You can also check out the source on GitHub if you need more of an idea on how to use it on specific pages - https://github.com/BlackrockDigital/startbootstrap-sb-admin
If you really want to use that project to learn Laravel then you can. As you're still new to Laravel, I wouldn't bother updating it (you'd likely be in over your head).
To get started with the project, just follow the instructions on their repo - https://github.com/start-laravel/sb-admin-laravel-5:
Clone the project git clone https://github.com/start-laravel/sb-admin-laravel-5.git
Switch into the newly created folder
composer install to install Laravel and the required dependencies
npm install
bower install

Composer: Updating a Project Created with `create-project`

Does composer provide a way to update the package a project was created with? i.e., if I create a new laravel project with the following
composer create-project --prefer-dist laravel/laravel blog
Composer will grab the latest version of the laravel/laravel package, unarchive it into the blog folder, and then run composer install from the blog folder.
What I want/need to know is, does composer provide a way for me to update the laravel/laravel package that was downloaded to the blog folder? I know I could run composer update inside the blog folder myself, but this will only update things listed in the compser.json's require property — it will not update the unarchived laravel/laravel in blog (or will it?)
As far as I know it's not really possible.
Imagine that you create a new as example Laravel project.
The composer create-project creates the skeleton with all initial routes in your configuration etc.
From the very very first moment you are starting to change the default routes, removing the default controllers and changing the default views, your project would be out of sync. because meanwhile laravel changes the skeleton to newer versions with some new default routes etc or event changes directory structure.
It would be really hard to merge those changes over your existing application.
A better solution would be to follow the "Upgrade guides" (laravel: https://laravel.com/docs/5.4/upgrade) and then just commit those changes to your own project.
If you want to upgrade to a new laravel version, you can always follow the upgrade guide for your specific version:
Laravel 5.8 to 6.0
Laravel 5.7 to 5.8
Laravel 5.6 to 5.7
Laravel 5.5 to 5.6
If you are more than one version behind, you need to apply the previous upgrade guide. So if you are on 5.6 and want to upgrade to 5.8, you need to follow the guide for 5.6 to 5.7 and then from 5.7 to 5.8.
The guides are pretty helpful: they tell you which package must be updated to what version and inform you about deprecated methods which will be removed in the upcoming versions.
Another method which you can use to upgrade to new minor versions is to just look at the differences from one laravel release to the next. That way, you can see what exactly has changed and which files are new (configuration files for example which you can copy and paste into your project as the default composer create-project command would do).
As for the current version, you can see the commits since last release here: v5.8.30 to 5.8
Directly under the headline for a release, there is a small link labelled "36 commits to 5.8 since this release" which will take you to the link above, just for the latest version.
That's not the goal of composer, that just manage your packages.
You should see composer create-project just as a shortcut of git clone + composer install. If you need to deploy your application you've multiple options, from a simple git pull, to more advanced deployment tools like Capistrano. But composer isn't one of these tools.
I just needed to do this, and I couldn't find anything simpler than a git clone and a git pull (as #Federkun). Maybe an alternative would be to publish a phar file for the project and download that?
I can see db-ping does this. It's based on joomla/using phar. Here is the main file for building, inspired from joomla's file.

Categories