Deploy Rails Frontend Client FAQs

Question 1

How does this skill improve my Claude Code workflow?

Accepted Answer

It eliminates manual configuration errors by providing Claude with a standardized deployment path. It includes automated shell script execution, build validation, and post-deployment health checks to ensure your frontend and legacy backend are perfectly synced.

Question 2

What does the Deploy Rails Frontend Client skill do?

Accepted Answer

This skill automates the deployment of a Next.js frontend (specifically the shot-client-next app) to Fly.io, pre-configured to communicate with a legacy Ruby on Rails backend. It handles environment variables, build checks, and deployment workflows automatically.

Question 3

How does this skill handle WebSocket connections?

Accepted Answer

The skill automatically configures the environment to use ActionCable WebSockets. It sets the necessary build arguments to point to the wss://shot-counter.fly.dev/cable endpoint, ensuring real-time features work out-of-the-box.

Question 4

When should I use this skill instead of the Phoenix version?

Accepted Answer

You should use this skill only when you specifically need to connect to the legacy Rails backend at shot-counter.fly.dev. For standard production or Elixir-based environments, use the 'deploy-phoenix-client' skill instead.

Question 5

What technical requirements are needed to use this skill?

Accepted Answer

You need the Fly.io CLI installed and authenticated. The skill is designed to work within the shot-client-next directory and requires access to the fly.toml configuration file for the legacy Rails environment.

Deploy Rails Frontend Client

Deploy Rails Frontend Client

概要

主な機能

ユースケース

概要

主な機能

ユースケース