Desplegar sitios web y apps web de Google AI Studio

Conectar Google AI Studio con GitHub

Abre el sitio web o la app web que ya creaste.

Abrir Google AI Studio

https://aistudio.google.com

Your app in Google AI Studio Settings GitHub

¿Primera vez? Pulsa "Sign in to GitHub to continue" Pulsa "Install & Authorize" cuando se te pida

Settings es el icono del engranaje en la esquina superior derecha. ¿Ya estás conectado a GitHub? Pasa a la siguiente tarea.

Crear una cuenta de GitHub

Only if you don't have one yet.

https://github.com/signup

Crear un repositorio y guardar

Un repositorio es la carpeta de tu proyecto en GitHub. Hostinger lee tu proyecto desde ahí.

Pulsa "Create new repository" Escribe un nombre para el repositorio. La descripción es opcional Elige Private Pulsa "Create GitHub repository" Pulsa "Push changes to GitHub" Espera hasta que el estado diga "GitHub & Google AI Studio are currently in sync"

Ese mensaje confirma que tu proyecto está guardado.

Consigue hosting en Hostinger

Necesitas un plan de Hostinger que incluya Web Apps. ¿Ya tienes uno? Abre tu cuenta y pasa al siguiente paso.

Consigue hosting de Web Apps en Hostinger

Elige un plan que incluya Web Apps de Node.js.

USED IN TUTORIAL

Crear una Web App e importar tu proyecto

Hostinger Websites Create website Web App

Elige tu dominio, o un dominio temporal para empezar Elige Import your Git repository Elige Continue with GitHub y autoriza a Hostinger si te lo pide Selecciona el repositorio que guardaste en el paso 1

Puede que Hostinger te muestre esto como preguntas de su asistente en lugar de un formulario. Las opciones son las mismas.

Revisar la configuración del build

Hostinger detecta automáticamente la configuración del build de tu proyecto. Comprueba el framework seleccionado y continúa si todo está correcto.

¿No estás seguro de la configuración del build?

Opcional. Pega esto en tu proyecto de Google AI Studio y compara su respuesta con lo que seleccionó Hostinger. Solo lee tus archivos.

Check this project's deployment settings for Hostinger. This is a read-only check. I am deploying this project to Hostinger as a Web App, imported from GitHub. Hostinger has already suggested build settings, and I want to confirm them against the real project. Inspect the actual project files: package.json, the lockfile, the build configuration and any server file. Do not guess from the preview or from how the app looks. Rules: - Do NOT change, create or delete any file. - Do NOT print the value of any API key or secret. Keep two things separate: - FRONTEND TOOLING: what builds the pages, for example Vite. - SERVER RUNTIME: whether a Node.js server must keep running in production, for example an Express server that serves the app or calls an API. If the project has a Node.js server that must keep running, the Hostinger framework preset should match that server, even when the pages are built with Vite. If there is no server, the preset should match the frontend build tool. Reply in this short format, as plain text and not JSON: Framework preset to choose in Hostinger: Needs a running Node.js backend: Yes or No, with a one-line reason Root directory: only if the app is not at the repository root Package manager: Build command: or "none needed" Server entry file: or "none" Node.js version: only if the project states one, otherwise "not specified" Mismatch to fix: anything that would break on Hostinger, or "none found" If you cannot verify a line from the files, write "not sure" instead of guessing.

Añadir tus variables de entorno

¿No aparece ninguna variable? Omite este paso.

Revisa las variables de entorno que detectó Hostinger Introduce los valores que necesita tu proyecto Pulsa Continue

Los secretos que guardaste en Google AI Studio no se copian a Hostinger, así que vuelve a introducirlos aquí. Si tu proyecto usa la Gemini API, crea una clave en esta página:

Abrir Google AI Studio

API keys page

https://aistudio.google.com/apikey

IMPORTANTE

Introduce las claves de API solo en Hostinger. Nunca pongas una clave privada en una variable que empiece por VITE_, y nunca subas a GitHub un archivo .env con claves reales.

¿No sabes qué variables necesita tu proyecto?

Encontrar las variables que necesita mi proyecto

Pega esto en tu proyecto de Google AI Studio. Lista los nombres de variables que tu código lee de verdad y no cambia nada.

List the environment variables this project needs on Hostinger. This is a read-only check. Search the real source code for process.env and import.meta.env, and read any example environment file. Do not guess and do not invent names. Rules: - Do NOT change, create or delete any file. - Report variable NAMES only. Never print a value. - Do not suggest several names for the same key. Report the one name the code reads. For each variable, give one line: NAME, what it is for, Required or Optional, read on the SERVER or in BROWSER code Do not list variables the hosting platform normally sets by itself, such as NODE_ENV or PORT, unless the code cannot work without a value I must enter. Then add one last line: Private key exposed in browser code: Yes or No Answer Yes if a private key, such as a Gemini API key, is read through a VITE_ variable or otherwise ends up in code that runs in the browser.

Sacar una clave privada del código del navegador

Úsalo solo si la comprobación anterior dice que una clave privada está expuesta en el código del navegador. Las variables que empiezan por VITE_ se incluyen en páginas que cualquiera puede leer.

A private API key in this project is read in browser code. Move it to the server so visitors can never see it. First confirm it from the real files: show me the file and line where browser code reads the key, without printing the key's value. If you cannot find one, stop and tell me. Do not change anything. If it is confirmed, make the smallest change that fixes it, and keep the design and every feature exactly as they are: - Call the API from a server route. Use the Node.js server the project already has. Add a minimal one only if there is none. - Read the key on the server from an environment variable that does NOT start with VITE_. - Make the browser code call my own server route instead of the API directly. - Remove the key from every file that is sent to the browser. Rules: - Never print the key's value. - Do not add a .env file with real keys to the repository. - Do not change unrelated code. When you finish, tell me: - the files you changed - the exact variable name to add in Hostinger - whether the project now needs a running Node.js server, so I can check the framework Hostinger selected

Desplegar

Revisa la configuración final Pulsa Deploy Espera a que termine el build Abre el sitio web en producción

Si el build falla

Copia el error que muestra Hostinger, pégalo en este prompt y ejecútalo en tu proyecto de Google AI Studio. Después guarda la corrección en GitHub, o cambia el ajuste en Hostinger y vuelve a desplegar.

Corregir un despliegue fallido

Encuentra la causa real a partir de tu error y corrige solo eso.

My project failed to deploy on Hostinger. I deployed it as a Web App imported from GitHub. Here is the exact error from Hostinger's build log: [PASTE THE ERROR HERE] Here is what Hostinger selected: Framework: [PASTE IT HERE] Other build settings, if you can see them: [PASTE THEM HERE, OR DELETE THIS LINE] Find the real cause from this error and the actual project files: package.json, the build configuration and any server file. Do not try random changes, and do not invent a cause the error and the files do not support. If the error is not enough to be sure, tell me what else to copy from Hostinger. - If a Hostinger setting is wrong, tell me exactly which setting to change and to what. Do not change code for that. - If the code or configuration is wrong, fix only that. Keep the design and features the same. - Do not upgrade unrelated packages. - If the log contains a key or password, do not repeat it. Never print the value of an API key or secret. Reply with: Cause: What you changed, or which Hostinger setting to change: What I should do next:

Probar el sitio web en producción

Abre tu sitio web en producción y comprueba que sus páginas y funciones principales funcionan.

Si tu proyecto tiene funciones de IA, inicio de sesión o servicios conectados, pruébalos también.

Si algo no funciona en el sitio web en producción

Copia el prompt que corresponda a tu problema y ejecútalo en tu proyecto de Google AI Studio. Después guarda la corrección en GitHub.

Corregir una página vacía o en blanco

El build terminó, pero el sitio web en producción muestra una página vacía.

My project deployed to Hostinger without a build error, but the live website shows a blank page. It works in the Google AI Studio preview. Find what is different in production. Check the real project files for: - errors that only happen in the production build - asset and script paths that break outside the preview, including the base path in the build configuration - a server that does not serve the built files, or serves them from the wrong folder - a server that listens on a fixed port instead of the port the hosting gives it - code that needs an environment variable which is missing in production If I paste errors from the browser console below, start from them: [PASTE ANY BROWSER CONSOLE ERRORS HERE, OR DELETE THIS LINE] Base the fix on what you find in the files and the errors, not on guesses. If you cannot tell the cause, say what else I should copy for you. Keep the design and features exactly the same, and never print the value of an API key or secret. Reply with: Cause: What you changed, or which Hostinger setting to change: What I should do next:

Corregir una función de IA, el inicio de sesión u otra función

El sitio web carga, pero una función no funciona.

My project is live on Hostinger and the pages load, but this feature does not work: [DESCRIBE THE FEATURE AND WHAT HAPPENS] Any error message I can see: [PASTE IT HERE, OR DELETE THIS LINE] It works in the Google AI Studio preview. Find why it fails in production. Check the real project files for: - the environment variables this feature reads. List their NAMES so I can confirm each one has a value in Hostinger - code that depends on Google AI Studio's own environment or secrets and has no equivalent on Hostinger - API calls that need a running Node.js server, in case the project was deployed without one - addresses that point to the preview or to localhost instead of the live domain - for sign-in or outside services: settings that must list my live domain Never ask me for the value of an API key or secret, and never print one. Never move a private key into browser code or into a VITE_ variable to make the feature work. Do not invent a cause the files and the error do not support. Keep the design and other features the same. Reply with: Cause: What you changed, or what I must set in Hostinger or in the outside service: What I should do next:

Corregir un 404 en una página interna

La página de inicio funciona, pero al abrir o recargar otra página aparece un 404.

My project is live on Hostinger. The home page works, but opening or refreshing an inner page shows a 404 page. Inspect how this project handles routes: the router in the frontend, and the server file if there is one. - If the project runs its own Node.js server, make that server return the app's main page for routes the frontend router handles, without breaking API routes or static files. - If the project has no server, do not add one. Tell me what the hosting must do for these routes and which Hostinger setting to check. Change only what this problem needs. Keep the design and features the same. Reply with: Cause: What you changed, or which Hostinger setting to change: What I should do next:

Actualizar tu sitio web

Cada actualización sigue el mismo camino: Google AI Studio → GitHub → Hostinger → Sitio web en producción.

Haz un pequeño cambio en Google AI Studio Abre Settings y luego GitHub Pulsa "Push changes to GitHub" Espera hasta que el proyecto esté sincronizado Espera a que Hostinger despliegue la actualización Recarga tu sitio web en producción y comprueba el cambio

Hostinger despliega la actualización por sí solo mientras tu repositorio de GitHub siga conectado y el despliegue automático esté activado para tu Web App.