-
Notifications
You must be signed in to change notification settings - Fork 42
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
Why there is no .htaccess file? #12
Comments
Hi there! Thanks for coming by and inquiring. The reason there's no
.htaccess is because this is a mirror of the official core package and the
official core package is not distributed with one.
…On Sun, Apr 22, 2018, 3:54 AM Almog Baku ***@***.***> wrote:
Why there is no .htaccess file?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#12>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/ATNtgr9PXY1BQnsMDNt-_Ior_0ioyR1fks5trEUogaJpZM4TeyJi>
.
|
If I'm not mistaken, the release version(zip file) does include it. |
Considering that the bot creates the tagged versions in this fork by
downloading the official release zips, it's definitely not in the release
zip.
…On Sun, Apr 22, 2018, 6:33 AM Almog Baku ***@***.***> wrote:
If I'm not mistaken, the release version(zip file) does include it.
It could be great if somehow you can force the bot to add it, since the
composer override this file everytime(and post-script is nasty)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ATNtgnZhsZep1gbGaPQO1_6Kpx7bWoIeks5trGp-gaJpZM4TeyJi>
.
|
🤦 looks like next time I need to verify the account it'll post to if I reply by email... Terribly sorry about any confusion from my accidentally replying from my bot account. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Why there is no
.htaccess
file for the distribution version?The text was updated successfully, but these errors were encountered: