[#1025] Feature/add deploy tools cookbook #1782

Closed
wants to merge 8 commits into
from

Conversation

Projects
None yet
4 participants
@cordoval
Contributor

cordoval commented Oct 4, 2012

ref #1025

@cordoval

This comment has been minimized.

Show comment
Hide comment
@cordoval

cordoval Oct 4, 2012

Contributor

@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

Contributor

cordoval commented Oct 4, 2012

@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

cookbook/deployment-tools.rst
+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).

This comment has been minimized.

@wouterj

wouterj Oct 5, 2012

Member

Replace the dot with a semi colon

@wouterj

wouterj Oct 5, 2012

Member

Replace the dot with a semi colon

cookbook/deployment-tools.rst
+* If you use versioning you could still move things manually cloning or fetching
+ your repository from the final server folder location. However it is advised
+ you make use of better tools especially in the case where you have access
+ capabilities such as enough permissions in a virtual private server or similar system.

This comment has been minimized.

@wouterj

wouterj Oct 5, 2012

Member

same here

@wouterj

wouterj Oct 5, 2012

Member

same here

cookbook/deployment-tools.rst
+
+* Some projects are really large so they make use of more established tools for
+ deploying not only the files but really deploy a OS or package distribution
+ containing the sf2 project inside.

This comment has been minimized.

@wouterj

wouterj Oct 5, 2012

Member

and here

@wouterj

wouterj Oct 5, 2012

Member

and here

cookbook/deployment-tools.rst
+* Another important thing to keep in mind is the handling of dependencies.
+ One can use composer to fetch dependencies or include them all together with the
+ repository. Some tools would handle this for you and even perhaps avoid fetching
+ dependencies when a simple copy would do.

This comment has been minimized.

@wouterj

wouterj Oct 5, 2012

Member

and here

@wouterj

wouterj Oct 5, 2012

Member

and here

@cordoval

This comment has been minimized.

Show comment
Hide comment
@cordoval

cordoval Oct 6, 2012

Contributor

thanks @wouterj done

Contributor

cordoval commented Oct 6, 2012

thanks @wouterj done

@jmather

This comment has been minimized.

Show comment
Hide comment
@jmather

jmather Oct 6, 2012

There's a #symfony2 ? Aren't we all in #symfony?

There's a #symfony2 ? Aren't we all in #symfony?

@jmather

This comment has been minimized.

Show comment
Hide comment
@jmather

jmather Oct 6, 2012

configuring should probably be configuration

configuring should probably be configuration

@cordoval

This comment has been minimized.

Show comment
Hide comment
@cordoval

cordoval Oct 6, 2012

Contributor

thanks @jmather :)

Contributor

cordoval commented Oct 6, 2012

thanks @jmather :)

@jmather

This comment has been minimized.

Show comment
Hide comment
@jmather

jmather Oct 6, 2012

Contributor

@cordoval glad to help.

Contributor

jmather commented Oct 6, 2012

@cordoval glad to help.

@weaverryan

This comment has been minimized.

Show comment
Hide comment
@weaverryan

weaverryan Oct 8, 2012

Member

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:

  • Transferring the project files up to the server
  • Updating your vendor libraries
  • Running any database migrations
  • Clearing the Symfony cache

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!

Member

weaverryan commented Oct 8, 2012

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:

  • Transferring the project files up to the server
  • Updating your vendor libraries
  • Running any database migrations
  • Clearing the Symfony cache

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!

@jmather

This comment has been minimized.

Show comment
Hide comment
@jmather

jmather Oct 8, 2012

Contributor

@weaverryan I totally agree. I have kicked @cordoval (yet) another PR with an updated introduction. Good thinking!

Contributor

jmather commented Oct 8, 2012

@weaverryan I totally agree. I have kicked @cordoval (yet) another PR with an updated introduction. Good thinking!

weaverryan added a commit that referenced this pull request Oct 31, 2012

[#1782] Proofread and tweaks to new deployment docs:
* 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
@weaverryan

This comment has been minimized.

Show comment
Hide comment
@weaverryan

weaverryan Oct 31, 2012

Member

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 Common Post-Deployment Tasks. If you spot any issues with my changes, let me know! The entry is also specifically for Symfony 2.0 - I then upgraded it (i.e. changed things to say "Composer") after merging this into 2.1.

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!

Member

weaverryan commented Oct 31, 2012

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 Common Post-Deployment Tasks. If you spot any issues with my changes, let me know! The entry is also specifically for Symfony 2.0 - I then upgraded it (i.e. changed things to say "Composer") after merging this into 2.1.

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!

@jmather

This comment has been minimized.

Show comment
Hide comment
@jmather

jmather Oct 31, 2012

Contributor

Glad I could help. I will look at your changes tonight :)

Contributor

jmather commented Oct 31, 2012

Glad I could help. I will look at your changes tonight :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment