AI App Hosting 1.3.0-1

Added guided help to connect a Git repository over SSH When you enter an SSH-style Git URL for a deploy, or when a deploy fails because SSH access isn’t set up, the system now shows the steps to connect. Create or choose an SSH key, grant that key access to the repository on the hosting service, and recheck the connection. The steps link directly to SSH key management, and name service-specific instructions for hosting services that the system recognizes. For more information on managing SSH keys, read our Managing SSH Keys and API Tokens documentation. Git-source deploys also now support SSH keys that require a passphrase. You can supply a one-time passphrase when you deploy or redeploy an application; the system uses it only for that operation and does not store it. When a git clone operation fails, the system now reports the specific reason, such as missing SSH access, an untrusted host key, required HTTPS credentials, or a missing or incorrect key passphrase. Detect a Node.js build output directory The system now detects a Node.js application’s build output directory from the build tool and directory that the build script names. It asks you for the directory when it cannot detect one. A deploy that builds successfully but produces nothing to serve now fails and names the missing directory, instead of returning a 404 error. Serve an application at a domain you already use You can now serve an application at a domain that your account already uses. The system asks you to confirm this, and keeps the domain when you delete the application. For more information on how a domain switches between serving files and serving an application, read our How Domains Serve Content documentation. Store application environment variables in a .env file The system now stores an application’s environment variables in the application’s own .env file, rather than in the container configuration where other users could read them. You can paste an entire .env file. Variable names must begin with a letter or an underscore, values must be a single printable line, and you cannot set the PORT variable. You cannot set variables when Git tracks the application’s .env file. Added CageFS and non-EA4 package support You can now serve a web application to a CageFS account on CloudLinux®. The system also supports non-EA4 packages that require EA4 packages. For more information on AI App Hosting plugin releases, read our AI App Hosting Release Notes documentation.