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
advanced app - requirements.php - ln command incorrect #1606
Comments
A solution might be as follows:
|
* master: (27 commits) fixed div/0 issue in console progress bar console HelpController use correct script name support table aliases for ActiveQuery::joinWith(). guides fixed/improved CS fix improved fixture controller Added back border to debugger toolbar. #1788 info about retaining the default scenario fixes #1606 Default name and title added to GitHub auth client. added classes to grid, list and detail view fixed basic app travis debugging travis debugging travis added debug toolbar background to have line separators fixed paths in travis.yml reverted 1e4c1ec to get a working debug toolbar fixed issue with too long th columns in debugger enabled acceptance tests for basic application run basic app functional tests within the main repo test chain ...
@cebe : It still think it will not work with this ln. The ln syntax is wrong |
The comment above the
|
What is the purpose of the ln instruction then? If I move it I need to change it - ok. However, if i ln it I would like to keep it like it is. Because otherwise I need to copy it and cannot link it. Or do I miss something? |
Ah, got it. Changed the docs to use symllinks instead of hardlinks to make |
Ok. Explain a lot. But still the syntax of ln is just vice versa. And you should exchange the hard link in the text by soft or symbolic link. ln [OPTION]... [-T] TARGET LINK_NAME |
fixed, thanks |
The comment line
ln requirements.php ../requirements.php
is incorrect. It is ln . Besides, the web dir is two levels below.So it should be
ln ../../requirements.php requirements.php
if one is sitting in the web dir.And even if you do it like that it will not work from the web since the
$frameworkPath
is then incorrect. So one actually needs to copy it into the web root and then change the paths.The text was updated successfully, but these errors were encountered: