Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

quickstart documentation misses --config at sentry migrate #425

Closed
mfrasca opened this issue Apr 12, 2012 · 3 comments
Closed

quickstart documentation misses --config at sentry migrate #425

mfrasca opened this issue Apr 12, 2012 · 3 comments

Comments

@mfrasca
Copy link
Contributor

mfrasca commented Apr 12, 2012

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? ;)
@mfrasca
Copy link
Contributor Author

mfrasca commented Apr 12, 2012

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.

@dcramer
Copy link
Member

dcramer commented Apr 12, 2012

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)

@dcramer
Copy link
Member

dcramer commented May 1, 2012

Closing this as the original problem was fixed

@dcramer dcramer closed this as completed May 1, 2012
@github-actions github-actions bot locked and limited conversation to collaborators Dec 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants