Download the PHP package dmfh/typo3-deployer without Composer
On this page you can find all versions of the php package dmfh/typo3-deployer. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download dmfh/typo3-deployer
More information about dmfh/typo3-deployer
Files in dmfh/typo3-deployer
Package typo3-deployer
Short Description Shared Deployer 7/8 recipe for deploying TYPO3 v12+ to shared hosting (Alfahosting, IONOS, 1blu, all-inkl, HostEurope, Strato, Mittwald). Hybrid directory strategy, rsync-based, per-provider profiles.
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 typo3-deployer
dmfh/typo3-deployer
Shared Deployer 7 recipe for deploying TYPO3 v12+ to shared hosting. One core, many hosters — the provider-specific quirks live in small profiles, everything project- and secret-specific stays in the consuming project.
Supported / planned provider profiles: Alfahosting, IONOS, 1blu, all-inkl, HostEurope, Strato, Mittwald.
Why
The deploy logic (hybrid TYPO3 directory strategy, rsync transfer, permissions, TYPO3 CLI steps, disk/file-count guards, server-side backup wiring) was written once and copy-pasted across ~8 projects, then drifted. This package is the single source of truth. Projects pin a version and update deliberately.
Design
- Core (
src/) — provider-agnostic config, tasks and deploy flow. No hostnames, paths or secrets. Ever. This repo is public. - Provider profiles (
src/provider/*.php) — pureset()calls for one hoster (SSH multiplexing, PHP binary, …). Declarative, no logic. - Per project (not in this repo) —
.hosts.yml(hosts, deploy paths, ssh users, TYPO3_CONTEXT) and secret files (.env,bin/.env). Both gitignored.
Install
Usage
Project deploy.php:
Project .hosts.yml (see .hosts.yml.example) — this file is gitignored
and never enters this package.
Deploy:
What the deploy does
- Disk-space + file-count preflight (shared-hosting guards).
- rsync the CI-built code (incl.
vendor/and built assets) to a new release. - Build the TYPO3 hybrid directory structure: real parent dirs, persistent
subdirs symlinked into
shared/, per-release cache dirs. - TYPO3 CLI: DB schema update, language update, cache warmup, reference index, scheduler run, backend lock/unlock around the switch.
- Stage-only: prepend an HTTP Basic-Auth block to
public/.htaccess. - Create/refresh the customer-account-level
backups/andbin/dirs and upload the server-side backup scripts fromserver-bin/. - Rotate logs, print a deployment summary.
Server-side backup scripts (server-bin/)
server-backup.sh (DB), server-backup-files.sh (files) and nas-pull.sh are
deployed to each server's bin/. They are parametrised entirely via CLI flags
(-o/-n/-f) and a per-server bin/.env — no credentials in this repo.
They are the counterpart to the local ~/typo3-backup orchestrator, which calls
them over SSH. Keep script names and flags stable so that contract holds.
Adding a provider
Create src/provider/<hoster>.php with the hoster's quirks only:
Keep it declarative. If a hoster needs conditional behaviour, prefer a setting the core already reads over branching logic in the profile.
