-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Exclude user_guide if CodeIgniter is installed via Composer. #5843
Comments
Well, how do you propose to do that? The |
I'm not familiar with composer packages. Normally, it can be excluded by add this line:
Into |
I agree with @indrakaw, installation via composer should be fast and light-weight, which means non-required files should be excluded. As suggested, the folder should be included in |
Apparently all This might take while, I'm installing the package via composer as commit as version pointer. Update:
It was installed via:
Update 2: |
I tried multiple tests and it works. I had to forked the release branch then make a commit change on And this is the local test:
{
"repositories": [
{
"type": "vcs",
"url": "https://github.com/indrakaw/CodeIgniter"
}
],
"require": {
"codeigniter/framework": "dev-gitattribute-release-test"
}
}
I tried another installation just by
|
Hi. Is it possible to get Edit:
Your contribution did reduce the package directory into several MiBs. You could've done it better by excluded the source file for user_guide too, as mentioned above:
Excluding the source file can be done by modify this line on Line 22 in 0648ae2
Into: |
This is probably similar to #3831.
If possible, I'd to exclude
user_guide
directory to keep the file size when using composer down. It's quite big, compared to core directories:Installed with
--prefer-dist
Installed with
--prefer-source
I'm in favor of ignoring it, The idea is that when using the library as is on a prod server, you don't end up with files that can be used for full path disclosure.
https://www.owasp.org/index.php/Full_Path_Disclosure
Addendum:
My thoughts were that when you are using this (or any other package), I would typically look through the code and the documentation online instead of reading through a docs folder in the vendor directory.
The text was updated successfully, but these errors were encountered: