The `fis3-deploy-http-push` package serves as the default deployment plugin for the FIS3 build system, offering functionalities for both local and remote file synchronization via HTTP POST requests. Currently at version 2.0.8, it enables developers to configure custom deployment targets and attach specific data parameters for different file types directly within their FIS3 build configurations. A key characteristic is its deep integration with the FIS3 framework, allowing for sophisticated, programmatic control over the deployment process, including the ability to incorporate interactive elements like token prompts for authentication during a build. However, it is critical to note the explicit and severe security warnings associated with the provided `receiver.php` example script, which is inherently insecure and **must not be deployed in production environments**. This limitation means the plugin is primarily suitable for internal development, staging, or highly trusted network setups. The package's release cadence is not independent but rather follows the lifecycle and maintenance schedule of the broader FIS3 project.
npm install fis3-deploy-http-pushVerified import paths — ran on the pinned version, not inferred.
Demonstrates how to configure the `http-push` plugin within a FIS3 project to deploy JavaScript files to a remote HTTP receiver endpoint with custom parameters.
DO NOT use the example `receiver.php` script in production. Implement a custom, secure backend receiver that includes robust authentication, authorization, and input validation, or utilize a different, secure deployment mechanism for production assets.
Ensure you are using `fis3` as your project's build tool. If you require a standalone HTTP deployment solution, consider alternative packages not specific to FIS3.
Before deploying, ensure your target server is running and configured with a custom, secure receiver script or API endpoint that can process the uploaded files sent by this plugin.
Develop a custom, secure receiver application with proper authentication, authorization, and input sanitization, or choose an alternative, secure deployment method for production.
Verify the `receiver` URL is correct and accessible. Ensure the remote server is online and the receiver script (your custom one, not the insecure example) is correctly deployed and functioning.
Double-check the `to` option in your `fis.plugin('http-push', { to: '...' })` configuration. Also, verify that your custom receiver script correctly reads and utilizes the `to` parameter to determine the target path on the server.No dependency data recorded yet.