-
Notifications
You must be signed in to change notification settings - Fork 22
Clarify "bundle exec rails server" should be run inside "my_awesome_app" #3
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
Comments
Hey, thanks for the feedback! I actually mention "To make a new Rails project, |
Hey! Thanks a lot for acknowledging receipt. I did read the phrase you mentioned. Problem is it's not correctly framed, I think. In its present form, it seems to mean what I described earlier. Let me explain why exactly. The problem could be the absence of a saxon genitive. Perhaps saying "into your project's folder" would make things clearer. The word "projects" (without the genitive) led me to believe that the Also, as far as I understand, it's not until the Overall, I think minimal editing and a simple reordering of the instructions would do. That section of the text would then look something like this: To make a new Rails project, run the following command:
Hope this helps. |
I actually meant "projects" folder as in "the folder which contains all your projects", not the folder for I totally agree that it's not obvious that you need to run the |
Ahh, I see. Thanks for the swift reply. |
This is a tiny omission that caused momentary panic at least in my case. If the text is followed to the letter, it appears that the command can be run outside the new project's folder. However, doing so makes the gem system grunt at you with a wonderfully descriptive "Could not locate Gemfile". Of course, little did I know that the solution was very simple: cd into the new project's folder, in this case "my_awesome_app".
The text was updated successfully, but these errors were encountered: