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.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • 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.
Please rate this library. Is it a good library?

Example code of doofinder/doofinder-magento2

Informations about the package doofinder-magento2

Doofinder for Magento 2

Build Status

IMPORTANT: If you are in trouble with the module, please contact Doofinder Support from the Doofinder website.

Docker Environment

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 the internet (to receive a callback).

To do so, you can use, for example, the utility ngrok: https://dashboard.ngrok.com/get-started/setup

Once the external URL is created, simply set the MAGENTO_BASE_URL environment variable (see Environment Variables).

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.

Get composer credentials

[!IMPORTANT] It is mandatory to obtain credentials for composer usage. These fields can be obtained by creating an access key into your Magento marketplace account. The public key will be COMPOSER_AUTH_USERNAME and the private key will be COMPOSER_AUTH_PASSWORD environment variables (see Environment Variables).

Environment variables

[!TIP] You can create an .env.local file to override the environment variables defined in .env such as composer credentials or Magento installation data to fit your needs.

For example, below is a base .env.local file:

The Makefile automatically overrides .env vars with the ones found in .env.local.

[!IMPORTANT] The Makefile internally appends --env-file .env --env-file .env.local to docker compose command for properly configuring container environment. So take it into account when interacting directly with docker compose.

Initial setup

You can set up a fresh Magento installation using the provided Makefile targets init or init-with-data. This command will:

Finally, Magento 2 with the module installed will be running at http://MAGENTO_BASE_URL.

The admin panel will be available at http://MAGENTO_BASE_URL/admin. Admin credentials are defined in the .env, if you used the env.example would be:

Xdebug ready to use

If you wish to debug your new Magento installation, simply uncomment the XDEBUG_CONFIG environment variable in docker-compose.yml configure your IDE accordingly and have fun!

Varnish was added to manage cache

By default Varnish is commented on docker-compose. So if you need to use it, you can uncomment and restart your containers. To enable Magento to use Varnish as cache manager, you can follow the official doc from Adobe: Configure the Commerce application to use Varnish.

If you uncomment Varnish container, remember to comment the port 9012:80 in the web container.

Uninstall the module

You can remove the Doofinder module using this straightforward method:

Test another versions

Change your branch to the tag that you want inside package directory

Backup and Restore Database

During development, it is sometimes useful to create a data snapshot before performing an action.

Important details before pushing changes to GitHub

In order to be able to merge a PR, the PHP Code Sniffer must pass without any warnings. To check the compliance of Magento 2 standards, first check that you have PHP >= 8.3 locally (it might also work with PHP 7.4, but in the Adobe Commerce Marketplace PHP 8.3 is used for the tests) and then execute at the root folder of this project composer install command and finally execute vendor/bin/phpcs.

PHP compatibility

This plugin has been thoroughly tested and confirmed to be compatible with the following PHP versions:

✅ Supported PHP Versions:

⚠️ Note:

Tested compatibility with the following M2 versions

Last notes

Please take care when you change the environment variable MAGENTO_VERSION, since you will have to change probably the PHP_VERSION and the 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:

Troubleshooting

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:

All versions of doofinder-magento2 with dependencies

PHP Build Version
Package Version
Requires magento/framework Version >=101.0.6
guzzlehttp/guzzle Version *
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package doofinder/doofinder-magento2 contains the following files

Loading the files please wait ....