gitrusprus/social-graph
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix production auth by proxying /api to backend in remote builds.

Browse Source 
Remote frontend nginx now forwards API requests to Django so login and registration work when the host proxy only routes to port 8080.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
gitrusprus
2026-06-29 09:33:54 +03:00
co-authored by Cursor
parent ce4e9ac5e6
commit 10e7d65a00
6 changed files with 70 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
deploy/apache/social-graph.conf
+10 -8
View File
@@ -11,21 +11,23 @@
# sudo apache2ctl configtest && sudo systemctl reload apache2
<VirtualHost *:80>
ServerName your-domain.com
ServerAlias www.your-domain.com
ServerName social.deepfishing.ru
ProxyPreserveHost On
RequestHeader set X-Forwarded-Proto "http"
RequestHeader set X-Forwarded-Proto "https"
RequestHeader set X-Forwarded-For %{REMOTE_ADDR}s
# Backend API (раскомментируйте при VITE_DATA_MODE=remote и profile with-backend)
# ProxyPass /api http://127.0.0.1:8000/api
# ProxyPassReverse /api http://127.0.0.1:8000/api
# Frontend SPA (nginx в контейнере sg_frontend)
# Вариант A (рекомендуется): весь трафик на frontend-контейнер.
# В remote-сборке frontend сам проксирует /api → backend.
ProxyPass / http://127.0.0.1:8080/
ProxyPassReverse / http://127.0.0.1:8080/
# Вариант B: проксировать /api напрямую на backend (если frontend без nginx.remote.conf)
# ProxyPass /api http://127.0.0.1:8000/api
# ProxyPassReverse /api http://127.0.0.1:8000/api
# ProxyPass / http://127.0.0.1:8080/
# ProxyPassReverse / http://127.0.0.1:8080/
ErrorLog ${APACHE_LOG_DIR}/social-graph-error.log
CustomLog ${APACHE_LOG_DIR}/social-graph-access.log combined
</VirtualHost>