This forum is no longer active. Please post your questions to our new community site
Unable to work with Apache/SVN
|
|
Hi. The latest Bitnami Redmine doesn’t work with Apache/SVN configuration. I added the following Location to httpd.conf: <Location /svn> And tried to access the repository via HTTP. But I’m receiving the following error in logs: I double checked, and don’t have any other sqlite libs then does coming with CentOS, but these are 64-bit and 3.3.6 – not 3.3.7. Any idea what causes this? Regards. |
|
|
Hi, Sorry, it is a really strange error and we can not reproduce this issue on our systems. Could you check the sqlite version included in the Stack and the system version? Have you restarted Apache using “ctlscript.sh” ? |
|
|
Hi, i can confirm this error on a plain install of Ubuntu 8.04 LTS Server. Best regards. |
|
|
Hi, btw. i’m using the 32 bit Version of Ubuntu. Best regards. |
|
|
Hi, Just wanted to let you know that we are taking a look into this. Cheers, Victoria. |
|
|
Great, we’re really looking forward to use the bitnami stack. Best regards. |
|
|
Hi, It seems that the problem is with the Apache PHP module. If you are not using the PHP bundled in the stack with any other application, you can simple open the /apache2/conf/httpd.conf file and coment the line: LoadModule php5_module modules/libphp5.so Now restart apache executing /ctlscript.sh restart We’ll to fix this but in meantime this should make work the Apache/Subversion configuration :) |
|
|
Hi, works perfectly. Thank you very much! Best regards. |
|
|
Any news on this issue? Best regards. |
|
|
I just wanted to let you know that the current Bitnami Redmine version is still affected by this problem. EDIT: I was quite surprised to find out that you do not seem to have a public bugtracker. You offer all these awesome project management tools yet you are not even using one for your own project? |
|
|
Hi, We use BitNami Redmine for traking issues internally. This issue only happens is you want to enable WebDAV and if you have enabled PHP in the RubyStack, not in the Redmine Stack itself. This is a low priority issue, anyway it is in our tracking tool :) |

