renttek / magento2-well-known
Package info
github.com/renttek/magento2-well-known
Type:magento2-module
pkg:composer/renttek/magento2-well-known
Requires
- beberlei/assert: ^3.3
- hyva-themes/module-magento2-admin: ^1.1
Requires (Dev)
- bitexpert/phpstan-magento: ^0.42.0
- ergebnis/composer-normalize: ^2.50
- mage-os/framework: ^2.2
- mage-os/module-store: ^2.2
- phpstan/extension-installer: ^1.4
- phpstan/phpstan: ^2.1
- phpstan/phpstan-strict-rules: ^2.0
- rector/rector: ^2.3
- symplify/easy-coding-standard: ^13.0
This package is auto-updated.
Last update: 2026-03-17 18:14:05 UTC
README
Important
This extension is WIP and not finished yet. The current state of missing features can be seen in the TODO.md
This extension adds a dedicated section to the Admin Panel for managing "files" within the /.well-known/ directory. It allows you to quickly create and serve plain-text or JSON content for specific paths (such as apple-developer-merchantid-domain-association or security.txt) without needing to touch the server's filesystem.
Installation
composer require renttek/magento2-well-known bin/magento module:enable Renttek_WellKnown bin/magento setup:upgrade
Usage
TBD (describe content management in the admin ui)
Extending / Custom provider for /.well-known/ content
If more control is needed, the extension also provides the Renttek\WellKnown\Model\WellKnownProviderInterface to implement custom providers for /.well-known/ content.
To do that, implement the WellKnownProviderInterface in your own code and register the provider with the Renttek\WellKnown\Model\WellKnownProviderPool.
frontend/di.xml:
<?xml version="1.0"?> <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:ObjectManager/etc/config.xsd">rguments> </type> <type name="Renttek\WellKnown\Model\WellKnownProviderPool"> <arguments> <argument name="providers" xsi:type="array"> <item name="my_custom_provider" xsi:type="object" sortOrder="10">Vendor\Module\Model\CustomProvider</item> </argument> </arguments> </type> </config>