-
Notifications
You must be signed in to change notification settings - Fork 14
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
Install MongoDB extension by default #7
Comments
Hi @alcaeus, it sounds great, I think it would be a great addition to XAMPP. The installer already includes optional PHP extensions (disabled by default) so users can easily enable them if needed. |
Hi Beltran, great to hear! Can you give me a few insights into how extensions are packaged in XAMPP? From reading the code, I understand this as follows:
|
Great research:
|
@beltran-rubo circling back to this now. We're building DLLs for Windows automatically as part of our release process, and they are attached to the GitHub release. Would those files have to be uploaded to sourceforge or is it possible to grab them directly from GitHub? |
We can pick them from the official MongoDB release at GitHub and include it into the XAMPP installer. We usually also upload to sourceforge to have all the thirdparty sources together for simplicity, we can take care of that. |
Hello! Before I blindly create a pull request, I thought I'd ask in the issue tracker first.
Would there be any interest to package the MongoDB extension so it's installed by default? At MongoDB we've received numerous support requests from people using tools like XAMPP and WAMPserver about not being able to get the extension running. Usually, these errors can be traced back to users not enabling the extension in the correct .ini files (typically only enabling it for the CLI so it shows up when running
php -m
but not when runningphpinfo()
in their web server). These issues could be avoided and the user experience improved by bundling the MongoDB extension.If this is not the right repository/channel for such an issue, please tell me where to open this discussion instead. Thanks!
The text was updated successfully, but these errors were encountered: