WordPress Packagist
Repman
| WordPress Packagist | Repman | |
|---|---|---|
| 7 | 5 | |
| 691 | 502 | |
| 0.4% | 1.6% | |
| 6.8 | 4.7 | |
| about 2 months ago | about 2 months ago | |
| PHP | PHP | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
WordPress Packagist
-
How do you create WordPress websites for your clients?
If I have to use WordPress for something, I'll build it as a standard PHP project, requiring WordPress and any themes/plugins as a Composer dependencies from johnpbloch/wordpress and WordPress Packagist (more info here). If I need to do any significant templating, I like to use Timber.
- Fullstack but new to WP - Searching for answers
-
Is there a package.json equivalent but for plugins?
Use it together with https://wpackagist.org/ and you can update all plugins/themes by latest or by version number.
-
How to use Git for Wordpress sites?
Another option you can look at is Bedrock by Roots - that is sets WP as an app with composer already set up. It allows you to install WP plugins (from official WP repo) via composer (WP Packagist). The structure is set up to allow for git workflow. Also helpful if you want to make use of a bunch of composer packages on your site.
-
Looking for advice: installing plugin from GitHub on many sites for upgrade
https://wpackagist.org/ in the example you see "repositories", now in that array you can put your plugins github-link and set the other settings. with composer install you install them and with composer update you update them
- Backdoor in several WP Themes and Plugins from AccessPress
-
How should I update plugins in a Git-based workflow with Staging and Production environments?
Side question: I know that the WordPress ecosystem has been moving toward better support for Composer – e.g., with WPackagist. But wouldn't plugins installed/updated via Composer run into the same issue?
Repman
-
Anyone tried setting up Repman on AWS?
500 error when you first bring it up. Solved by running `chown www-data:www-data -R /app/var/log` (credit: https://github.com/repman-io/repman/issues/582). ...This might be solved in newer images, but we didn't catch that the docker-compose was behind until after we'd resolved this.
-
Private or self hosted registry options for composer/php dependencies
https://repman.io/ its free, used satis before but this is better imo
-
Is using VCS instead of Private Packagist a viable solution?
Both Repman and Private Packagist are hosted and self-hosted. Who maintains it does not really matter. But if you want to maken an argument between the two, Repman is open source on GitHub! https://github.com/repman-io/repman
What are some alternatives?
Packagist - Package Repository Website - try https://packagist.com if you need your own -
Satis - Simple static Composer repository generator - For a full private Composer repo use Private Packagist
Phpactor - Mainly a PHP Language Server with more features than you can shake a stick at
Composition - Check your Composer dependencies at runtime.
Spout - Read and write spreadsheet files (CSV, XLSX and ODS), in a fast and scalable way
composer-patches - Simple patches plugin for Composer
Laminas API Tool Skeleton - Skeleton Application for Laminas API Tools
ComposerRequireChecker - A CLI tool to check whether a specific composer package uses imported symbols that aren't part of its direct composer dependencies
Rector - Instant Upgrades and Automated Refactoring of any PHP 5.3+ code
composer-diff - Compares composer.lock changes and generates Markdown report so you can use it in PR description.
Firegento - Extends the customer functionality of Magento.
laravel-task - A simple way to trigger tasks in a clean and simple way