In Sentry 8.15 using system.url-prefix
don't use that settings in UI links. Also in manage, account and api endpoints.
If we get the value with:
sentry config get system.url-prefix
type: STRING
from config: https://xxxx.com/sentry
current: https://xxxx.com/sentry
In sentry.config.py
FORCE_SCRIPT_NAME = '/sentry'
NGINX relevant config:
# Sentry
# if your main app's static media is served at _static, you're screwed
rewrite ^(/_static/)(.*)$ https://xxxx.com/sentry/_static/$2 permanent;
rewrite ^(/api/)(.*)$ https://xxxx.com/sentry/api/$2 permanent;
location /sentry {
# rewrite /sentry/(.*) /$1 break;
include uwsgi_params;
uwsgi_param SCRIPT_NAME /sentry;
uwsgi_pass 127.0.0.1:9001;
uwsgi_modifier1 30;
uwsgi_param Host $host;
uwsgi_param X-Real-IP $remote_addr;
uwsgi_param X-Forwarded-For $proxy_add_x_forwarded_for;
uwsgi_param X-Forwarded-Proto $http_x_forwarded_proto;
}
Installation is through virtualenv
PIP freeze output
amqp==1.4.9
anyjson==0.3.3
appdirs==1.4.3
asn1crypto==0.22.0
billiard==3.3.0.23
boto3==1.4.4
botocore==1.5.39
celery==3.1.18
cffi==1.10.0
click==6.7
contextlib2==0.5.4
cryptography==1.8.1
cssselect==1.0.1
cssutils==0.9.10
Django==1.6.11
django-crispy-forms==1.4.0
django-debug-toolbar==1.3.2
django-jsonfield==0.9.13
django-picklefield==0.3.2
django-sudo==2.1.0
django-templatetag-sugar==1.0
djangorestframework==2.4.8
docutils==0.13.1
email-reply-parser==0.2.0
enum34==1.1.6
exam==0.10.6
futures==3.1.1
hiredis==0.1.6
honcho==0.7.1
httplib2==0.10.3
idna==2.5
ipaddress==1.0.18
jmespath==0.9.2
kombu==3.0.35
libsourcemap==0.5.0
loremipsum==1.0.5
lxml==3.7.3
mmh3==2.3.1
mock==1.0.1
oauth2==1.9.0.post1
packaging==16.8
percy==0.4.4
petname==1.7
Pillow==3.2.0
progressbar2==3.10.1
psycopg2==2.6.2
py==1.4.33
pycparser==2.17
pyOpenSSL==16.2.0
pyparsing==2.2.0
pytest==2.6.4
pytest-django==2.9.1
pytest-html==1.9.0
python-dateutil==2.6.0
python-memcached==1.58
python-openid==2.2.5
python-u2flib-server==4.0.1
python-utils==2.1.0
pytz==2017.2
PyYAML==3.11
qrcode==5.3
raven==5.33.0
rb==1.6
redis==2.10.5
requests==2.12.5
s3transfer==0.1.10
selenium==3.0.0b3
sentry==8.15.0
setproctitle==1.1.10
simplejson==3.8.2
six==1.10.0
South==1.0.1
sqlparse==0.2.3
statsd==3.1
structlog==16.1.0
symsynd==2.4.0
toronado==0.0.11
ua-parser==0.7.3
urllib3==1.16
uWSGI==2.0.15
Subpaths are not supported per our documentation.
We don't support running Sentry at a subpath. See: https://github.com/getsentry/sentry/pull/5174
But why? What's difficult with allowing to specify? There are some circumstances that subdirectory is better than subdomains (for example not having a wildcard certificate and not wanting to expose other ports than 80/443.
I've done something in django some time ago, a framework has means to put an application into directory. Just why?
edit: even javascripts construct URL-s using baseUrl option.
Most helpful comment
But why? What's difficult with allowing to specify? There are some circumstances that subdirectory is better than subdomains (for example not having a wildcard certificate and not wanting to expose other ports than 80/443.
I've done something in django some time ago, a framework has means to put an application into directory. Just why?
edit: even javascripts construct URL-s using
baseUrloption.