Published - 5 years ago ( Updated - 5 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.
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.
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
No Comment
Post your comment