-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[#1025] Feature/add deploy tools cookbook #1782
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@weaverryan also if you can i notice all actianables are 5months + older, is there a way you could flag some more actionables more recently? thanks |
There are several ways you can deploy a symfony2 application: | ||
|
||
* One way is moving the files manually or via ftp if you don't use versioning | ||
(e.g. git). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replace the dot with a semi colon
thanks @wouterj done |
thanks @jmather :) |
@cordoval glad to help. |
Hi Luis! I think this can be a very great entry - something people will be looking for and also which we can evolve as a community (which will spark nice discussion). But before I merge this in, I'd like to propose a slight reorganization. Specifically, what do you think about starting the article with a section that details all the different things that are necessary on a deploy, regardless of your tool. For example:
I'd like a very easy-to-read (some sort of bulleted list with notes) place where people can go to learn the steps required in deployment. Then, in the next section, you can go on to discuss different methods for accomplishing these items, as you're doing now. What do you think? Thanks! |
@weaverryan I totally agree. I have kicked @cordoval (yet) another PR with an updated introduction. Good thinking! |
Added suggestions by @weaverryan at symfony#1782 (comment)
* Removed some less-technical details to make things shorter, to the point * Added a section which lays out the specific commands you always need to run after transferring source code * Proofread and fixed any markup errors
Hi guys! I've patched this into the 2.0 branch at:
I also made my own changes at sha: 2f9cfb6. Those changes look substantial, but a lot of it is subtle markup changes and reorganization of sections. The biggest thing to check out is the new section I added called Thanks to @cordoval and @jmather for your work bootstrapping this! Perhaps this can become a resource that grows and grows with the knowledge of the full community :). Cheers! |
Glad I could help. I will look at your changes tonight :) |
ref #1025