Search Results

Search found 2 results on 1 pages for 'denisw'.

Page 1/1 | 1 

• Can I set up a hostname alias that is only active in a specific network?

  - by denisw

  I have a small ARM box running ownCloud in my house, and a domain bound to my DSL router with Dynamic DNS. This works well as I can configure the ownCloud client to use the domain name, which works both in the house and when I'm on the road. However, at home I would like to let my laptop and my server talk to each other directly on the local network, rather than as if they were talking over the Internet (including DNS resolution for my domain name, routing all traffic through the DSL machinery etc.). I know that I can set a hostname alias for my domain in /etc/hosts - the problem is that I want this alias to only be active when I'm in the home network, while in all other cases DNS resolution should be used as normal. Is this possible?

  Read the article

• Make Trac use a Drupal user database for authentication

  - by denisw

  I am trying to set up a Trac instance as a complement to a Drupal site and would like to give users the possibility to use their Drupal account in Trac, too, ideally in a single sign-on fashion (if the user is already logged into Drupal, he is automatically logged into Trac). The question now is how to accomplish this. I have found a plugin named DrupalIntegration which seems to implement that functionality; however, it is poorly documented - in fact, not documented at all. I managed to install it, but don't know how to configure it. Here is what I came up with from looking at the source code and the documentation of the AccountManager plugin (on which DrupalIntegration depends): [components] trac.web.auth.loginmodule = disabled acct_mgr.api = enabled acct_mgr.web_ui.LoginModule = enabled acct_mgr.web_ui.RegistrationModule = disabled TracDrupalIntegration.DrupalIntegration = enabled [account-manager] drupal_database = mysql://<usernam>:<password>@localhost/<db> password_store = DrupalIntegration (<username>, <password> and <db> are naturally substituted with the correct data). While the Trac log says: 2010-12-18 10:54:09,570 Trac[loader] DEBUG: Loading TracDrupalIntegration from /usr/lib/python2.5/site-packages/TracDrupalIntegration-0.1-py2.5.egg this doesn't seem to work: trying to log in with a Drupal username / password results in an "Invalid username or password" error. Has someone used the DrupalIntegration and can point out to me what I did wrong? Or is there any other approach you know (or even have used in the past) to integrate Drupal and Trac that way?

  Read the article

1