can't find DSN for projects

[mfrasca]

comparing the docs with the current behaviour.

cd Local/github.com/dcramer/sentry/
virtualenv /usr/share/sentry/
source /usr/share/sentry/bin/activate
python setup.py install
sentry init /usr/share/sentry/etc/sentry.conf.py
sentry --config=/usr/share/sentry/etc/sentry.conf.py upgrade
sentry --config=/usr/share/sentry/etc/sentry.conf.py start

then I look for information on how to get to know public and private keys of the default project.
I would expect it on the sentry documentation, but I find it in raven:
http://raven.readthedocs.org/en/latest/config/index.html#the-sentry-dsn

it states I should follow the sequence of links:
Account -> Projects -> [Project Name] -> [Member Name]

I direct my browser to http://localhost:9000/

the described sequence is only available after I login.

after login I follow the steps, but the information is not there.

should I tweak the configuration to have it work?
or what am I missing?

thanks!
MF

[dcramer]

I've corrected this issue and pushed out a bugfix release as 4.0.5. The migrations will automatically fix any missing project keys.

Once you've updated, just go to Account -> Projects, and you'll see your DSN there.

[mfrasca]

:) thanks!
(don't forget to update the docs)

[mrooney]

I'm seeing the same thing on a fresh 4.1.7, then upgraded to 4.2.1 to see if that fixed it. This whole new DSN is rather confusing as a previous Sentry user, alas, but it could be completely my fault. I tried messing around and creating a team and member but I'm still not sure how to get a client sending errors to Sentry. Any help would be greatly appreciated!

[dcramer]

@mrooney It should show up on the main page if you havent sent events (assuming you're logged in), otherwise it's under your project's settings.

[mrooney]

thanks @dcramer! I dropped the database then recreated it, and /this/ time I said yes to creating a superuser, and after logging in with those credentials, the DSN showed up.

It would be great if the documentation at http://sentry.readthedocs.org/en/latest/quickstart/index.html mentioned that you should say yes to this, or create it yourself, and then tell you to log in with the superuser to get your DSN, then perhaps even recommend a "raven test", so you have everything you need to get started after reading that. Those were the critical steps I missed if they were documented. The first time, even after running "sentry createsuperuser" myself and logging in, the DSN was really nowhere to be found, but this time it worked, creating the superuser when it asked.

Thanks again for the rad project and your help.

[mfrasca]

@mrooney : the issue here is currently closed. I suggest you (re)open (it)(a new one), but even better correct the docs in your own fork and open a pull request. @dcramer is very responsive to clear and limited pull reqs. ciao! M