Improve generic deployment article #5158
Comments
|
It's probably not about incenteev parameter handler because if we follow the document, we have not installed any dependencies yet (done in the step after that). I don't know if there is a tool for that. If we deploy with capistrano, Incenteev parameter handler seems not to be the solution. The best place to store the parameters.yml file in a capistrano structure is in the "incenteev-parameters": {
"dist-file": "app/config/parameters.yml.dist",
"file": "../shared/app/config/parameters.yml"
}, |
|
Shit like this is why people think development is hard. It's not, people just suck at making documentation for just about anything. I lost count how many times I read a tutorial where lots of critical information was missing. Critical meaning information absolutely required to finish the exercise. i.e. lots of times I've seen tutorials that would say "add xyz code to your project", without specifying where in the project to place that code, or in which file, or exactly where in the file it should be placed. Also often missing is what exactly the code does, and why it's there/needed in the first place. Coding is the new magic. You say (type) a few words, and things happen, but no one is expected to know what those words do anymore. Frameworks were a blessing, but the more I get into them the worse this shit gets. There is absolutely no point in adding a function to your framework if the documentation for it sucks or is nonexistent. Documentation is the thing you use to tell other people what your function does. If you fuck it up/leave things out, how on earth is anyone supposed to know what that function does? |
|
@ThibauldNuyten I totally agree with you! That's why I love Symfony documentation. Everything works, you can copy+paste the code, they even include the necessary In the particular case of this article, the problem is that it's a vague and generic article on purpose. We have dedicated articles to explain step-by-step how to deploy Symfony apps to Azure, Heroku, etc. But this article is about some general notes and comments about deploying ... so it will always miss information needed in your particular case :( I can't think of a solution to this problem. |
|
@javiereguiluz I totally agree with you when you say that the Symfony Documentation is awesome and contains plenty of information. But for this case, I still don't understand what the quote from @wouterj refers to
This quote is still present in the current documentation. Which automatic utility is it referring to? |
|
Yes I am wondering what "automatic utilities" are myself. I agree with ThibauldNuyten. |
…l (javiereguiluz) This PR was squashed before being merged into the 2.7 branch (closes #8122). Discussion ---------- Improved the explanation about deployment + parameters.yml This fixes #5158. As usual, the explanations in this article are a bit vague, because this is a generic deployment article and it contains no details (we have dedicated articles to explain those details). Commits ------- 186458c Improved the explanation about deployment + parameters.yml
From the article:
We should better explain what the "automatic utilities" are. Afaik, it's only the incenteev parameter handler that's included in the SE? Or is there something from Symfony itself that handles his.
The step is also a bit strange as it only tells what not to do. Nothing explains what the user needs to do.
This was issue was submitted by a user on a dutch forum
The text was updated successfully, but these errors were encountered: