Use this when you install the Magic Meal Kits server into your own Google Cloud project for the first time, or redeploy it to the latest version. Walks through the 4-step install wizard of the v2 dashboard.
This guide follows the new dashboard (v2), which opens at
make.magicmealkits.com/v2/deploy. If you are on the
previous screen at make.magicmealkits.com/deploy, the
buttons sit in slightly different places but the order is the same. The dashboard UI is in Korean,
so each step gives the English meaning with the Korean label in parentheses.
You install Magic Meal Kits from the web app at
make.magicmealkits.com. The install wizard deploys the Magic Meal
Kits server into your own Google Cloud project. You own the server, the data, and the URL.
Install with a regular Gmail account, not a Google Workspace account. The install wizard only
supports the Google Cloud environment of a regular Gmail account. Your Make account and the other
accounts you connect from Make can be Workspace accounts.
The wizard has 4 steps, shown in the progress bar at the top: Account (계정), Project and
plan (프로젝트·요금제), Deploy (배포), and Done (완료). The previous screen had 5 steps;
plan selection moved into the project step, and there is a new deploy confirmation dialog.
1
Sign in
At make.magicmealkits.com, click Sign in with Google and pick
the Gmail account you bought the plan with. The sign-in screen is still in English.
Zoomed in
Example screen. The real screen shows Magic Meal Kits here.
Zoomed in
If you sign in with an account that has no purchase, no plan shows up and you get
Upgrade plan (요금제 업그레이드) instead of the install button. Sign out and sign back in
with the account you bought the plan with.
2
Account: connect Google Cloud
Open Deploy app (앱 배포) in the left menu. On your first visit a guide video pops up. You can
close it; to see it again, click View guide (가이드 보기) at the top right. Click
Connect with Google (Google로 연결).
Zoomed in
On the Google permission screen, pick the same account you signed in with and click
Allow. If you allow only some of the permissions, the project list won’t load or the
deployment fails.
Example screen. The real screen shows Magic Meal Kits here.
Zoomed in
Tick the box next to the permission before you click Continue.
3
Account: check the connection
Check the connected email and the app (Basic or Pro), then click Continue (계속).
Zoomed in
4
Project and plan: pick a project
Under GCP project (GCP 프로젝트), pick the project to install into. If you don’t have one, click
Create new project (새 프로젝트 만들기); the name must be 6 to 30 lowercase letters, numbers,
or hyphens. A new project takes a few minutes to show up in the list. If it isn’t there, wait a
moment and click the refresh button at the top right.
Zoomed in
5
Project and plan: billing check
As soon as you pick a project, the wizard checks its billing status. If you see
Billing is enabled for this project (이 프로젝트에서 결제가 활성화되어 있습니다), move on.If you see Billing not enabled (결제가 활성화되지 않음), deployment is blocked. Click
this project’s billing page (이 프로젝트의 결제 페이지) in the message, link a billing
account, come back, and click Recheck billing status (결제 상태 다시 확인).
Zoomed in
6
Project and plan: pick a plan and deploy
Pick a resource plan (리소스 요금제) and click Deploy (배포). Starting on Free (무료)
is fine; you can change it later on the App Status screen.
Plan
Resources
Use
Approx. GCP cost
Free (무료)
1 vCPU, 256 MB
Development and testing
$0 within the free tier
Basic (베이직)
1 vCPU, 512 MB
Recommended
About $5/month
Performance (퍼포먼스)
2 vCPU, 1 GB
High traffic
About $15/month
Zoomed in
Running Magic Meal Kits itself is free. Google Cloud bills infrastructure directly, with a
generous free allowance. Actual cost depends on your usage and region.
7
Confirm the deployment
In the Deploy to Cloud Run? (Cloud Run에 배포할까요?) dialog, click Deploy (배포).
Zoomed in
8
Deploy: wait
Building the server takes a few minutes. Keep the tab open while you wait. If a billing
problem shows up at this point, you get a billing-required notice and go back to step 2.
Zoomed in
9
Done
The Deployment complete (배포 완료) screen shows your service URL. Click
View App Status (앱 상태 보기).
Zoomed in
10
Copy the API key from App Status
On the App Status (앱 상태) screen, copy the key with the copy button next to API key
(API 키). The service URL is in the Deployment (배포) card further down the same screen. You
use both values in the first module test.
To move your server to the latest version, click Redeploy (재배포) at the top right of the
App Status screen. The Version (버전) card on the same screen shows your current version and
the last deploy time. A redeploy upgrades the server you already have: it swaps the running
container for the latest version and creates a new Cloud Run revision.
Zoomed in
Preserved
Changes
Server URL, API key, license
The container image / version
GCP project and region
A new Cloud Run revision is created
Firestore & BigQuery data
Environment variables / config
Redeploying does not lose data and does not change your URL or API key. Only the server
version moves forward. There is no automatic update notice; redeploy from the App Status screen
whenever you want.
