Download the PHP package logifire/ftps-deploy without Composer
On this page you can find all versions of the php package logifire/ftps-deploy. 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 ftps-deploy
FTPS Deploy
A simple PHP deployment tool that uses FTPS to upload changed files to a remote server. It tracks file changes using MD5 hashes and only uploads modified files.
Features
- FTPS secure file transfer
- Tracks file changes using MD5 hashes
- Only uploads modified files
- Supports file/directory ignore patterns
- Creates remote directories automatically
- Passive mode FTP support
Installation
Install via Composer:
Configuration
You can initialize a template configuration file by running:
This will create a deploy-config.php file in your project root which you can then edit with your FTPS credentials.
Otherwise, create a deploy-config.php file manually in your project root:
Custom Configuration File Location
By default, FTPS deploy looks for deploy-config.php in the current working directory. If you want to use a configuration file located elsewhere, you can specify its path using the --config option:
This allows you to keep multiple configuration files for different environments or projects, and select which one to use at deploy time.
Usage
Run deployment using:
To only generate or update the hash file (without uploading or deleting any files), use the --only-hashes option:
You can also specify a custom config file location with the --config argument:
To see available options, run:
Composer Script (Optional)
If you are using Composer, you can add a convenient script to your composer.json:
This allows you to run deployment with:
Or, to deploy with a custom config file (e.g., for staging):
Deployment Hashes File (deploy-hashes.json)
FTPS Deploy keeps track of file changes using a JSON file (by default named .deploy-hashes.json) in your project directory. This file stores hashes of previously deployed files to determine which files have changed and need to be uploaded or deleted.
- Default location:
.deploy-hashes.jsonin your project root. - Custom location: The
hash_fileentry is present by default in yourdeploy-config.phpfile. You can change its value to specify a different path:
This is useful if you want to:
- Store deployment state outside your project directory (e.g., in CI/CD pipelines like GitHub Actions)
- Use different hash files for different environments
- Avoid committing the hash file to version control
Options
| Option | Description |
|---|---|
init |
Create a template deploy-config.php in the current directory. |
--config=PATH |
Use a custom config file instead of ./deploy-config.php. |
--only-hashes |
Only generate/update the hash file, do not upload or delete files. |
--help |
Show help message. |
If you change the location, make sure the path is writable by the deployment process.
Requirements
- PHP 8.0 or higher
- PHP FTP extension
- FTPS-enabled hosting
License
This project is licensed under the GNU General Public License v3.0 - see the LICENSE file for details.
Disclaimer: While FTPS Deploy automates the deployment process, it is the user's responsibility to verify that all files are correctly synchronized and that the deployment meets the intended requirements. Always review your deployment results and test your application after deploying.
Note: This library, including its code, documentation, and this README, was generated with the assistance of AI.
All versions of ftps-deploy with dependencies
ext-ftp Version *