by Devin Yang
(This article was automatically translated.)

Published - 6 years ago ( Updated - 6 years ago )

I was told by my friends that according to Murphy's Law, the promotion is always so difficult. Of course, I have to show him how smooth I am. I'm not afraid.
I also added a column by the way.
php artisan make:migration add_disabled_to_users_table --table=users
Then, you can add column data.


By the way, grab the content of the conversation between me and my friend, I didn’t talk nonsense, I really upgraded the system very quickly, and the upgrade was very fast.
The following is the content of the conversation with my friend, he said "upgrading is always so difficult", so I will upgrade smoothly for him to see: p

 
I am not afraid of directly rising. (In fact, I secretly prepared some information)
Because it will be backed up automatically every day, plus the manual backup function built in my background, I will make another backup.


My "version background" usually only maintains the latest version of Laravel, that is to say, there will be no problem with the update of the small version number.

And "Bugs problem tracking background", although the version is relatively old, it was developed based on my "version background" (Laravel version 5.4),
But because of the MVC architecture, I only need to throw the template used by Bugs into the new SEO background (5.6.x), and then the Bus background can be updated smoothly (no problem). :p
Rather than upgrading the "Bugs Tracking Backend" (Laravel 5.4.x), I'll just accept the sample that sets the "Bugs Tracking Backend" (Laravel 5.6.x) as the "Bugs Tracking Backend".
At the beginning, when I was developing the "pattern background", it was a background that adopted the MVC architecture, could be reused, expanded freely, and defined and expanded any template.


So instantly update the background of the three Productions at the same time. Wiki background, Bugs background for problem tracking, and MIS background for defining various specifications.
Finally, please do not learn from me directly, execute migrate in the Production environment, because I have practiced it.
Unless you are the only one developing the entire system, and you understand it well, there will be no problems.



In the follow-up...., I will post the upgrade results to my friend, and he asks if I can make a shit button. :D

Tags: laravel

Devin Yang

Feel free to ask me, if you don't get it.:)

No Comment

Post your comment

Login is required to leave comments

Similar Stories


laravel

Let's run Laravel

If you haven't heard of D-Laravel, let me introduce it. D-Laravel is a Laravel and docker execution environment built with docker-compose. Let us quickly generate Laravel projects through simple bash. This article teaches you how to use the docker image provided by D-Laravel to build a swoole execution development environment. After reading this article, you should be able to quickly create a swoole execution environment through D-Laravel.

laravel,laravel livewire

Laravel livewire file upload demo

Livewire is a full-stack framework for the Laravel framework. It was the first time I wrote code, and he was probably the one who was able to write and marvel at the magic. My colleague also marveled while writing after being pushed by me. When I first learned Vue, I was not so surprised by him.

docker,laravel

How to use multiple YAML files to execute multiple docker container services

This video introduces how to use the docker-compose command to specify multiple YAML structure language configuration files to create container execution, and introduces how we simplify docker-compose by using .env in the D-Laravel environment Start command.