Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/extdn/extension-dashboard-m2
A Magento 2 dashboard to display installed extensions. Read the blog post on some of the thinking behind it:
https://github.com/extdn/extension-dashboard-m2
Last synced: 12 days ago
JSON representation
A Magento 2 dashboard to display installed extensions. Read the blog post on some of the thinking behind it:
- Host: GitHub
- URL: https://github.com/extdn/extension-dashboard-m2
- Owner: extdn
- Created: 2019-02-21T01:54:53.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2022-03-23T10:19:03.000Z (over 2 years ago)
- Last Synced: 2024-08-02T05:19:25.390Z (3 months ago)
- Language: PHP
- Homepage: https://store.fooman.co.nz/blog/mlau-2019-devexchange-extension-and-security-recap.html
- Size: 298 KB
- Stars: 38
- Watchers: 7
- Forks: 6
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Extension Dashboard for Magento 2
This module adds a dashboard to review all installed extensions in the Magento admin (Magento 2.3.0+ for now only).
## Screenshots
![Screenshot Dashboard](docs/extension_dashboard.png?raw=true")
## Installation
We strongly recommend to always make changes to a Magento 2 site through a development environment that runs in the Developer Mode:
```bash
bin/magento deploy:mode:set developer
```
Add this Git repository to composer and then install the composer package:
```bash
composer config repositories.extdndash git https://github.com/extdn/extension-dashboard-m2.git
composer require extdn/extension-dashboard-m2:dev-master
```
Next, enable the module:
```bash
bin/magento module:enable Extdn_ExtensionDashboard
bin/magento setup:upgrade
```
Next, follow the usual procedure to push changes from the development environment to production (for example with `bin/magento deploy:mode:set production`).
## Extension feeds
This dashboard is being fed through feeds: Either a CSV-file or a remote resource that allows you to define version-information. Currently, the following is supported:
- Define a new DI VirtualType (see `di.xml`) to use the `ComposerFeedProvider` to load information from Packagist.
- Use the `CsvFeedProvider` to load information from a local CSV file.
- Add a custom provider to the listing of providers.
## Todo
- Move extension feeds to different submodules?
- Automatically fetch information from Packagist on existing extensions, if available.