Before asking a cursory look at the next online tutorial, foggy.
Q1: Does using Phar Packaging require special handling of the current code? For example my current project, if in this way to the official server update version, need to modify the previous code no?
Q2: For example, I packed up project.phar
, before the project entrance is Index.php
, then the package after apache
the direct change of the index file to add one on the project.phar
line?
Q3: How can I update the version seamlessly? I have previously uploaded the new version of the file, and then modify the previous site folder name (such as add a _20141030), and then change the name of the folder just uploaded to the previous site folder name! But this will also have about 3s
~ ~ 5s
about the interruption.
Q2 I'll try it by myself after work! can be ignored!
Reply content:
Before asking a cursory look at the next online tutorial, foggy.
Q1: Does using Phar Packaging require special handling of the current code? For example my current project, if in this way to the official server update version, need to modify the previous code no?
Q2: For example, I packed up project.phar
, before the project entrance is Index.php
, then the package after apache
the direct change of the index file to add one on the project.phar
line?
Q3: How can I update the version seamlessly? I have previously uploaded the new version of the file, and then modify the previous site folder name (such as add a _20141030), and then change the name of the folder just uploaded to the previous site folder name! But this will also have about 3s
~ ~ 5s
about the interruption.
Q2 I'll try it by myself after work! can be ignored!
Q2, if it is nginx, you can create a new conf, and then use the nginx-c to specify root for seamless update ....