Files
gitrusprusandCursor 10e7d65a00 Fix production auth by proxying /api to backend in remote builds.
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>
2026-06-29 09:33:54 +03:00

34 lines
1.5 KiB
Plaintext
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Прокси на хосте → контейнеры Docker.
# Скопировать:
# sudo cp deploy/apache/social-graph.conf /etc/apache2/sites-available/social-graph.conf
#
# Перед включением поднимите контейнеры:
# docker compose -f docker-compose.prod.yml --env-file deploy/.env.prod up -d frontend
# # при remote: ... --profile with-backend up -d
#
# sudo a2enmod proxy proxy_http headers rewrite
# sudo a2ensite social-graph.conf
# sudo apache2ctl configtest && sudo systemctl reload apache2
<VirtualHost *:80>
ServerName social.deepfishing.ru
ProxyPreserveHost On
RequestHeader set X-Forwarded-Proto "https"
RequestHeader set X-Forwarded-For %{REMOTE_ADDR}s
# Вариант 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>