Deploy Situs & Aplikasi Web Google AI Studio

Hubungkan Google AI Studio ke GitHub

Buka website atau aplikasi web yang sudah Anda buat.

Buka Google AI Studio

https://aistudio.google.com

Your app in Google AI Studio Settings GitHub

Pertama kali? Klik "Sign in to GitHub to continue" Klik "Install & Authorize" saat diminta

Settings adalah ikon roda gigi di pojok kanan atas. Sudah terhubung ke GitHub? Lanjut ke tugas berikutnya.

Buat Akun GitHub

Only if you don't have one yet.

https://github.com/signup

Buat Repository dan Simpan

Repository adalah folder proyek Anda di GitHub. Hostinger membaca proyek Anda dari sana.

Klik "Create new repository" Masukkan nama repository. Deskripsi bersifat opsional Pilih Private Klik "Create GitHub repository" Klik "Push changes to GitHub" Tunggu hingga status menampilkan "GitHub & Google AI Studio are currently in sync"

Pesan itu menandakan proyek Anda sudah tersimpan.

Dapatkan Hosting Hostinger

Anda memerlukan paket Hostinger yang mencakup Web App. Sudah punya? Buka akun Anda dan lanjut ke langkah berikutnya.

Dapatkan Hosting Web App Hostinger

Pilih paket yang mencakup Node.js Web App.

USED IN TUTORIAL

Buat Web App dan Impor Proyek Anda

Hostinger Websites Create website Web App

Pilih domain Anda, atau domain sementara untuk memulai Pilih Import your Git repository Lanjutkan dengan Continue with GitHub dan beri izin kepada Hostinger jika diminta Pilih repository yang Anda simpan di Langkah 1

Hostinger mungkin menampilkannya sebagai pertanyaan dari asistennya, bukan sebagai formulir. Pilihannya sama.

Tinjau Pengaturan Build

Hostinger otomatis mendeteksi pengaturan build proyek Anda. Periksa framework yang dipilih, lalu lanjutkan jika semuanya sudah benar.

Ragu dengan Pengaturan Build Anda?

Opsional. Tempel ini ke proyek Google AI Studio Anda dan bandingkan jawabannya dengan pilihan Hostinger. Prompt ini hanya membaca file Anda.

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.

Tambahkan Variabel Environment Anda

Tidak ada variabel yang tercantum? Lewati langkah ini.

Tinjau variabel environment yang dideteksi Hostinger Masukkan nilai yang dibutuhkan proyek Anda Klik Continue

Secret yang Anda simpan di Google AI Studio tidak disalin ke Hostinger, jadi masukkan lagi di sini. Jika proyek Anda memakai Gemini API, buat kunci di halaman ini:

Buka Google AI Studio

API keys page

https://aistudio.google.com/apikey

PENTING

Masukkan kunci API hanya di Hostinger. Jangan pernah menaruh kunci privat di variabel yang diawali VITE_, dan jangan pernah mengunggah file .env berisi kunci asli ke GitHub.

Tidak yakin variabel apa yang dibutuhkan proyek Anda?

Temukan Variabel yang Dibutuhkan Proyek Saya

Tempel ini ke proyek Google AI Studio Anda. Prompt ini mencantumkan nama variabel yang benar-benar dibaca kode Anda dan tidak mengubah apa pun.

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.

Pindahkan Kunci Privat dari Kode Browser

Gunakan ini hanya jika pemeriksaan di atas menyatakan ada kunci privat yang terekspos di kode browser. Variabel yang diawali VITE_ dimasukkan ke halaman yang bisa dibaca siapa saja.

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

Jalankan Deploy

Tinjau konfigurasi akhir Klik Deploy Tunggu hingga build selesai Buka website live

Jika build gagal

Salin error yang ditampilkan Hostinger, tempel ke prompt ini, lalu jalankan di proyek Google AI Studio Anda. Setelah itu simpan perbaikannya ke GitHub, atau ubah pengaturan di Hostinger dan deploy ulang.

Perbaiki Deployment yang Gagal

Menemukan penyebab sebenarnya dari error Anda dan hanya memperbaiki itu.

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:

Uji Website Live

Buka website live Anda dan pastikan halaman serta fitur utamanya berfungsi.

Jika proyek Anda punya fitur AI, login, atau layanan yang terhubung, coba juga fitur-fitur itu.

Jika ada yang tidak berfungsi di website live

Salin prompt yang sesuai dengan masalah Anda dan jalankan di proyek Google AI Studio Anda. Setelah itu simpan perbaikannya ke GitHub.

Perbaiki Halaman Kosong atau Putih

Build selesai, tetapi website live menampilkan halaman kosong.

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:

Perbaiki Fitur AI, Login, atau Fitur Lain

Website bisa dimuat, tetapi ada fitur yang tidak berfungsi.

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:

Perbaiki 404 di Halaman Dalam

Halaman utama berfungsi, tetapi membuka atau me-refresh halaman lain menampilkan 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:

Perbarui Website Anda

Setiap pembaruan mengikuti jalur yang sama: Google AI Studio → GitHub → Hostinger → Website Live.

Buat perubahan kecil di Google AI Studio Buka Settings, lalu GitHub Klik "Push changes to GitHub" Tunggu hingga proyek tersinkron Tunggu Hostinger men-deploy pembaruan Refresh website live Anda dan periksa perubahannya

Hostinger men-deploy pembaruan dengan sendirinya selama repository GitHub Anda tetap terhubung dan deployment otomatis aktif untuk Web App Anda.