infomaniak-deployment

Deploy Astro sites to Infomaniak via rsync-over-SSH with Cloudflare-aware .htaccess.

3|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/Mikeys-Tech-Lab/poc --skill infomaniak-deployment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: infomaniak-deployment
Source: https://github.com/Mikeys-Tech-Lab/poc/tree/main/.cursor/skills/infomaniak-deployment
Command: npx skills add https://github.com/Mikeys-Tech-Lab/poc --skill infomaniak-deployment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the challenge of reliably deploying and securing a website to Infomaniak managed hosting using CI/CD, with environment-specific access controls and troubleshooting guidance.

Core Features & Use Cases

  • GitHub Actions rsync deployment: Builds (Astro), generates access restrictions, and deploys apps/site/dist/ via rsync over SSH with --delete for clean updates.
  • Cloudflare-aware IP restriction with a safe baseline: Blocks direct-to-origin bypass by enforcing use of Cloudflare’s CF-Connecting-IP header through generated .htaccess.
  • Environment strategy for Seed, Preview, and Public: Handles dev/preview access (IP allowlist vs Cloudflare Access/Zero Trust) and public deployment differences, plus required secrets/variables per GitHub environment.

Quick Start

Ask an AI to “Generate the Infomaniak CI/CD deployment plan for Seed, Preview, and Public, using rsync-over-SSH with Cloudflare-aware .htaccess, and list the exact GitHub secrets and variables I must configure to make the workflows run safely.”

Frequently Asked Questions about infomaniak-deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy to Infomaniak managed hosting using GitHub Actions and rsync?

You deploy to Infomaniak managed hosting using GitHub Actions by configuring an rsync-over-SSH workflow that builds your site, generates `.htaccess` access restrictions, and syncs the output directory with the `--delete` flag for clean updates.

What's the best way to prevent direct-to-origin bypass attacks when using Cloudflare with Infomaniak?

The best way to prevent direct-to-origin bypass attacks is enforcing Cloudflare's `CF-Connecting-IP` header through a generated `.htaccess` file, which blocks direct access to your Infomaniak hosting origin.

How does non-interactive SSH authentication work for Infomaniak CI/CD deployments?

Non-interactive SSH authentication for Infomaniak CI/CD deployments requires an ed25519 SSH key, stored as a GitHub secret, to establish secure automated connections without manual password input during the rsync process.

Can I use different access control strategies for dev, preview, and public environments?

You can use different access control strategies by configuring GitHub environments for Seed, Preview, and Public, applying IP allowlists for dev/preview access and public deployment settings for the public environment.

Why does my rsync deployment to Infomaniak fail during the GitHub Actions workflow?

Your rsync deployment to Infomaniak may fail due to incorrect ed25519 SSH key configuration, missing GitHub environment secrets, or improper handling of hosting proxy constraints and Cloudflare header behavior.