You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -122,6 +122,8 @@ Deployment setup:
122
122
123
123
After successful deployment, obtain the bot API URL from either `deploy-services` job results or from [GCP Project Console](https://console.cloud.google.com) and proceed to [switching bot environment](#switching-bot-environment).
124
124
125
+
Alternatively, to fit within the [GCP free tier](https://cloud.google.com/free/docs/free-cloud-features#free-tier), you can deploy PostgreSQL on an e2-micro Compute Engine VM and connect Cloud Run services using [Direct VPC](https://cloud.google.com/run/docs/configuring/vpc-direct-vpc). However, because a self-managed PostgreSQL instance requires additional configuration and operational oversight, this approach is not covered in this instruction.
126
+
125
127
## Switching bot environment
126
128
After the bot is either [launched locally](#local-environment) or [deployed in GCP](#production-deployment), Telegram needs to be configured with a proper webhook URL. To set it, use:
0 commit comments