Download the PHP package doofinder/doofinder-magento2 without Composer
On this page you can find all versions of the php package doofinder/doofinder-magento2. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download doofinder/doofinder-magento2
More information about doofinder/doofinder-magento2
Files in doofinder/doofinder-magento2
Package doofinder-magento2
Short Description Doofinder module for Magento 2
License OSL-3.0 AFL-3.0
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package doofinder-magento2
doofinder-magento2
IMPORTANT: If you are in trouble with the module, please contact Doofinder Support from the Doofinder website.
Docker Environment
NOTE: If you are in Windows or WSL, probably you'll have to fix CONTROL-M (^M) carriage return characters in
build.shfile. Run this command to get rid of this characters:
Configure NGROK In order to be able to create an account or login to an existing Doofinder account during the module initial setup, you will have to expose your local webserver to internet (to receive a callback).
To do so, you can use, for example; the utility Ngrok: https://dashboard.ngrok.com/get-started/setup
And once you have the external url created simply edit the .env file and set the MAGENTO_BASE_URL={your-url.ngrok-free.app} (for example: MAGENTO_BASE_URL=forcibly-ethical-apple.ngrok-free.app)
So, when the installation process finished, instead of accessing to http://localhost:9012 you will use your url (for example: http://forcibly-ethical-apple.ngrok-free.app).
Notice that you'll need to specify the 9012 port when executing ngrok.
Then setup the environment by executing:
from the base directory where the docker-compose.yml is located.
The installation process will take some minutes to be finished. You can follow the status logging with:
Finally, Magento 2 with the module installed will be running at http://localhost:9012.
The admin panel will be available at http://localhost:9012/admin. Admin credentials are defined in the .env, if you used the env.example would be:
To install sample data, with the containers running, you can simply execute:
In order to make this script work, the only thing you'll need to do is to fill the username and password fields in the src/auth_json file, with the same values used previously in the .env file, base your file in the auth.json.sample file.
OR if you'd rather load the data manually, you can also:
Note: After you run the command you will be prompted for authentication:
. You will have to use simply the same Magento repository tokens that you used in the .env file:
These fields can be obtained by going to Your magento marketplace account and creating an access key. The public key will be COMPOSER_AUTH_USERNAME and the private key will be COMPOSER_AUTH_PASSWORD.
Xdebug ready to use
If you wish to debug your new Magento installation, just simply set the correct values in .env and configure your IDE attending to the remote PHP docker container web. You should also bind your local source path: ./src to the docker one: /app
PhpMyAdmin ready to use
Once the installation has finished, you can also access to a ready to use phpMyAdmin local server listening in port 8080: http://localhost:8080.
Here you will see all the Magento 2 tables in the database specified in the file .env (by default: magentobase)
Uninstall the module
You can remove the Doofinder module using this straightforward method:
Manual Uninstall
Test another versions
Change your branch to the tag that you want inside package directory
Go inside the magento container
Last notes
Please, take care when you change in .env the MAGENTO_VERSION parameter since you'll have to change probably the PHP_VERSION & COMPOSER_VERSION ones in order to maintain the compatibility. For example, if you wish the Magento 2.4.3 version you should have:
but if you want to test, let's say, the 2.3.1 version you should have something like this:
And please, don't forget to copy in .env your Magento repository tokens filling the parameters:
Troubleshooting
Permissions issues
After running the bin/magento setup:upgrade or other magento commands inside the docker container some folders are created and the user running apache can loose permissions to execute returning 500 Error.
To restore permissions for these folders run in the host terminal sudo chmod 777 -R src/.
Redirect issues
If after the setup process has finished the website doesn't load you may need to change the urls in the database.
Connect to the database in localhost:3312 using the mysql user and password defined in the .env (magentobase).
In the table core_config_data there are two configs for the base urls that magento will redirect to, with paths:
web/unsecure/base_urlweb/secure/base_urlMake sure that those urls are the ones you'll be using to connect to your site or magento will always redirect to them.
