Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Replace Capifony with Capistrano/symfony#5533

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Closed
mojzis wants to merge3 commits intosymfony:2.7frommojzis:patch-1

Conversation

@mojzis
Copy link
Contributor

Since Capifony only works with Capistrano 2 (https://github.com/everzet/capifony/blob/master/README.md) and Capistrano 3 is the current version, its probably better to advice using the newer alternative.

Since Capifony only works with Capistrano 2 (https://github.com/everzet/capifony/blob/master/README.md) and Capistrano 3 is the current version, its probably better to advice using the newer alternative.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

symphony while contributing to the Symfony documentation ? not good...

Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

sorry :)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

you still have symphony here

@wouterj
Copy link
Member

👍

(there are 2 minor spacing issues: one space too much before) and one new line too much at the end of the file, but we'll take care of these issues while merging).

@xabbuh
Copy link
Member

Do we really want to dismiss Capifony? Why don't we promote both?

@wouterj
Copy link
Member

@xabbuhhttp://williamdurand.fr/2015/04/11/on-capifony-and-its-future/ suggests that Capifony is there only for backwards compability and new projects should use either Capistrano v3 or other tools (like Docker). As this message is written by the maintainers of Capifony, I think it's better to no longer mention it (and btw, there still is a mention of Capifony).

@xabbuh
Copy link
Member

indeed, I should have thought about it 👍

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

where is the Capifony link defined?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

on line 192/193 (it already existed, so the diff doesn't show it)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

thank you@wouterj

@wouterj
Copy link
Member

Cool! Thanks for keeping the docs in sync with changes in Symfony tooling@mojzis!

wouterj added a commit that referenced this pull requestJul 23, 2015
This PR was submitted for the 2.7 branch but it was merged into the 2.3 branch instead (closes#5533).Discussion----------Replace Capifony with Capistrano/symfonySince Capifony only works with Capistrano 2 (https://github.com/everzet/capifony/blob/master/README.md) and Capistrano 3 is the current version, its probably better to advice using the newer alternative.Commits-------8f3ec0c Replace Capifony with Capistrano/symfony
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@mojzis@wouterj@xabbuh@stof@OskarStark

[8]ページ先頭

©2009-2025 Movatter.jp