Multiple ReviewBoard install on one server interfere with each other
I've installed RB twice, in 2 separate subdirectories, each using a
separate run of rb-site. One is in /local/reviews, and a test/debug one is
in /local/reviews-test. I have set up an Apache config. to set up each of
these as separate sub-URLs on the same server (no virtual servers).
I am finding that I can get into one OK, but when I try to get into the
other, it gives errors trying to access the other! I can see nothing in
the DB or settings in either that refer to the other. An example error I
get when accessing the main one (/reviews/) is:
Page not found (404) Request Method: GET Request URL:
http://localhost/reviews/dashboard/
Using the URLconf defined in djblets.util.rooturl, Django tried these URL
patterns, in this order:
1. ^reviews-test/
The current URL, reviews/dashboard/, didn't match any of these.
You're seeing this error because you have DEBUG = True in your Django
settings file. Change that to False, and Django will display a standard 404
page.
Where did the ref. to /reviews-test/ come from? I had been getting it the
other way around (reviews-test failed accessing reviews) until I restarted
httpd, and could log into the test one. But now the main one fails.
Here's the config:
# RB access itself
WSGIScriptAlias /reviews /local/reviews/htdocs/reviewboard.wsgi/reviews
Directory /local/reviews/htdocs
# Error handlers
ErrorDocument 500 /errordocs/500.html
WSGIPassAuthorization On
AllowOverride All
Options -Indexes FollowSymLinks
Allow from all
/Directory
# Alias static media requests to filesystem
Alias /reviews/media /local/reviews/htdocs/media
Alias /reviews/errordocs /local/reviews/htdocs/errordocs
Alias /reviews/favicon.ico
/local/reviews/htdocs/media/rbcommons/images/favicon.png
# TEST
# RB access itself
WSGIScriptAlias /reviews-test
/local/reviews-test/htdocs/reviewboard.wsgi/reviews-test
## NB - I guessed at the argument above also including '-test', that may be
wrong to do
Directory /local/reviews-test/htdocs
# Error handlers
ErrorDocument 500 /errordocs/500.html
WSGIPassAuthorization On
AllowOverride All
Options -Indexes FollowSymLinks
Allow from all
/Directory
# Alias static media requests to filesystem
Alias /reviews-test/media /local/reviews-test/htdocs/media
Alias /reviews-test/errordocs /local/reviews-test/htdocs/errordocs
Alias /reviews-test/favicon.ico
/local/reviews-test/htdocs/media/rbcommons/images/favicon.png
I had to fiddle with the script-generated one to get it to work outside of
a virtual server setting.
And the site settings for the main one:
# Site-specific configuration settings for Review Board
# Definitions of these settings can be found at
# http://docs.djangoproject.com/en/dev/ref/settings/
# Database configuration
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.mysql',
'NAME': 'reviewboard',
'USER': 'review_board_user',
'PASSWORD': 'xxx',
'HOST': 'localhost',
'PORT': '',
},
}
# Unique secret key. Don't share this with anybody.
SECRET_KEY = 'xxx'
# Cache backend settings.
CACHE_BACKEND = 'memcached://localhost:11211/'
# Extra site information.
SITE_ID = 1
SITE_ROOT = '/reviews/'
FORCE_SCRIPT_NAME = ''
DEBUG = True
The test settings have equiv. values, with a diff. NAME (d/b name) value.
Full disclosure: I originally had the test one installed in
/local/reviews-test but using the reviews d/b and /reviews/ path, and have
moved it (renamed the d/b) while updating the d/b and Apache settings. I
then created the 'main' one in /local/reviews/ using the right values.
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/reviewboard?hl=en
Getting warnings about cache miss for large diffs
Hi, I thought this issue has been fixed long ago, but I seemed to see its recurrence every once in awhile: Cache miss for key reviewboard...:diff-sidebyside-hl-989989 Cache miss for key reviewboardcom:perforcecom://path/to/file WARNING - Failed to fetch large data from cache for key reviewboard...com://path/to/file version: 1.6.13 djblets: 0.6.23 django: 1.3.3 evolution: 0.6.7 memcached -d -p 11211 -u memcached -m 2048 -c 1024 Can anyone shed some light?. Thanks -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Integration of RB with Gitlab
Hi, I'm trying to setup ReviewBoard to work with Gitlab repository. Since Gitlab has a web front end API, From everything I've read so far, seems the most straightforward integration would be to specify a Raw File URL mask in the repository setup. However, I've run into a bit of a problem. It looks like for revision placeholder, RB server will pass in file blob's SHA1, but Gitlab API wants the client to pass in SHA1 of the commit. So far in all my searching/googling I haven't found a way to either modify RB to pass in SHA1 of the commit or a different Gitlab HTTP URL that would accept SHA1 of the file blob. Are you aware of anyone else that successfully integrated Gitlab with ReviewBoard? Could I be missing something fundamentally easy? Or is my only option to setup a cron job that would periodically update local repository on the RB server thank you -- Dennis -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Will there be a 1.6.14 release
Just checking to see if a 1.6.14 release is planned or the next release will be 1.7. If there is a better place for such questions, please let me know. Thanks, -amac -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Integration of RB with Gitlab
For remote access, we need a URL that provides file contents based on blob sha1. I don't really know anything about gitlab, but we've previously had pretty good success getting hosting providers to add an API for us when we need it (access by blob is a pretty trivial thing). If you can't do that, an in-sync local repo is probably your best bet. -David -David On Tue, Nov 20, 2012 at 12:49 PM, DXM dxm...@gmail.com wrote: Hi, I'm trying to setup ReviewBoard to work with Gitlab repository. Since Gitlab has a web front end API, From everything I've read so far, seems the most straightforward integration would be to specify a Raw File URL mask in the repository setup. However, I've run into a bit of a problem. It looks like for revision placeholder, RB server will pass in file blob's SHA1, but Gitlab API wants the client to pass in SHA1 of the commit. So far in all my searching/googling I haven't found a way to either modify RB to pass in SHA1 of the commit or a different Gitlab HTTP URL that would accept SHA1 of the file blob. Are you aware of anyone else that successfully integrated Gitlab with ReviewBoard? Could I be missing something fundamentally easy? Or is my only option to setup a cron job that would periodically update local repository on the RB server thank you -- Dennis -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Will there be a 1.6.14 release
Hi, Yes, I'll be pushing out a 1.6.14 probably this week. We'll continue to release 1.6.x releases for a little while after 1.7 is out. I'm putting out an RC of 1.7 hopefully also this week. Christian On Nov 20, 2012, at 13:29, amac freea...@gmail.com wrote: Just checking to see if a 1.6.14 release is planned or the next release will be 1.7. If there is a better place for such questions, please let me know. Thanks, -amac -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Integration of RB with Gitlab
On 2012-11-20 15:49, DXM wrote: I'm trying to setup ReviewBoard to work with Gitlab repository. Since Gitlab has a web front end API, From everything I've read so far, seems the most straightforward integration would be to specify a Raw File URL mask in the repository setup. However, I've run into a bit of a problem. It looks like for revision placeholder, RB server will pass in file blob's SHA1, but Gitlab API wants the client to pass in SHA1 of the commit. Sorry to say, but if Gitlab cannot give you a blob by it's identifying SHA, you are out of luck. By the time a diff makes it to RB, the SHA of the commit against which the diff was generated is no longer known. (And I am not aware that it is possible to determine what commit owns a particular blob ID.) So... basically, see David's reply for your options. Getting the Gitlab server patched is probably best; being able to retrieve blobs by ID is a feature the server really ought to provide. (I had the same problem with an older gitorious server, and spent some time trying to determine if there was some other solution short of a complete mirror of the repository - e.g. a local web service that could fetch just the necessary blob - but wasn't able to come up with anything. In the end, I had to patch the gitorious server. Fortunately upstream gitorious has already been patched, so it was just a matter of grabbing the necessary patch from upstream and applying it.) p.s. If you end up patching Gitlab yourself, what you need is basically a URL that gives you the output of 'git show blob-id'. The path isn't actually needed for git. -- Matthew -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Integration of RB with Gitlab
Thank you for the reply, guys. I wonder if I could just write my own stand-alone service (listening on port 8080) that could sit on the gitlab box and just serve up the output of 'git show... command. On Tuesday, November 20, 2012 5:39:36 PM UTC-5, Matthew Woehlke wrote: On 2012-11-20 15:49, DXM wrote: I'm trying to setup ReviewBoard to work with Gitlab repository. Since Gitlab has a web front end API, From everything I've read so far, seems the most straightforward integration would be to specify a Raw File URL mask in the repository setup. However, I've run into a bit of a problem. It looks like for revision placeholder, RB server will pass in file blob's SHA1, but Gitlab API wants the client to pass in SHA1 of the commit. Sorry to say, but if Gitlab cannot give you a blob by it's identifying SHA, you are out of luck. By the time a diff makes it to RB, the SHA of the commit against which the diff was generated is no longer known. (And I am not aware that it is possible to determine what commit owns a particular blob ID.) So... basically, see David's reply for your options. Getting the Gitlab server patched is probably best; being able to retrieve blobs by ID is a feature the server really ought to provide. (I had the same problem with an older gitorious server, and spent some time trying to determine if there was some other solution short of a complete mirror of the repository - e.g. a local web service that could fetch just the necessary blob - but wasn't able to come up with anything. In the end, I had to patch the gitorious server. Fortunately upstream gitorious has already been patched, so it was just a matter of grabbing the necessary patch from upstream and applying it.) p.s. If you end up patching Gitlab yourself, what you need is basically a URL that gives you the output of 'git show blob-id'. The path isn't actually needed for git. -- Matthew -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Integration of RB with Gitlab
On 2012-11-20 17:54, DXM wrote: Thank you for the reply, guys. I wonder if I could just write my own stand-alone service (listening on port 8080) that could sit on the gitlab box and just serve up the output of 'git show... command. If you can run git against something that looks like a git checkout (I think a bare repo would work also) on the Gitlab server, that should work. (But I would still recommend putting in a feature request for Gitlab :-).) I couldn't do that with gitorious because there aren't readily accessible repositories; I would have needed to clone the gitorious repo for such a service (and at that point, you might as well keep the clone where RB can talk to it directly). -- Matthew -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
