I have just downloaded and installed MAMP, and the testlink and mantis modules for it. All work individually, but I'm trying to get mantis integrated with testlink so test link can add new mantis bugs. Sems more config is needed and I found a howto in the doc drectory but it is for version 1.7 of testlink fot latest 1.9.6 and some of the files, sugegested changes needed do no exist in my setup, so I'm a bit stuck. Is there any uptodate documentation/examples on how to do this

dear all,i have an issue integrating mantis to bitnami testlink stack,is it possible? if yes could any one help me with the steps as i googled it but found nothing. thanx

Hi,

I have a bitnami Wordpress blog on my server. (mydomain1.com)

I want to set up a second Wordpress blog on my server. (mydomain2.com)

The end result should be two different Wordpress blogs with different domain names!

How can I do this?

Can I just install bitnami Wordpress to a different location?

Hey all, Please help me out i am stuck deadly :( I have install bitnami redmine on centos (Centos is on VM) it is working fine on it but the problem is i didnt access the repository, so i google and found a script to attach at the bottom of httpd.conf. Script is below

<Location /svn/>
DAV svn

SVNListParentPath on
SVNParentPath "your path to the svn root"
SVNIndexXSLT "/svnindex.xsl"

SVNPathAuthz short_circuit

SVNCacheTextDeltas off
SVNCacheFullTexts off

AuthName "VisualSVN Server"
AuthType VisualSVN
AuthzVisualSVNAccessFile "your path to the svn root/authz-windows"
AuthnVisualSVNBasic on
AuthnVisualSVNIntegrated on
AuthnVisualSVNUPN On

require valid-user

# Add Expires/Cache-Control header explictly
ExpiresActive on
ExpiresDefault access
</Location>

After adding the script and set the subversionparent path, i am able to acceess the external repository, After that i restart my centos machine and run ctlscript.sh to start services of apache,sql and subversion the apache2 did`nt open and show some errors so i google again and add some lines in httpd.conf lines are.

LoadModule dav_svn_module modules/mod_dav_svn.so
LoadModule authz_svn_module modules/mod_authz_svn.so

LoadModule authn_visualsvn_module modules/mod_authn_visualsvn.so
LoadModule authz_visualsvn_module modules/mod_authz_visualsvn.so
LoadModule log_access_visualsvn_module mopdules/mod_log_visualsvn.so

and add their .so files on modules folder then again i start apache2 it is showing syntax error again, and error is

httpd: syntax error on line 116 of /opt/redmine-2.2.3-0/apache2/conf/httpd.conf:cannot load /opt/redmine-2.2.3-0/apache2/modules/mod_authn_visualsvn.so into server: /opt/redmine-2.2.3-0/apache2/modules/mod_authn_visualsvn.so: invalid ELF header apache config test fails, aborting

please help me out i m stuck badly and i donnot understand what to do?

I have downloaded the Bitnami Wordpress stack and have gotten it running on my virtual machine but I'd like WordpIs there Wordpress Multisite instead. I found an AMI file on Amazon that's a Bitnami Wordpress Multisite install, but it runs at Amazon. Is there a Bitnami virtual machine for Multisite or is there a way for me to convert my current Wordpress virtual machine to Multisite?

Hi, I've been using bitnami LAMP for a while. On top of it, I installed wordpress, gallery using bitnami's own packages, and then I've been manually upgrading both.

Is about time I upgrade the distro to a newer ubuntu release - the 10.04 kernel & mysql have not proven to be very stable for me; ever week or two mysql would stop working. I'd like to try a newer kernel and mysql.

Is it possible to do a distribution upgrade from the virtual server command line like in a real server? is there any bitnami-specific caveat I need to be aware of? do I risk breaking wordpress/gallery?

Hi,

I've a "simple" question: it's possible to realize a full disk encryption in a Lampstack? I've seen a lot of articles and most people have solved the problem by reinstalling Ubuntu or using the alternate cd ... which I can't use in the cloud...

For the moment I've an ecrypt folder that I use for backup necessities but I want to do a step forward with a FDE.. are there any best practice or tutorial that I can follow?

I am running MAMP stack 5.3.21, have 2 apache virtual hosts, each with its own cert.

In httpd-ssl.conf, the top virtual host is set to "_ default _".

Access the bottom virtual host under Safari, Chrome, FF has no problem; the right cert is used, and the cert server name matches that of the apache host name.

When I try to access bottom virtual host (as in the httpd-ssl.conf file) using https under IE, and only IE, the cert of the top virtual host is used!

This is really weird.

Anyone got any idea why this is happening?

any help is appreciated

I have a website stored in a folder on my desktop PC which I'd like to host so that it's locally accessible in a browser at a URL like "127.0.0.0.1:82/welcome.html" (rather than its current file URL). I've already used a BitNami stack to host Moodle in a similar fashion and so I presume it can be done for more general webpages...

I've downloaded the WAMP stack and have been browsing various support guides and forum posts to try to understand how to establish a virtual host. I presume this is done with Apache? Is this method correct or am I wasting my time?

I'm currently working through these posts:

• http://bitnami.com/forums/forums/wampstack/topics/using-wampstack-with-virtualhosts
• http://www.stackarena.com/2012/07/creating-virtual-hosts-on-wamp-server/
• http://answers.bitnami.com/questions/9936/virtualhost-on-bitnami-wamp-stack-doesnt-work
• http://wiki.bitnami.com/Components/Apache#How_to_create_a_Virtual_Host.3f

I've not had much success thus far and at the back of my mind is the thought that my method is wrong. Could someone please simply confirm this will work and/or perhaps share some more direct advice?

Hello,

I just installed Bitnami image of Solr on an EC2 server, and actually, I'm stuck :

When I start Solr with the script of Bitnami (./ctlscript.sh restart solr I can't access to Solr (http://my-amazon-ec2.com:8983/solr/admin) from an external IP (404 error by Jetty).

But, when I start it manually with java -jar start.jar , I can access it without problem.

Someone else got this problem ?

I've setup an OSQA stack on AWS EC2 using ami-0c861565 ( http://bitnami.com/stack/osqa/cloud/amazon )

I want to collaborate with others but I'm new to how to do this. I've heard that it's better to make modifications to a web app on a local machine and only when this is working, then push this to the AWS instance.

Is there a best practice on how to do this with an OSQA stack or in general? Do I make a git repo of some of the folders on the AWS instance and the clone them to my local machine? What about the database?

This must be a solved problem but I can't seem to find a good answer. I've done a bit of Django before and you always start working on your local machine and then copy what you have to the server. I've managed to get the local installer working on my laptop (OSX) from here: http://bitnami.com/stack/osqa but I have no idea how to merge this with the layout on the AWS instance.

Hey i am using mantis on XAMP, when i made a new repository an error generates and can`nt access the repository, i add the plugin for repository and subversion code as well their is nothing to add related to repository. Please help me out.

Hello

I am trying to update the Redmine followig this: Updating Redmine code only

But the command: $ rake db:migrate RAILS_ENV="production"

[root@dionisio htdocs]# rake db:migrate RAILS_ENV="production" --trace
** Invoke db:migrate (first_time)
** Invoke environment (first_time)
** Execute environment
** Invoke db:load_config (first_time)
** Execute db:load_config
** Execute db:migrate
==  AddUniqueIndexToIssueRelations: migrating =================================
-- add_index(:issue_relations, [:issue_from_id, :issue_to_id], {:unique=>true})
rake aborted!
An error has occurred, all later migrations canceled:

Index name 'index_issue_relations_on_issue_from_id_and_issue_to_id' on table 'issue_relations' already exists/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/connection_adapters/abstract/schema_statements.rb:576:in `add_index_options'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/connection_adapters/abstract/schema_statements.rb:351:in `add_index'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/migration.rb:466:in `send'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/migration.rb:466:in `method_missing'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/migration.rb:438:in `say_with_time'
/usr/local/lib/ruby/1.8/benchmark.rb:293:in `measure'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/migration.rb:438:in `say_with_time'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/migration.rb:458:in `method_missing'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/migration.rb:334:in `send'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/migration.rb:334:in `method_missing'
/opt/redmine-2.0.2-0/apps/redmine/htdocs/db/migrate/20111201201315_add_unique_index_to_issue_relations.rb:10:in `up'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/migration.rb:370:in `up'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/migration.rb:410:in `send'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/migration.rb:410:in `migrate'
/usr/local/lib/ruby/1.8/benchmark.rb:293:in `measure'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/migration.rb:410:in `migrate'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/connection_adapters/abstract/connection_pool.rb:129:in `with_connection'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/migration.rb:389:in `migrate'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/migration.rb:528:in `__send__'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/migration.rb:528:in `migrate'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/migration.rb:720:in `migrate'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/migration.rb:777:in `call'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/migration.rb:777:in `ddl_transaction'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/migration.rb:719:in `migrate'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/migration.rb:700:in `each'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/migration.rb:700:in `migrate'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/migration.rb:570:in `up'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/migration.rb:551:in `migrate'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-3.2.13/lib/active_record/railties/databases.rake:193
/usr/local/lib/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/task.rb:246:in `call'
/usr/local/lib/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/task.rb:246:in `execute'
/usr/local/lib/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/task.rb:241:in `each'
/usr/local/lib/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/task.rb:241:in `execute'
/usr/local/lib/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/task.rb:184:in `invoke_with_call_chain'
/usr/local/lib/ruby/1.8/monitor.rb:242:in `synchronize'
/usr/local/lib/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/task.rb:177:in `invoke_with_call_chain'
/usr/local/lib/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/task.rb:170:in `invoke'
/usr/local/lib/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:143:in `invoke_task'
/usr/local/lib/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:101:in `top_level'
/usr/local/lib/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:101:in `each'
/usr/local/lib/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:101:in `top_level'
/usr/local/lib/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:110:in `run_with_threads'
/usr/local/lib/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:95:in `top_level'
/usr/local/lib/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:73:in `run'
/usr/local/lib/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:160:in `standard_exception_handling'
/usr/local/lib/ruby/gems/1.8/gems/rake-10.0.4/lib/rake/application.rb:70:in `run'
/usr/local/lib/ruby/gems/1.8/gems/rake-10.0.4/bin/rake:33
/usr/local/bin/rake:19:in `load'
/usr/local/bin/rake:19
Tasks: TOP => db:migrate

How to fix it?

Regards.

Using the latest ReviewBoard VM

I installed the required P4Python modules as follows: cd /opt/bitnami sudo ./use_reviewboard . scripts/setenv.sh easy_install P4PythonInstaller

Now in the admin screen when I attempt to save a Perforce repo I get the following red banner at the top: /opt/bitnami/python/lib/python2.7/site-packages/P4API.so: undefined symbol: ZNSo9_M_insertIlEERSoT

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
***redmine.conf***
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^/(.*) https://%{SERVER_NAME}/$1 [R,L]
SSLRequireSSL
ProxyPass / balancer://redminecluster
ProxyPassReverse / balancer://redminecluster<Proxy balancer://redminecluster>
  RequestHeader set X_FORWARDED_PROTO ‘https’
  BalancerMember http://Bell.BeckwithElectric.inc:3001
  BalancerMember http://Bell.BeckwithElectric.inc:3002</Proxy>
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
httpd.conf
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
#strong text
# This is the main Apache HTTP server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
# In particular, see 
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.  
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so 'log/access_log'
# with ServerRoot set to '/www' will be interpreted by the
# server as '/www/log/access_log', where as '/log/access_log' will be
# interpreted as '/log/access_log'.
#
# NOTE: Where filenames are specified, you must use forward slashes
# instead of backslashes (e.g., "c:/apache" instead of "c:\\apache").
# If a drive letter is omitted, the drive on which httpd.exe is located
# will be used by default.  It is recommended that you always supply
# an explicit drive letter in absolute paths to avoid confusion.

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path.  If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk.  If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
#
ServerRoot "C:/BitNami/redmine-2.3.0-0/apache2"

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to 
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 12.34.56.78:80
Listen 80
#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.so
LoadModule asis_module modules/mod_asis.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule authn_alias_module modules/mod_authn_alias.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbd_module modules/mod_authn_dbd.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authn_file_module modules/mod_authn_file.so
#LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_host_module modules/mod_authz_host.so
#LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule cache_module modules/mod_cache.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule cgi_module modules/mod_cgi.so
#LoadModule charset_lite_module modules/mod_charset_lite.so
#LoadModule dav_module modules/mod_dav.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule dav_lock_module modules/mod_dav_lock.so
#LoadModule dbd_module modules/mod_dbd.so
LoadModule deflate_module modules/mod_deflate.so
LoadModule dir_module modules/mod_dir.so
#LoadModule disk_cache_module modules/mod_disk_cache.so
#LoadModule dumpio_module modules/mod_dumpio.so
LoadModule env_module modules/mod_env.so
#LoadModule expires_module modules/mod_expires.so
#LoadModule ext_filter_module modules/mod_ext_filter.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule filter_module modules/mod_filter.so
LoadModule headers_module modules/mod_headers.so
#LoadModule ident_module modules/mod_ident.so
#LoadModule imagemap_module modules/mod_imagemap.so
LoadModule include_module modules/mod_include.so
#LoadModule info_module modules/mod_info.so
LoadModule isapi_module modules/mod_isapi.so
#LoadModule ldap_module modules/mod_ldap.so
#LoadModule logio_module modules/mod_logio.so
LoadModule log_config_module modules/mod_log_config.so
#LoadModule log_forensic_module modules/mod_log_forensic.so
#LoadModule mem_cache_module modules/mod_mem_cache.so
LoadModule mime_module modules/mod_mime.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
#LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
#LoadModule reqtimeout_module modules/mod_reqtimeout.so
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule setenvif_module modules/mod_setenvif.so
#LoadModule speling_module modules/mod_speling.so
LoadModule ssl_module modules/mod_ssl.so
#LoadModule status_module modules/mod_status.so
#LoadModule substitute_module modules/mod_substitute.so
#LoadModule unique_id_module modules/mod_unique_id.so
#LoadModule userdir_module modules/mod_userdir.so
#LoadModule usertrack_module modules/mod_usertrack.so
LoadModule version_module modules/mod_version.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so<IfModule !mpm_netware_module>
<IfModule !mpm_winnt_module>
#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.  
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User daemon
Group daemon

</IfModule>
</IfModule>

# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition.  These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed.  This address appears on some server-generated pages, such
# as error documents.  e.g. admin@your-domain.com
#
ServerAdmin webmaster@beckwithelectric.com

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
ServerName bell.beckwithelectric.inc:80

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "C:/BitNami/redmine-2.3.0-0/apache2/htdocs"

#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories). 
#
# First, we configure the "default" to be a very restrictive set of 
# features.  
#
<Directory />
    Options FollowSymLinks
    AllowOverride None
    Order deny,allow
    Deny from all
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "C:/BitNami/redmine-2.3.0-0/apache2/htdocs">
    #
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    #
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    #
    # The Options directive is both complicated and important.  Please see
    # http://httpd.apache.org/docs/2.2/mod/core.html#options
    # for more information.
    #
    Options Indexes FollowSymLinks

    #
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   Options FileInfo AuthConfig Limit
    #
    AllowOverride None

    #
    # Controls who can get stuff from this server.
    #
    Order allow,deny
    Allow from all

</Directory>

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
    DirectoryIndex index.html index.php
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being 
# viewed by Web clients. 
#
<FilesMatch "^\\.ht">
    Order allow,deny
    Deny from all
    Satisfy All
</FilesMatch>

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog "logs/error.log"

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

<IfModule log_config_module>
    #
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    #
    LogFormat "%h %l %u %t \\"%r\\" %>s %b \\"%{Referer}i\\" \\"%{User-Agent}i\\"" combined
    LogFormat "%h %l %u %t \\"%r\\" %>s %b" common

    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \\"%r\\" %>s %b \\"%{Referer}i\\" \\"%{User-Agent}i\\" %I %O" combinedio
    </IfModule>

    #
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here.  Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    #
    CustomLog "logs/access.log" common

    #
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #
    #CustomLog "logs/access.log" combined
</IfModule>

<IfModule alias_module>
    #
    # Redirect: Allows you to tell clients about documents that used to 
    # exist in your server's namespace, but do not anymore. The client 
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar

    #
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    #
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL.  You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.

    #
    # ScriptAlias: This controls which directories contain server scripts. 
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client.  The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    #
    ScriptAlias /cgi-bin/ "C:/BitNami/redmine-2.3.0-0/apache2/cgi-bin/"

</IfModule>

<IfModule cgid_module>
    #
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #
    #Scriptsock logs/cgisock
</IfModule>

#
# "C:/BitNami/redmine-2.3.0-0/apache2/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "C:/BitNami/redmine-2.3.0-0/apache2/cgi-bin">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
</Directory>

#
# DefaultType: the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value.  If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain

<IfModule mime_module>
    #
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    #
    TypesConfig conf/mime.types

    #
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #
    #AddType application/x-gzip .tgz
    #
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    #
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    #
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz

    #
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    #
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #
    #AddHandler cgi-script .cgi

    # For type maps (negotiated resources):
    #AddHandler type-map var

    #
    # Filters allow you to process content before it is sent to the client.
    #
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml
</IfModule>

#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type.  The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
#MIMEMagicFile conf/magic

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#

#
# MaxRanges: Maximum number of Ranges in a request before
# returning the entire resource, or one of the special
# values 'default', 'none' or 'unlimited'.
# Default setting is to accept 200 Ranges.
#MaxRanges unlimited

#
# EnableMMAP and EnableSendfile: On systems that support it, 
# memory-mapping or the sendfile syscall is used to deliver
# files.  This usually improves server performance, but must
# be turned off when serving from networked-mounted 
# filesystems or if support for these functions is otherwise
# broken on your system.
#
#EnableMMAP off
#EnableSendfile off

# Supplemental configuration
#
# The configuration files in the conf/extra/ directory can be 
# included to add extra features or to modify the default configuration of 
# the server, or you may simply copy their contents here and change as 
# necessary.

# Server-pool management (MPM specific)
#Include conf/extra/httpd-mpm.conf

# Multi-language error messages
#Include conf/extra/httpd-multilang-errordoc.conf

# Fancy directory listings
#Include conf/extra/httpd-autoindex.conf

# Language settings
#Include conf/extra/httpd-languages.conf

# User home directories
#Include conf/extra/httpd-userdir.conf

# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf

# Virtual hosts
#Include conf/extra/httpd-vhosts.conf

# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf

# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf

# Various default settings
#Include conf/extra/httpd-default.conf

# Secure (SSL/TLS) connections
Include conf/extra/httpd-ssl.conf

# Note: The following must must be present to support
#       starting without SSL on platforms with no /dev/random equivalent
#       but a statically compiled-in mod_ssl.
#
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>

# Security 
ServerSignature Off
ServerTokens Prod

Include "C:\\BitNami\\redmine-2.3.0-0/apache2/conf/ssi.conf"

LoadFile "C:/BitNami/REDMIN~1.0-0/php/libpq.dll"
LoadModule php5_module "C:/BitNami/REDMIN~1.0-0/php/php5apache2_2.dll"
AddType application/x-httpd-php .php
PHPIniDir "C:/BitNami/redmine-2.3.0-0/php"

Include "C:/BitNami/redmine-2.3.0-0/apache2/conf/fastcgi.conf"
Include "C:/BitNami/redmine-2.3.0-0/apps/phpmyadmin/conf/phpmyadmin.conf"
Include "C:/BitNami/redmine-2.3.0-0/apps/redmine/conf/redmine.conf"

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
httpd-ssl.conf
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
# This is the Apache server configuration file providing SSL support.
# It contains the configuration directives to instruct the server how to
# serve pages over an https connection. For detailing information about these 
# directives see <URL:http://httpd.apache.org/docs/2.2/mod/mod_ssl.html>
# 
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.  
#

#
# Pseudo Random Number Generator (PRNG):
# Configure one or more sources to seed the PRNG of the SSL library.
# The seed data should be of good random quality.
# WARNING! On some platforms /dev/random blocks if not enough entropy
# is available. This means you then cannot use the /dev/random device
# because it would lead to very long connection times (as long as
# it requires to make more entropy available). But usually those
# platforms additionally provide a /dev/urandom device which doesn't
# block. So, if available, use this one instead. Read the mod_ssl User
# Manual for more details.
#
#SSLRandomSeed startup file:/dev/random  512
#SSLRandomSeed startup file:/dev/urandom 512
#SSLRandomSeed connect file:/dev/random  512
#SSLRandomSeed connect file:/dev/urandom 512

#
# When we also provide SSL we have to listen to the 
# standard HTTP port (see above) and to the HTTPS port
#
# Note: Configurations that use IPv6 but not IPv4-mapped addresses need two
#       Listen directives: "Listen [::]:443" and "Listen 0.0.0.0:443"
#
Listen 443

##
##  SSL Global Context
##
##  All SSL configuration in this context applies both to
##  the main server and all SSL-enabled virtual hosts.
##

#
#   Some MIME-types for downloading Certificates and CRLs
#
AddType application/x-x509-ca-cert .crt
AddType application/x-pkcs7-crl    .crl

#   Pass Phrase Dialog:
#   Configure the pass phrase gathering process.
#   The filtering dialog program (`builtin' is a internal
#   terminal dialog) has to provide the pass phrase on stdout.
SSLPassPhraseDialog  builtin

#   Inter-Process Session Cache:
#   Configure the SSL Session Cache: First the mechanism 
#   to use and second the expiring timeout (in seconds).
#SSLSessionCache         "dbm:C:/BitNami/redmine-2.3.0-0/apache2/logs/ssl_scache"
SSLSessionCache        "shmcb:C:/BitNami/redmine-2.3.0-0/apache2/logs/ssl_scache(512000)"
SSLSessionCacheTimeout  300

#   Semaphore:
#   Configure the path to the mutual exclusion semaphore the
#   SSL engine uses internally for inter-process synchronization. 
SSLMutex default

##
## SSL Virtual Host Context
##

<VirtualHost _default_:443>

#   General setup for the virtual host
DocumentRoot "C:/BitNami/redmine-2.3.0-0/apache2/htdocs"
ServerName Bell.BeckwithElectric.inc:443
ServerAdmin webmaster@beckwithelectric.com
ErrorLog "C:/BitNami/redmine-2.3.0-0/apache2/logs/error.log"
TransferLog "C:/BitNami/redmine-2.3.0-0/apache2/logs/access.log"

#   SSL Engine Switch:
#   Enable/Disable SSL for this virtual host.
SSLEngine on

#   SSL Protocol support:
#   List the protocol versions which clients are allowed to
#   connect with. Disable SSLv2 by default (cf. RFC 6176).
SSLProtocol all -SSLv2

#   SSL Cipher Suite:
#   List the ciphers that the client is permitted to negotiate.
#   See the mod_ssl documentation for a complete list.
SSLCipherSuite HIGH:MEDIUM:!aNULL:!MD5

#   Speed-optimized SSL Cipher configuration:
#   If speed is your main concern (on busy HTTPS servers e.g.),
#   you might want to force clients to specific, performance
#   optimized ciphers. In this case, prepend those ciphers
#   to the SSLCipherSuite list, and enable SSLHonorCipherOrder.
#   Caveat: by giving precedence to RC4-SHA and AES128-SHA
#   (as in the example below), most connections will no longer
#   have perfect forward secrecy - if the server's key is
#   compromised, captures of past or future traffic must be
#   considered compromised, too.
#SSLCipherSuite RC4-SHA:AES128-SHA:HIGH:MEDIUM:!aNULL:!MD5
#SSLHonorCipherOrder on

#   Server Certificate:
#   Point SSLCertificateFile at a PEM encoded certificate.  If
#   the certificate is encrypted, then you will be prompted for a
#   pass phrase.  Note that a kill -HUP will prompt again.  Keep
#   in mind that if you have both an RSA and a DSA certificate you
#   can configure both in parallel (to also allow the use of DSA
#   ciphers, etc.)
#SSLCertificateFile "C:/BitNami/redmine-2.3.0-0/apache2/conf/server-dsa.crt"
SSLCertificateFile "C:/BitNami/redmine-2.3.0-0/apache2/conf/server.crt"

#   Server Private Key:
#   If the key is not combined with the certificate, use this
#   directive to point at the key file.  Keep in mind that if
#   you've both a RSA and a DSA private key you can configure
#   both in parallel (to also allow the use of DSA ciphers, etc.)
#SSLCertificateKeyFile "C:/BitNami/redmine-2.3.0-0/apache2/conf/server-dsa.key"
SSLCertificateKeyFile "C:/BitNami/redmine-2.3.0-0/apache2/conf/server.key"

#   Server Certificate Chain:
#   Point SSLCertificateChainFile at a file containing the
#   concatenation of PEM encoded CA certificates which form the
#   certificate chain for the server certificate. Alternatively
#   the referenced file can be the same as SSLCertificateFile
#   when the CA certificates are directly appended to the server
#   certificate for convinience.
#SSLCertificateChainFile "C:/BitNami/redmine-2.3.0-0/apache2/conf/server-ca.crt"
SSLCertificateChainFile "C:/BitNami/redmine-2.3.0-0/apache2/conf/gd_bundle.crt"

#   Certificate Authority (CA):
#   Set the CA certificate verification path where to find CA
#   certificates for client authentication or alternatively one
#   huge file containing all of them (file must be PEM encoded)
#   Note: Inside SSLCACertificatePath you need hash symlinks
#         to point to the certificate files. Use the provided
#         Makefile to update the hash symlinks after changes.
#SSLCACertificatePath "C:/BitNami/redmine-2.3.0-0/apache2/conf/ssl.crt"
#SSLCACertificateFile "C:/BitNami/redmine-2.3.0-0/apache2/conf/ssl.crt/ca-bundle.crt"
SSLCACertificatePath "C:/BitNami/redmine-2.3.0-0/apache2/conf"
SSLCACertificateFile "C:/BitNami/redmine-2.3.0-0/apache2/conf/gd_bundle.crt"

#   Certificate Revocation Lists (CRL):
#   Set the CA revocation path where to find CA CRLs for client
#   authentication or alternatively one huge file containing all
#   of them (file must be PEM encoded)
#   Note: Inside SSLCARevocationPath you need hash symlinks
#         to point to the certificate files. Use the provided
#         Makefile to update the hash symlinks after changes.
#SSLCARevocationPath "C:/BitNami/redmine-2.3.0-0/apache2/conf/ssl.crl"
#SSLCARevocationFile "C:/BitNami/redmine-2.3.0-0/apache2/conf/ssl.crl/ca-bundle.crl"

#   Client Authentication (Type):
#   Client certificate verification type and depth.  Types are
#   none, optional, require and optional_no_ca.  Depth is a
#   number which specifies how deeply to verify the certificate
#   issuer chain before deciding the certificate is not valid.
#SSLVerifyClient require
#SSLVerifyDepth  10

#   Access Control:
#   With SSLRequire you can do per-directory access control based
#   on arbitrary complex boolean expressions containing server
#   variable checks and other lookup directives.  The syntax is a
#   mixture between C and Perl.  See the mod_ssl documentation
#   for more details.
#<Location />
#SSLRequire (    %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \\
#            and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \\
#            and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \\
#            and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \\
#            and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20       ) \\
#           or %{REMOTE_ADDR} =~ m/^192\\.76\\.162\\.[0-9]+$/
#</Location>

#   SSL Engine Options:
#   Set various options for the SSL engine.
#   o FakeBasicAuth:
#     Translate the client X.509 into a Basic Authorisation.  This means that
#     the standard Auth/DBMAuth methods can be used for access control.  The
#     user name is the `one line' version of the client's X.509 certificate.
#     Note that no password is obtained from the user. Every entry in the user
#     file needs this password: `xxj31ZMTZzkVA'.
#   o ExportCertData:
#     This exports two additional environment variables: SSL_CLIENT_CERT and
#     SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
#     server (always existing) and the client (only existing when client
#     authentication is used). This can be used to import the certificates
#     into CGI scripts.
#   o StdEnvVars:
#     This exports the standard SSL/TLS related `SSL_*' environment variables.
#     Per default this exportation is switched off for performance reasons,
#     because the extraction step is an expensive operation and is usually
#     useless for serving static content. So one usually enables the
#     exportation for CGI and SSI requests only.
#   o StrictRequire:
#     This denies access when "SSLRequireSSL" or "SSLRequire" applied even
#     under a "Satisfy any" situation, i.e. when it applies access is denied
#     and no other module can change it.
#   o OptRenegotiate:
#     This enables optimized SSL connection renegotiation handling when SSL
#     directives are used in per-directory context. 
#SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
<FilesMatch "\\.(cgi|shtml|phtml|php)$">
    SSLOptions +StdEnvVars
</FilesMatch>
<Directory "C:/BitNami/redmine-2.3.0-0/apache2/cgi-bin">
    SSLOptions +StdEnvVars
</Directory>

#   SSL Protocol Adjustments:
#   The safe and default but still SSL/TLS standard compliant shutdown
#   approach is that mod_ssl sends the close notify alert but doesn't wait for
#   the close notify alert from client. When you need a different shutdown
#   approach you can use one of the following variables:
#   o ssl-unclean-shutdown:
#     This forces an unclean shutdown when the connection is closed, i.e. no
#     SSL close notify alert is send or allowed to received.  This violates
#     the SSL/TLS standard but is needed for some brain-dead browsers. Use
#     this when you receive I/O errors because of the standard approach where
#     mod_ssl sends the close notify alert.
#   o ssl-accurate-shutdown:
#     This forces an accurate shutdown when the connection is closed, i.e. a
#     SSL close notify alert is send and mod_ssl waits for the close notify
#     alert of the client. This is 100% SSL/TLS standard compliant, but in
#     practice often causes hanging connections with brain-dead browsers. Use
#     this only for browsers where you know that their SSL implementation
#     works correctly. 
#   Notice: Most problems of broken clients are also related to the HTTP
#   keep-alive facility, so you usually additionally want to disable
#   keep-alive for those clients, too. Use variable "nokeepalive" for this.
#   Similarly, one has to force some clients to use HTTP/1.0 to workaround
#   their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
#   "force-response-1.0" for this.
BrowserMatch "MSIE [2-5]" \\
         nokeepalive ssl-unclean-shutdown \\
         downgrade-1.0 force-response-1.0

#   Per-Server Logging:
#   The home of a custom SSL log file. Use this when you want a
#   compact non-error SSL logfile on a virtual host basis.
CustomLog "C:/BitNami/redmine-2.3.0-0/apache2/logs/ssl_request.log" \\
          "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \\"%r\\" %b"

</VirtualHost>

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

I'm installed latest gitlab with bitnami. but i cant push my updates to central repo. It always asking for git password. I'm installed it in a local server and given the domain name as a local IP. The public keys are updated in /hom/git/.ssh/authorised_keys list. but it asks for git user password. Please help me .

In recent weeks, I am using XAMPP 1.8.1 for installation of different applications on localhost for testing and training. The overall configuarion of XAMPP is satisfied.

However, when I installed OpenScholar in it, although the whole installation is completed, I received a lot of warning message about .inc files.

How can I remove them? Should I be required to remove some types of files (which is asked in the final stage of installation of other applications)? If so, how and which should I remove?

Please let me know your professional advices.

P.S. Maybe, it is called "clean up", either automatic or manual.

Hello,

Is there a special procedure to get PyLucene and JCC installed to work with the BitNami ReviewBoard stack? (a guide similar to http://answers.bitnami.com/questions/1504/cant-import-ldap-in-python-onbitnami-djangostack-ubuntu for ldap?)

Thank you.

• Daniel

My AWS WP:MU installation redirects to the " Congratulations " page

on HTTPS but not on HTTP

How do I fix it?

ps.

Sorry had way too much fun with that bold button.