Download the PHP package dof-dss/maestro-hosting without Composer
On this page you can find all versions of the php package dof-dss/maestro-hosting. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 maestro-hosting
Maestro Hosting
Hosting providers and assets for Maestro.
Directory structure
Updating hosting configuration
Under resources/
- Files are copied across during the build without needing alteration.
- Templates are files that are modified during the build process before added to the project.
Changes to content in the files directory can be added and published as a new release.
If you require changes to a template you should make your changes but also look at the
hosting provider class to check the alterations made to the file.
Updating hosting build steps
If you need to alter how a hosting provider constructs the overall hosting setup you will need to change the steps in the build function of the provider class.
Adding a new hosting provider
To add a new hosting provider create a new class that inherits the Hosting base class.
Add the various setup steps to the build function and add any resources to
resources/
Injected services
Each providers build method is injected with 3 services:
- StyleInterface $io,
- FilesystemInterface $fs,
- ProjectInterface $project
StyleInterface
The styleinterface provides method to communicate user messages to the Maestro shell.
See: https://github.com/symfony/console/blob/4.2/Style/StyleInterface.php for details.
FilesystemInterface
The FilesystemInterface provides methods to interact with the filesystem IO and mirrors the functionality of the Symfony Filesystem class but provides the following additional features:
- Paths starting with a forward slash will be relative to the current directory.
- Paths starting with a double forward slash will be treated as absolute paths.
- The Read method will automatically parse the given filepath based on the file extension.
- The Write method will automatically compile the content parameter to the correct format based on file extension.
See: https://github.com/dof-dss/maestro-core/blob/main/src/FilesystemInterface.php
ProjectInterface
The projectInterface provides methods to manage the Maestro project.
You will usually call and iterate over the sites() method from within your build()
function to setup the hosting environment for each site.
See https://github.com/symfony/console/blob/4.2/Style/StyleInterface.php for details.
Enabling a hosting provider
Each forked project repository must contain a maestro.yml file with the required hosting provider
entries. When the maestro shell project:build command runs, it will iterate each of these providers
and run their build method.
Entries must have a service name (which isn't strict), the FQN of the provider class and a tag of 'maestro.hosting'.
See the example below.
