This forum is no longer active. Please post your questions to our new community site
Recent Posts by kamko
|
27 Feb, 2009 07:32 AM
|
Topic: Trac / .htaccess forwarding in the /apache2/htdocs directory? Your welcome antonio! I’m glad to help: i’m sure I’m not the only one with this question and i’m glad to help the bitnami community. I read in the main forum that you’re transitioning from bitnami forum support. Perhaps I can help with bitnami. Can you private message me as well, or have the your colleague message me. Or send me an email at the address I registered with for the forums. I’d like to ask a followup question on this thread on how I can help however I need some input on it over email before I just go ahead and post away. Thanks, and your help has really been valuable. I’ve learned so much from your posts. |
|
25 Feb, 2009 06:46 AM
|
Topic: Trac / .htaccess forwarding in the /apache2/htdocs directory? Ah, found the answer. Here’s the step by step process to make the top level ”/apache2/htdocs directory” enable redirects via mod_alias (ie: a visit to index.html will be forwarded to another page due to an .htaccess file’s Redirect instruction). I have tested this and this should work on a vanilla, just created, instance of the bitnami Trac stack. (PLEASE verify though) Open the httpd.confg file and where the <directory /> </ Directory> command is, replace with either [note: if possible, please tell me which is better so we can update this thread!] <Directory /> Options FollowSymLinks AllowOverride All Order deny,allow Deny from all Satisfy all </Directory> Or: <Directory /> Options All AllowOverride All </Directory> Also, under : <Directory "/home/falconviewuserssh/trac-0.10.4-9/apache2/htdocs"> update the AllowOverride attribute, from: AllowOverride None to: AllowOverride All Finally: make an .htaccess file and give it the following instruction:
Please reply back if you had a chance to verify the instructions above. Thanks! |
|
13 Feb, 2009 03:02 PM
|
Topic: Trac / .htaccess forwarding in the /apache2/htdocs directory? Antonio, thanks for responding. Which module are we talking about? Hmm, The guy in the last post never got a chance to followup on the post. Do I need to turn on mod_rewrite? When I check the mod_rewrite doc at: http://httpd.apache.org/docs/1.3/mod/mod_rewrite.html That website doesn’t mention specifically the ‘Redirect’ command in htaccess anywhere … it does talk about Rewrite rules a lot though, but I think I’m looking for info on Redirect. |
|
13 Feb, 2009 01:23 AM
|
Topic: Trac / .htaccess forwarding in the /apache2/htdocs directory? Hello, Hopefully from what I did so far, this doesn’t come off as a newbie question. I did look at another user’s post in the forum on htaccess config with joomla [1] that I thought was useful but perhaps someone can provide some insight here: Steps so far: I created an .htaccess file in the /apache2/htdocs directory to redirect. it had this instruction only: Redirect /index.html http://domain.com/trac/our_proj That by itself didn’t work. I found in the httpd.conf file that AllowOverride was set to “AllowOverride None” so i changed it to: still didn’t work. Are there any are additional settings anywhere that I need to modify for .htaccess files to work? [1] http://bitnami.org/forums/forums/3/topics/741 – I want to get some guidance before I start messing around more with the comments in this thread so that I know I’m on the right track and doing the steps to get this to work… |
|
06 Feb, 2009 06:37 AM
|
Topic: Trac / How to prepare for future bitnami Trac update? Hey Antonio, Trying to be thorough here with this post. Bear with me. ;) Let me clarify on the question that you requested more information on, where you mentioned:
So, to install trac, we install trac by using the following file (at present time this is true, at least): bitnami-trac-0.10.4-9-linux-installer.bin Obviously, that file is a binary and we all know that is not possible for one to ‘review’ binaries in a text editor like they would source code. However, will the update from trac-0.10.4-9 to trac.-0.11 be: a. a closed, unable to be viewed, binary file (as well)
or I think some of this question could possibly have been answered when you mentioned above that you guys
The only reason I ask is that people modify their Trac installations, and they may want to review what happens in an update. For instance, I use some plugins with my trac installation, so I might really need to know what’s in the update script to make sure the upgrade is compatible and so I can do testing before I certify the update for my installation of Trac. If there is a problem, I’ll like to know what I have to do to adjust my settings so that the upgrade will function. :) |
|
31 Jan, 2009 11:52 PM
|
Topic: Trac / Updated version of the Trac stack ? ... jphlechene, Can you provide a link to the “post on the bitnami website to describes the manipulation required to manually update from 0.10.4-9 to 0.11”? I’m having some trouble locating it. :/ In addition, since I notice now it’s February 2009 and this thread was last updated in September 2008, if any information on updating that was published then is now outdated, please forward me to a better source if you know of it. |
|
31 Jan, 2009 11:44 PM
|
Topic: Trac / How to prepare for future bitnami Trac update? hi, I noticed jphlechene’s post dated Sep 25, 2008 7:53AM (http://bitnami.org/forums/forums/18/topics/664#posts-2404) asking about the plans for an updated Trac Stack. However, my question is different but in the same area. I am currently using Trac to manage a project and I was wondering how the update process will work before our team customizes or modifies Trac / SVN / Apache in any way, which I fear could make more difficult or jeopardize our ability to update Trac via the bitnami process. So here are the questions:
kamko |

