Author: dq

Hudson on Ubuntu as Service

On Debian-based distributions, such as Ubuntu, you can install Hudson through apt-get.

Recent versions are available in http://hudson-ci.org/downloads/debian/

Installation
$ sudo sh -c "echo 'deb http://hudson-ci.org/debian binary/' > /etc/apt/sources.list.d/hudson.list"
$ sudo apt-get update
$ sudo apt-get install hudson

Upgrade


$ sudo apt-get update
$ sudo apt-get safe-upgrade


What does this package do?


Hudson will be launched as a daemon up on start. See /etc/init.d/hudson for more details.
The 'hudson' user is created to run this service.
Log file will be placed in /var/log/hudson/hudson.log. Check this file if you are troubleshooting Hudson.
/etc/default/hudson will capture configuration parameters for the launch.

Where to go from here?


Try Hudson locally : http://localhost:8080 and install whatever plugins and more you need.
You might want to make Hudson visible through Apache, to make it available on port 80 (for example, http://myserver/hudson/ instead of http://myserver:8080/). See this blog for more details

Apache HTTPD, Hudson and Tomcat

Hudson Prefix

We want to see hudson running on servername/hudson/. The first step is to change the prefix hudson uses, so we get from servername:8080/ to servername:8080/hudson/. To do that pico /etc/default/hudson, add

–prefix=/hudson to below line.

HUDSON_ARGS="–webroot=/var/run/hudson/war –httpPort=$HTTP_PORT –ajp13Port=$AJP_PORT –prefix=/hudson"

sudo /etc/init.d/hudson force-reload

apt-get install apache2

apt-get install libapache2-mod-proxy-html

a2enmod proxy

a2enmod proxy_http

By default it is configured to deny all proxying, so edit /etc/apache2/mods-enabled/proxy.conf to allow proxying:

ProxyRequests Off
<Proxy *>
Order deny,allow
Allow from all
</Proxy>

In your /etc/apache2/sites-enabled/ directory there should be some file like 000-default or similar, with settings for the site. Add proxy configurations in it for mapping the /hudson path on the website to localhost:8080/hudson:

pico /etc/apache2/sites-enabled/000-default

and add below:


###ProxyPass /hudson http://http:8080/hudson

ProxyPass /hudson http://127.0.0.1:8080/hudson
ProxyPassReverse /hudson http://127.0.0.1:8080/hudson
ProxyRequests Off
# Local reverse proxy authorization override
# Most unix distribution deny proxy by default (ie /etc/apache2/mods-enabled/proxy.conf in Ubuntu)
<Proxy http://127.0.0.1:8080/hudson*>
Order deny,allow
Allow from all
</Proxy>

Restart Apache2

/etc/init.d/apache2 force-reload

=====================================

IGNORE BELOW

=====================================

In situations where you have existing web sites on your server, you may find it useful to run Hudson (or the servlet container that Hudson runs in) behind Apache, so that you can bind Hudson to the part of a bigger website that you may have. This document discusses some of the approaches for doing this.

Make sure that you change the Hudson httpListenAddress from its default of 0.0.0.0 to 127.0.0.1 or any Apache-level restrictions can be easily bypassed by hitting the Hudson port directly.

mod_proxy

mod_proxy works by making Apache perform "reverse proxy" — when a request arrives for certain URLs, Apache becomes a proxy and further forward that request to Hudson, then it forwards the response back to the client.

The following Apache modules must be installed : 

a2enmod proxya2enmod proxy_http

A typical set up for mod_proxy would look like this: 

ProxyPass         /hudson  http://localhost:8081/hudsonProxyPassReverse  /hudson  http://localhost:8081/hudsonProxyRequests     Off# Local reverse proxy authorization override# Most unix distribution deny proxy by default (ie /etc/apache2/mods-enabled/proxy.conf in Ubuntu)<Proxy http://localhost:8081/hudson*>Order deny,allowAllow from all</Proxy>

This assumes that you run Hudson on port 8081.

For this set up to work, the context path of Hudson must be the same between your Apache and Hudson (that is, you can't run Hudson on http://localhost:8081/ci and have it exposed at http://localhost:80/hudson).

Set the context path in Windows by modifying the hudson.xml configuration file and adding –prefix=/hudson (or similar) to the <arguments> entry.

The ProxyRequests Off prevents Apache from functioning as a forward proxy server (except for ProxyPass), it is advised to include it unless the server should function as a proxy.

If you are running Apache on a Security-Enhanced Linux (SE-Linux) machine it is essential to make SE-Linux do the right thing by issuing as root 
																					setsebool -P httpd_can_network_connect true

If this is not issued Apache will not be allowed to forward proxy requests to Hudson and only an error message will be displayed.

Because hudson already compress its output, you can not use the normal proxy-html filter to modify urls: 
																					SetOutputFilter proxy-html

Instead you can use the following: 

																					SetOutputFilter INFLATE;proxy-html;DEFLATE			ProxyHTMLURLMap http://your_server:8080/hudson /hudson

http://wiki.uniformserver.com/index.php/Reverse_Proxy_Server_2:_mod_proxy_html_2
But since hudson seems to be well behaved it even better to just not use SetOutputFilter and ProxyHTMLURLMap.

If there are problems with hudson sometimes servicing random garbage pages, then the following may help: 
																					SetEnv proxy-nokeepalive 1

mod_proxy with HTTPS

If you'd like to run Hudson with reverse proxy in HTTPS, one user reported that HTTPS needs to be terminated at Hudson, not at the front-end Apache. See this e-mail thread for more discussion.

Alternatively, you can add an additional ProxyPassReverse directive to redirect non-SSL URLs generated by Hudson to the SSL side. Assuming that your webserver is your.host.com, placing the following within the SSL virtual host definition will do the trick: 

ProxyRequests     OffProxyPreserveHost On<Proxy http://localhost:8081/hudson*>Order deny,allowAllow from all</Proxy>ProxyPass         /hudson  http://localhost:8081/hudsonProxyPassReverse  /hudson  http://localhost:8081/hudsonProxyPassReverse  /hudson  http://your.host.com/hudson

Yet another option is to rewrite the Location headers that contain non-ssl URL's generated by Hudson. If you want to access hudson from https://www.example.com/hudson, placing the following within the SSL virtual host definition also works: 

ProxyRequests     OffProxyPreserveHost OnProxyPass /hudson/ http://localhost:8081/hudson/<Location /hudson/>ProxyPassReverse /Order deny,allowAllow from all</Location>Header edit Location ^http://www.example.com/hudson/ https://www.example.com/hudson/

mod_ajp/mod_proxy_ajp

More info welcome. Probably we should move the contents from here

I wanted to have Hudson running in a different workspace than my normal Tomcat server, but both available via the Apache web server. So, first up, modify Hudson to use a different web and ajp port than Tomcat: 

HTTP_PORT=9080AJP_PORT=9009...nohup java -jar "$WAR" --httpPort=$HTTP_PORT --ajp13Port=$AJP_PORT --prefix=/hudson >> "$LOG" 2>&1 &

Then setup Apache so that it knows that the prefix /hudson is being served by AJP in the httpd.conf file: 

LoadModule jk_module          libexec/httpd/mod_jk.soAddModule     mod_jk.c#== AJP hooks ==JkWorkersFile /etc/httpd/workers.propertiesJkLogFile     /private/var/log/httpd/mod_jk.logJkLogLevel    infoJkLogStampFormat "[%a %b %d %H:%M:%S %Y] "JkOptions     +ForwardKeySize +ForwardURICompat -ForwardDirectoriesJkRequestLogFormat     "%w %V %T"# Here are 3 sample applications - 2 that are being served by Tomcat, and HudsonJkMount  /friki/* worker1JkMount  /pebble/* worker1JkMount  /hudson/* worker2

Then finally the workers.conf file specified above, that just tells AJP which port to use for which web application: 

# Define 2 real workers using ajp13worker.list=worker1,worker2# Set properties for worker1 (ajp13)worker.worker1.type=ajp13worker.worker1.host=localhostworker.worker1.port=8009worker.worker1.lbfactor=50worker.worker1.cachesize=10worker.worker1.cache_timeout=600worker.worker1.socket_keepalive=1# Set properties for worker2 (ajp13)worker.worker2.type=ajp13worker.worker2.host=localhostworker.worker2.port=9009worker.worker2.lbfactor=50worker.worker2.cachesize=10worker.worker2.cache_timeout=600worker.worker2.socket_keepalive=1worker.worker2.recycle_timeout=300

mod_rewrite

Some people attempted to use mod_rewrite to do this, but this will never work if you do not add a ProxyPassReverse.
See the thread if you'd like to know why.

The following Apache modules must be installed : 

a2enmod rewritea2enmod proxya2enmod proxy_http

A typical set up for mod_rewrite would look like this: 

# Use last flag because no more rewrite can be applied after proxy passRewriteRule       ^/hudson(.*)$  http://localhost:8081/hudson$1 [P,L]ProxyPassReverse  /hudson        http://localhost:8081/hudsonProxyRequests     Off# Local reverse proxy authorization override# Most unix distribution deny proxy by default (ie /etc/apache2/mods-enabled/proxy.conf in Ubuntu)<Proxy http://localhost:8081/hudson*>Order deny,allowAllow from all</Proxy>

This assumes that you run Hudson on port 8081. For this set up to work, the context path of Hudson must be the same between your Apache and Hudson (that is, you can't run Hudson on http://localhost:8081/ci and have it exposed at http://localhost:80/hudson)

The ProxyRequests Off prevents Apache from functioning as a forward proxy server (except for ProxyPass), it is advised to include it unless the server should function as a proxy.

======================

http://community.webfaction.com/questions/4081/how-do-i-restart-apache-so-that-htaccess-is-reread-on-a-static-with-htaccess-app 

RewriteEngine onRewriteCond %{REQUEST_URI} !^/Concentration/RewriteRule ^(.*)$ /Concentration/$1 [P,L]

Remote desktop

This is only need for Ubuntu Desktop, it will not work for server.

Info via: http://www.makeuseof.com/tag/how-to-establish-simple-remote-desktop-access-between-ubuntu-and-windows/

Adept Ubuntu users would already be thinking about the System > Preferences > Remote Desktop menu entry. Of course we will use that. However, it lets you configure your computer to allow/disallow remote desktop access. It doesn’t let you connect to a remote computer. Extra software is required for that, which we will look at now.

Allow Remote Desktop Connections

First off, you would need to enable remote desktop on the Linux computer that you want to access via remote desktop. Doing so is easy by using the System > Preferences > Remote Desktop option. In the dialog that shows up – check “Allow other users to view your desktop”. You can also configure additional options like requiring password for remote access and notification icons. It is advisable to use a password for remote access, so that only trusted users may be able to establish a connection.

With all that set up, its time to connect to it from another computer. Three possible scenarios arise: you can connect using another Linux machine, or you might want to connect using a Windows PC or MAC. All require slightly different approaches. Here’s how.

Connecting From Another Linux Machine

Ubuntu uses Virtual Networking Connections for remote desktop. Your best bet would be to use a VNC viewer to access the remote desktop. Use the command sudo apt-get install xvnc4viewer to install VNC viewer. Now all you have to do is to issue the sudo vncviewer <hostname/ip> command. You will be asked for a password (if it is configured on the remote machine) and you can then view and interact with the remote desktop.

Connect To Ubuntu From A Windows PC

If you would to connect from a Windows computer, you can use TightVNC, tvnjviewer-2.6.2-bin.zip (JAR) (647.50 kb) or uVNC (There is also a seemingly portable version available that would run off your USB drive without installing, however it stores entries in the registry). Specify the IP address and the port number (default is 5900 and is not required to be mentioned explicitly), specify bandwidth that is available to you, hit Connect and you can access the desktop of the remote machine easily.

Keep in mind that none of these clients support encryption and you have only established an unencrypted connection up until now. Teamviewer and LogMeIn encrypt the the data flow between the two computer. You can use a SSH tunnel to encrypt the flow of data. Here are the steps in brief:
  • You need OpenSSH. (sudo apt-get openssh-server).
  • Create the tunnel using ssh -L 5900:localhost:5900 <ip address>, where IP address is the address of the remote computer. If you are connecting using a Windows computer, you can use PuTTY to create a tunnel.
  • Establish the connection as before however, this time you need to connect to localhost at port 5900 (or whatever port you specified in the command above). VNC client will then utilize the tunnel you just created and traffic between the two endpoints will now be encrypted.

While this is a lot of work compared to the one-click solution offered by Teamviewer or LogMeIn, it is certainly more configurable and caters to a wide variety of needs. Moreover, you only need to do the configuration once and you can also establish a VNC connection with a headless server (with some more configuration though!).

Connect To Ubuntu From A MAC

Mac users can also use their favorite VNC client (like Chicken of the VNC) and you should be able to remotely access the desktop of the said Linux machine.

Samba Shares


Install Samba Server on Ubuntu

information via: http://www.howtogeek.com/howto/ubuntu/install-samba-server-on-ubuntu/

If you want to share files between your Ubuntu and Windows computers, your best option is to use Samba file sharing.

To install, first open a terminal window and enter the following command:

sudo apt-get install samba smbfs

We’ve got samba installed, but now we’ll need to configure it to make it accessible. Run the following command to open the configuration file, substituting your editor of choice:

sudo pico /etc/samba/smb.conf

Find this section in the file:

####### Authentication #######

# “security = user” is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba-HOWTO-Collection/ServerType.html
# in the samba-doc package for details.
; security = user

Uncomment the security line, and add another line to make it look like this:

security = user
username map = /etc/samba/smbusers

This will set Samba to use the smbusers file for looking up the user list.

Finallly, add these two lines to your smb.conf:

[global]

null passwords = yes
map to guest = Bad User

The first tells Samba that null passwords are OK. The second that non-recognized users (which is what any user who doesn't have an account on your Ubuntu box will be) should be silently mapped to Guest (nobody).

This allows a non-authenticated Windows box to list the shares advertised as browseable by Samba. When the user attempts to connect to a share, Samba evaluates their credentials (in this case, Guest), and either allows them access, or prompts for a new user name/password. You can also always prevent shares from being listed by marking them as browseable = no.

You do sacrifice a little security for this convienince: anyone with access to your Samba server can now list your browesable shares and connect to any share that allows guest access. Samba isn't designed to face the Internet so all the normal rules for not doing that still apply. See the much more extensive Samba HOWTO (http://ubuntuforums.org/showthread.php?t=202605) for Ubuntu for general setup.

Next make sure that nobody is enabled in Samba's backend:

  • $ sudo smbpasswd -n nobody
  • $ sudo smbpasswd -e nobody

The first command creates the nobody account with a null password. The second enables this account. See this bug report (https://bugs.launchpad.net/ubuntu/+source/samba/+bug/39717) for more information. It took me awhile to track that down, but if I knew what I was doing it might have been faster. 😉

System user must be created first

:information via: http://ubuntuforums.org/showthread.php?t=839414


$ sudo useradd USERNAME –shell /bin/false

This assumes you create the SHARES folder and it is not the normal Linux /home.

Here's what I do to create and authorize each user of the SAMBA shares:

In, for example, the /home directory… to add a user called "USERNAME":

  • $ cd /shares/users
  • $ sudo mkdir USERNAME
  • $ sudo useradd -d /shares/users/USERNAME -s /bin/false -r USERNAME
  • $ sudo passwd USERNAME (then enter new UNIX password twice)
  • $ sudo smbpasswd -a USERNAME (then enter new SMB password twice)
  • $ sudo chown USERNAME USERNAME
  • $ sudo chgrp USERNAME USERNAME

Repeat for each user you wish to add to SAMBA.


System nobody must be enabled:


information via: http://ubuntuforums.org/archive/index.php/t-490168.html
For your shares that you want public users to access. But it still doesn't work. Check your /etc/shadow file with sudo cat /etc/shadow to see if you have a nobody account. You should.

Create a Samba User

There are two steps to creating a user. First we’ll run the smbpasswd utility to create a samba password for the user.

sudo smbpasswd -a <username> Completed above

Next, we’ll add that username to the smbusers file.

sudo gedit /etc/samba/smbusers

Add in the following line, substituting the username with the one you want to give access to. The format is <ubuntuusername> = “<samba username>”. You can use a different samba user name to map to an ubuntu account, but that’s not really necessary right now.

<username> = “<username>”

Now you can create samba shares and give access to the users that you listed here.

You may want the graphical version (don't know how it works yet)

Installing Samba Server confiuration tool:information via:http://www.unixmen.com/linux-tutorials/1060-how-to-configure-samba-using-a-graphical-interface-in-ubuntu

If on desktop Ubuntu or wish to have web interface


Now install the graphical interface System-config samba ( part may already be installed)


sudo apt-get install samba samba-common

sudo apt-get install system-config-samba

SWAT:From the application screen, install swat, Sambe Web Admin Tool (not a hugh, help but does with validation)
Access via: http://localhost:901/
Share Ubuntu Home Directories using Sambainformation via: http://www.howtogeek.com/howto/ubuntu/share-ubuntu-home-directories-using-samba/
Samba Server allows you to share the home directories of users automatically. This can be useful so that you don’t have to manually create every share for every user.

First, make sure that you’ve installed Samba server.

Share directories

To share the home directories, open up smb.conf with the following command:

sudo gedit /etc/samba/smb.conf

uncomment lines refering to CDROM

sudo gedit /etc/fstab
/dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0


Find this section of the file, and make it match the following:

Share Definitions

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user’s home directory as \\server\username
[homes]
comment = Home Directories
browseable = yes

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server. Un-comment the following parameter
# to make sure that only “username” can connect to \\server\username
valid users = %S

# By default, the home directories are exported read-only. Change next
# parameter to ‘yes’ if you want to be able to write to them.
writable = yes

Always remember to test:

$ sudo pico /etc/samba/smb.conf
$ testparm
Restart:

$ sudo restart smbd
$ sudo restart nmbd


Validate:Check to see if the shares are present:

apt-get install smbclient

smbclient -L localhost


Now you should be able to map a drive on windows using the following share format:

\\ubuntumachine\username

For example, if the Ubuntu machine is named ubuntuserv, and the username is geek, your share path would be \\ubuntuserv\geek


Samba documentation:http://us5.samba.org/samba/docs/man/manpages-3/smb.conf.5.html
Directory/File Mask
http://www.cyberciti.biz/tips/understanding-linux-unix-umask-value-usage.html
Create shares:Shares should be in the /srv directory structure:
/srv/share/public
# A publicly accessible directory, that can be read from

browseable = Yes
[public-read]
comment = Guest access share
path = /srv/shares/public
read only = yes
locking = yes
guest ok = yes
public = Yes
available = yes
writable = no
browseable = Yes
;[public]
; comment = %h Shared Public Directory
; path = /srv/shares/public
; force directory mode = 0777
; force create mode = 0777
; force group = nobody
; force user = nobody
; public = yes
; writeable = yes
; read only = no

(0) cd /srv
(1) sudo mkdir shares
(2) sudo chown -R nobody.nogroup /srv/shares
(3.1)
or (3.2) sudo chmod -R 0777 /srv/shares
(4) sudo mkdir public
(5) ls -l (to validate)

Un-install

if things go bad: $ sudo apt-get –purge remove smbfs
$ sudo apt-get –purge remove samba
–purge deletes all files not just the app.
also remove SWAT
SAMBA
https://bbs.archlinux.org/viewto[pic.php?id=45423

http://www.howtogeek.com/howto/ubuntu/share-ubuntu-home-directories-using-samba/
http://www.ubuntugeek.com/howto-setup-samba-server-with-tdbsam-backend.html
My /etc/samba/smb.conf file for reference:smb.conf (15.22 kb)

fstab (774.00 bytes)

smb.conf.save.zip (14.99 kb)

[A_KYC_PROD]
comment = KYC PROD SAMBA
browseable = yes
writable = yes
path = /data/samba/kyc
guest ok = no
vfs objects = full_audit
full_audit:failure = none
full_audit:success = mkdir rename unlink rmdir open pwrite
full_audit:prefix = %u|%I|%m|%S
full_audit:facility = LOCAL7
full_audit:priority = NOTICE

Maven setup

Copied from: http://maven.apache.org/download.html#Installation

Installation Instructions

Maven is a Java tool, so you must have Java installed in order to proceed. More precisely, you need a Java Development Kit (JDK), the Java Runtime Environment (JRE) is not sufficient.

Additional optional installation steps are listed after the platform specific instructions.

Windows 2000/XP

  1. Unzip the distribution archive, i.e. apache-maven-3.1.0-bin.zip (5.92 mb) to the directory you wish to install Maven 3.0.1. These instructions assume you chose C:\Program Files\Apache Software Foundation. The subdirectory apache-maven-3.0.1 will be created from the archive.
  2. Add the M2_HOME environment variable by opening up the system properties (WinKey + Pause), selecting the "Advanced" tab, and the "Environment Variables" button, then adding the M2_HOME variable in the user variables with the value C:\Program Files\Apache Software Foundation\apache-maven-3.0.1. Be sure to omit any quotation marks around the path even if it contains spaces. Note: For Maven < 2.0.9, also be sure that the M2_HOME doesn't have a '\' as last character.
  3. In the same dialog, add the M2 environment variable in the user variables with the value %M2_HOME%\bin.
  4. Optional: In the same dialog, add the MAVEN_OPTS environment variable in the user variables to specify JVM properties, e.g. the value -Xms256m -Xmx512m. This environment variable can be used to supply extra options to Maven.
  5. In the same dialog, update/create the Path environment variable in the user variables and prepend the value %M2% to add Maven available in the command line.
  6. In the same dialog, make sure that JAVA_HOME exists in your user variables or in the system variables and it is set to the location of your JDK, e.g. C:\Program Files\Java\jdk1.5.0_02 and that %JAVA_HOME%\bin is in your Path environment variable.
  7. Open a new command prompt (Winkey + R then type cmd) and run mvn –version to verify that it is correctly installed.

Unix-based Operating Systems (Linux, Solaris and Mac OS X)

  1. Extract the distribution archive, i.e. apache-maven-3.0.1-bin.tar.gz to the directory you wish to install Maven 3.0.1. These instructions assume you chose /usr/local/apache-maven. The subdirectory apache-maven-3.0.1 will be created from the archive.
  2. In a command terminal, add the M2_HOME environment variable, e.g. export M2_HOME=/usr/local/apache-maven/apache-maven-3.0.1.
  3. Add the M2 environment variable, e.g. export M2=$M2_HOME/bin.
  4. Optional: Add the MAVEN_OPTS environment variable to specify JVM properties, e.g. export MAVEN_OPTS="-Xms256m -Xmx512m". This environment variable can be used to supply extra options to Maven.
  5. Add M2 environment variable to your path, e.g. export PATH=$M2:$PATH.
  6. Make sure that JAVA_HOME is set to the location of your JDK, e.g. export JAVA_HOME=/usr/java/jdk1.5.0_02 and that $JAVA_HOME/bin is in your PATH environment variable.
  7. Run mvn –version to verify that it is correctly installed.

Optional configuration

Maven will work for most tasks with the above configuration, however if you have any environmental specific configuration outside of individual projects then you will need to configure settings. The following sections refer to what is available.

Settings

Maven has a settings file located in the Maven installation and/or user home directory that configure environmental specifics such as:

  • HTTP proxy server
  • repository manager location
  • server authentication and passwords
  • other configuration properties

For information on this file, see the Settings reference

Don't forget to run MVN MVN to init repo folder.

Sample here: settings.xml (1.76 kb)

Security

As of Maven 2.1.0+, you can encrypt passwords in your settings file, however you must first configure a master password. For more information on both server passwords and the master password, see the Guide to Password Encryption.

Toolchains

As of Maven 2.0.9+, you can build a project using a specific version of JDK independent from the one Maven is running with. For more information, see the Guide to Using Toolchains.

Sonar – Coding rules and Unit tests

Accomplish:

  • Installation
  • Duplication
  • TimeMachine
  • Configure Code Rules
  • Improve Unit tests

http://www.sonarsource.org/features/

http://docs.codehaus.org/display/SONAR/The+2+minutes+tutorial

http://www.sonarsource.org/downloads/

==============================================

cd /media/shares/sonar/

Currently using: sonar-3.3.1

OLD sonar-2.13.1

http://www.sonarsource.org/screencasts/installation-of-sonar/
$ wget http://dist.sonar.codehaus.org/sonar-x.x.x.zip
$ unzip sonar–x.x.x.zip
$ sonar–x.x.x.zip
$ cd conf
copy sonar.properties from old dir.
update ::: jdbc:mysql://localhost:3306/sonarxxx?useUnicode=true&characterEncoding=utf8
Manually create new empty DB schema on Q-Berry-WHS called::: sonarxxx
mysql> CREATE DATABASE sonarxxx CHARACTER SET utf8 COLLATE utf8_general_ci;
mysql> grant all privileges on sonarxxx.\* to 'sonar'@'localhost' identified by 't0ps3cr3t';
mysql> flush privileges;
$ cd /media/shares/sonar/sonar-3.3.1/bin/linux-x86-32
$ ./sonar.sh start
http://q-berry-whs:9000/
RENAME TABLE old_db.table TO new_db.table;

Tag Cloud