Download the PHP package symplify/monorepo-builder without Composer
On this page you can find all versions of the php package symplify/monorepo-builder. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download symplify/monorepo-builder
More information about symplify/monorepo-builder
Files in symplify/monorepo-builder
Package monorepo-builder
Short Description Prefixed version of Not only Composer tools to build a Monorepo.
License MIT
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 monorepo-builder
Not only Composer tools to build a Monorepo
Do you maintain a monorepo with more packages?
This package has few useful tools, that will make that easier.
Install
Usage
1. Are you New to Monorepo?
The best to lean-in fast is to read basic intro at blog post All You Always Wanted to Know About Monorepo. We also made a simple command to make that easy for you:
And the basic setup is done!
2. Merge local composer.json to the Root One
Merges configured sections to the root composer.json, so you can only edit composer.json of particular packages and let script to synchronize it.
Sections that are needed for monorepo to work will be merged:
- 'require'
- 'require-dev'
- 'autoload'
- 'autoload-dev'
- 'repositories'
- 'extra'
To merge run:
Typical location for packages is /packages. But what if you have different naming or extra /projects directory?
3. Bump Package Inter-dependencies
Let's say you release symplify/symplify 4.0 and you need package to depend on version ^4.0 for each other:
4. Keep Synchronized Package Version
In synchronized monorepo, it's common to use same package version to prevent bugs and WTFs. So if one of your package uses symfony/console 3.4 and the other symfony/console 4.1, this will tell you:
5. Keep Package Alias Up-To-Date
You can see this even if there is already version 3.0 out:
Not good. Get rid of this manual work and add this command to your release workflow:
This will add alias 3.1-dev to composer.json in each package.
If you prefer 3.1.x-dev over default 3.1-dev, you can configure it:
6. Split Directories to Git Repositories
Thanks to GitHub Actions, this was never simpler to set up. Use symplify/github-action-monorepo-split.
How to configure it? See our local setup at .github/workflows/split_monorepo.yaml
7. Release Flow
When a new version of your package is released, you have to do many manual steps:
- bump mutual dependencies,
- tag this version,
git pushwith tag,- change
CHANGELOG.mdtitle Unreleased tov<version> - Y-m-dformat - bump alias and mutual dependencies to next version alias
But what if you forget one or do it in wrong order? Everything will crash!
The release command will make you safe:
And add the following release workers to your monorepo-builder.php:
These TagVersionReleaseWorker and PushTagReleaseWorker are enabled by default.
If you want to disable these default workers, you can use the following code.
You can also include your own workers. Just add services that implements ReleaseWorkerInterface.
Are you afraid to tag and push? Use --dry-run to see only descriptions:
Do you want to release next patch version, e.g. current v0.7.1 → next v0.7.2?
You can use minor and major too.
