You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running the instructions from the documentation.
there are two things I notice and had to do differently than in the docs.
I'm using /usr/share/sentry as a base for the virtual environment. I find /www/sentry a bit misleading.
maybe a question of taste, it's my first time using virtualenv, but I would like to have all virtual environments in one predictable place and I would look in /usr/share.
not all virtual environments will be web related after all.
when I run sentry migrate I have to specify the option --config=/path/to/config/file.
this is very clearly mentioned in the paragraph on starting the web service, but that one follows running migrations. as they say here, mustard after lunch.
if sentry init worked with the option --config instead of the optional positional argument, maybe one would be able to guess correctly even without being instructed. or do you expect all users to read carefully all instructions before we start? ;)
The text was updated successfully, but these errors were encountered:
oh, I'm going to use/review the docs for helping us write a logging sentry handler. I plan adding it to the R logging module that I maintain on r-forge.
Ya a lot of the docs are really lacking. I've corrected the migrate command, and I'm completely open to the changes for the /www/ dir (it's just a random loc I chose, I dont even do that in production)
I'm running the instructions from the documentation.
there are two things I notice and had to do differently than in the docs.
maybe a question of taste, it's my first time using
virtualenv
, but I would like to have all virtual environments in one predictable place and I would look in/usr/share
.not all virtual environments will be web related after all.
sentry migrate
I have to specify the option--config=/path/to/config/file
.this is very clearly mentioned in the paragraph on starting the web service, but that one follows running migrations. as they say here, mustard after lunch.
if
sentry init
worked with the option--config
instead of the optional positional argument, maybe one would be able to guess correctly even without being instructed. or do you expect all users to read carefully all instructions before we start? ;)The text was updated successfully, but these errors were encountered: