Search

Items tagged with: GitHubActions

New GitHub Action: FTP Hash Deploy.

Deploy only changed files via FTP/FTPS — no state file, no timestamp guesswork. It uses server-side Git blob hashing: the server tells you exactly what it has, you upload only what's actually different.

- No state file to go stale or corrupt
- Works on any PHP-capable host (Strato, All-Inkl, Ionos, cPanel, Plesk...)
- dry-run mode to preview the diff safely

github.com/Agundur-KDE/ftp-has…

#GitHubActions #CICD #DevOps #PHP #WebDev #OpenSource

GitHub - Agundur-KDE/ftp-hash-deploy-action: FTP Deploy Action with server-side Git-style hashing — uploads only changed files, no state file, no guesswork.

FTP Deploy Action with server-side Git-style hashing — uploads only changed files, no state file, no guesswork. - Agundur-KDE/ftp-hash-deploy-action
GitHub
#opensource #devops #php #cicd #webdev #GitHubActions

CI/CD pipelines are a prime target for supply chain attacks. We hardened the GitHub Actions workflows for Composer, Packagist and Private Packagist with zizmor, a static analysis tool for GitHub Actions. 🌈

Our new blog post covers what zizmor catches, our configuration, and the pitfalls we hit along the way:
blog.packagist.com/securing-ou…

#php #phpc #composerphp #github #githubactions #supplychainsecurity

Securing our GitHub Actions workflows with zizmor

This is the next post in our supply chain security series, following the supply chain security update, the Composer 2.10 release and immutable version metadata on Packagist.org. The earlier posts covered Composer behavior, changes to Packagist.
Steven Rombauts (Private Packagist)
#github #php #phpc #supplychainsecurity #GitHubActions #composerphp

Do not use pull_request_target.
Do not use caches in publish workflows.
Use dependency cooldowns.
Use Zizmor.
Tell GitHub to make Actions secure by default.
#GitHub #GitHubActions
#github #GitHubActions

Diese Webseite verwendet Cookies. Durch die weitere Benutzung der Webseite stimmst du dieser Verwendung zu. https://inne.city/tos

⇧