Qlockify/qlockify-core-deployment
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(deploy): correct google oauth callback settings
Some checks failed
Deployment CI/CD / validate (push) Has been cancelled
Details
Deployment CI/CD / deploy (push) Has been cancelled
Details

Browse Source
This commit is contained in:
Amirhossein Khalili
2026-05-21 19:15:47 +03:30
parent e015f01cd6
commit af0ffb2293
2 changed files with 9 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
README.md
View File

@@ -45,7 +45,7 @@ Main deployed services:
Traffic pattern: Traffic pattern:
- `qlockify.ir` serves the frontend - `qlockify.ir` serves the frontend
- `api.qlockify.ir` serves the backend API, admin, docs, static, and media - backend traffic is served from `qlockify.ir` under `/api` and `/admin`
- Nginx terminates TLS and proxies requests to the frontend and backend containers - Nginx terminates TLS and proxies requests to the frontend and backend containers
## Expected Repository Layout ## Expected Repository Layout
@@ -107,18 +107,17 @@ Configured domains:
- `qlockify.ir` - `qlockify.ir`
- `www.qlockify.ir` - `www.qlockify.ir`
- `api.qlockify.ir`
Behavior: Behavior:
- `www.qlockify.ir` redirects to `qlockify.ir` - `www.qlockify.ir` redirects to `qlockify.ir`
- `http` redirects to `https` - `http` redirects to `https`
- frontend is served from `qlockify.ir` - frontend is served from `qlockify.ir`
- backend traffic is served from `api.qlockify.ir` - backend traffic is proxied from `qlockify.ir/api` and `qlockify.ir/admin`
Before production startup: Before production startup:
1. Point DNS records for `qlockify.ir`, `www.qlockify.ir`, and `api.qlockify.ir` to the server. 1. Point DNS records for `qlockify.ir` and `www.qlockify.ir` to the server.
2. Make sure `80` and `443` are open on the server firewall. 2. Make sure `80` and `443` are open on the server firewall.
3. Make sure the TLS certificate covers all required names. 3. Make sure the TLS certificate covers all required names.
@@ -147,10 +146,10 @@ Set these in:
Core production values: Core production values:
- `DJANGO_ALLOWED_HOSTS=api.qlockify.ir,qlockify.ir,www.qlockify.ir` - `DJANGO_ALLOWED_HOSTS=qlockify.ir,www.qlockify.ir`
- `CORS_ALLOWED_ORIGINS=https://qlockify.ir,https://www.qlockify.ir` - `CORS_ALLOWED_ORIGINS=https://qlockify.ir,https://www.qlockify.ir`
- `CSRF_TRUSTED_ORIGINS=https://api.qlockify.ir,https://qlockify.ir,https://www.qlockify.ir` - `CSRF_TRUSTED_ORIGINS=https://qlockify.ir,https://www.qlockify.ir`
- `BASE_URL=https://api.qlockify.ir` - `BASE_URL=https://qlockify.ir`
- `POSTGRES_HOST=db` - `POSTGRES_HOST=db`
- `REDIS_HOST=redis` - `REDIS_HOST=redis`
- `REDIS_URL=redis://redis:6379/0` - `REDIS_URL=redis://redis:6379/0`
@@ -161,7 +160,7 @@ Google OAuth values:
- `GOOGLE_OAUTH_CLIENT_ID=...` - `GOOGLE_OAUTH_CLIENT_ID=...`
- `GOOGLE_OAUTH_CLIENT_SECRET=...` - `GOOGLE_OAUTH_CLIENT_SECRET=...`
- `GOOGLE_OAUTH_REDIRECT_URI=https://api.qlockify.ir/api/users/oauth/google/callback/` - `GOOGLE_OAUTH_REDIRECT_URI=https://qlockify.ir/api/users/oauth/google/callback/`
- `GOOGLE_OAUTH_FRONTEND_CALLBACK_URL=https://qlockify.ir/auth/google/callback` - `GOOGLE_OAUTH_FRONTEND_CALLBACK_URL=https://qlockify.ir/auth/google/callback`
## Required Frontend Environment ## Required Frontend Environment
@@ -173,7 +172,7 @@ Set this in:
``` ```
```text ```text
VITE_API_BASE_URL=https://api.qlockify.ir/api VITE_API_BASE_URL=/api
``` ```
## Background Workers ## Background Workers

2
backend/.env.sample
View File

@@ -44,7 +44,7 @@ LANGUAGE_CODE=en-us
TIME_ZONE=Asia/Tehran TIME_ZONE=Asia/Tehran
SMS_APIKEY= SMS_APIKEY=
BASE_URL=https://api.qlockify.ir BASE_URL=https://qlockify.ir
GOOGLE_OAUTH_CLIENT_ID= GOOGLE_OAUTH_CLIENT_ID=
GOOGLE_OAUTH_CLIENT_SECRET= GOOGLE_OAUTH_CLIENT_SECRET=
GOOGLE_OAUTH_REDIRECT_URI=https://qlockify.ir/api/users/oauth/google/callback/ GOOGLE_OAUTH_REDIRECT_URI=https://qlockify.ir/api/users/oauth/google/callback/