kmlabz/sentry-onpremise
kmlabz/sentry-onpremise
Archived
2
0
Fork 0
Code Pull Requests Releases Activity
This repository has been archived on 2020-07-19. You can view files and clone it, but cannot push or open issues or pull requests.
630bba4026
sentry-onpremise/.gitignore

86 lines
1.1 KiB
Plaintext
Raw Normal View History

Getting started
2016-02-11 22:52:19 +01:00
# Byte-compiled / optimized / DLL files
__pycache__/
*.py[cod]
*$py.class
# C extensions
*.so
# Distribution / packaging
.Python
env/
build/
develop-eggs/
dist/
downloads/
eggs/
.eggs/
lib/
lib64/
parts/
sdist/
var/
*.egg-info/
.installed.cfg
*.egg
# PyInstaller
# Usually these files are written by a python script from a template
# before PyInstaller builds the exe, so as to inject date/other infos into it.
*.manifest
*.spec
# Installer logs
pip-log.txt
pip-delete-this-directory.txt
feat(install): Add automatic logs to install script (#312) This change makes the install script create a new install log file, `sentry_install_log-<ISO_TIMESTAMP>.txt`, for each run and records all the output there for future reference.
2020-01-03 11:17:35 +01:00
sentry_install_log*.txt
Getting started
2016-02-11 22:52:19 +01:00
# Unit test / coverage reports
htmlcov/
.tox/
.coverage
.coverage.*
.cache
nosetests.xml
coverage.xml
Fix possible typo in gitignore Remove a match-all glob pattern. It looks like some non-git tools read the `*,cover` as `*` and `cover` separately and basically ignore all files. Even though this is not really a problem with the repo itself, I think the change is still valid, considering `*,cover` looks like an invalid rule anyway. _____ Background: (__This part is vim-specific__) For a while now, my Neosnippet configuration has been going for a toss when working on our fork based off of this repo. I see a message similar to the one reported [here](https://github.com/Shougo/neocomplcache.vim/issues/468), but my vimrc configuration is as per the documentation available in the plugin docs. I finally spent enough time to debug this today, and it turns out this issue was happening *only* in this repo and nowhere else. So I went through the files that might've to do anything with folder-specific configuration (think dotenv, editorconfig etc.), and turned out `.gitignore` was the only such file; I use [this plugin](https://github.com/vim-scripts/gitignore) to load the gitignore rules into the `wildmenu` completion and the `*,` part basically (from what I understand) removes most of the load path configuration from vim 😄. I'll probably have to go make a change in that plugin as well though.
2019-06-12 08:07:53 +02:00
*.cover
Getting started
2016-02-11 22:52:19 +01:00
.hypothesis/
# Translations
*.mo
*.pot
# Django stuff:
*.log
local_settings.py
# Sphinx documentation
docs/_build/
# PyBuilder
target/
# Ipython Notebook
.ipynb_checkpoints
# pyenv
.python-version
Improve setup (#123) * declare sentry volumes external * move SENTRY_SECRET_KEY to .env file (not in git repo) * ignore docker-compose.override.yml to allow extending
2018-10-17 19:02:22 +02:00
# https://docs.docker.com/compose/extends/
docker-compose.override.yml
Getting started
2016-02-11 22:52:19 +01:00
*.tar
Mount the required volume
2016-05-28 01:44:34 +02:00
data/
Fix possible typo in gitignore Remove a match-all glob pattern. It looks like some non-git tools read the `*,cover` as `*` and `cover` separately and basically ignore all files. Even though this is not really a problem with the repo itself, I think the change is still valid, considering `*,cover` looks like an invalid rule anyway. _____ Background: (__This part is vim-specific__) For a while now, my Neosnippet configuration has been going for a toss when working on our fork based off of this repo. I see a message similar to the one reported [here](https://github.com/Shougo/neocomplcache.vim/issues/468), but my vimrc configuration is as per the documentation available in the plugin docs. I finally spent enough time to debug this today, and it turns out this issue was happening *only* in this repo and nowhere else. So I went through the files that might've to do anything with folder-specific configuration (think dotenv, editorconfig etc.), and turned out `.gitignore` was the only such file; I use [this plugin](https://github.com/vim-scripts/gitignore) to load the gitignore rules into the `wildmenu` completion and the `*,` part basically (from what I understand) removes most of the load path configuration from vim 😄. I'll probably have to go make a change in that plugin as well though.
2019-06-12 08:07:53 +02:00
.vscode/tags
feat(sentry10): Make on-premise work for Sentry 10 (#220)
2019-11-12 00:18:59 +01:00
# custom Sentry config
sentry/sentry.conf.py
sentry/config.yml
feat: Instruct users to migrate TSDB (#430) Tested this in a Ubuntu VM. The output of `date` is not too pretty but at least localized (so D/M vs M/D is not confusing) ## What is the TSDB migration? We're effectively deprecating all TSDB backends but `sentry.tsdb.redissnuba.RedisSnubaTSDB`. We cannot reasonably support any other backend due to the fact that we would have to reimplement each of the backends in Relay, which is written in a different language. Also, like with deprecating mysql support, we don't really have the capacity to support things we do not use ourselves. ## Migration `install.sh` should rewrite your configuration automatically and define a cutover date such that no data is lost. Before the cutover date, data is written to two backends at once, Redis and Snuba, and read from one, Redis. After the cutover date, event-related metrics will be read from Snuba which matches what we have on sentry.io. ## Manual migration guide for TSDB In case `install.sh` is unable to migrate your files you will be given basic instructions on the console that essentially tell you to completely delete all TSDB config and paste the new, standard one. If for some reason you cannot say goodbye to your existing TSDB config, please create a new issue in this repo and cc @untitaker on it.
2020-05-12 12:02:40 +02:00
sentry/*.bak
feat(sentry10): Make on-premise work for Sentry 10 (#220)
2019-11-12 00:18:59 +01:00
sentry/requirements.txt
feat(relay): Add Relay to onpremise installation (#421) Co-Authored-By: Burak Yigit Kaya <byk@sentry.io>
2020-04-24 14:31:59 +02:00
relay/credentials.json
ref(relay): Remove PK and rely on INTERNAL_IPS (#572) This patch adds `INTERNAL_IPS` definition to `sentry.conf.py` by sniffing the network from eth0 and relies on this for trusted Relays instead of the ALLOWLISTED PKs. This removes the necessity of syncing Relay PKs to `sentry.conf.py`. This PR needs getsentry/sentry#19798 to work.
2020-07-10 22:53:50 +02:00
relay/config.yml
Add volumed-out config directory for symbolicator. (#566) I would like to be able to customize the configuration for my Sentry 10 symbolicator instance, which this change allows me to easily do. See related: https://github.com/getsentry/symbolicator/issues/245 Co-authored-by: Burak Yigit Kaya <ben@byk.im>
2020-07-08 19:42:33 +02:00
symbolicator/config.yml
remove github stuff
2020-07-19 01:49:00 +02:00
data/
Copy Permalink