You can have problems updating Kloxo to version 6.1.10 (especially from 6.1.7) with using 'auto update' or 'update home' on kloxo.
short solution:
Run /script/cleanup
if this don't work try this:
# update your linux distribution
yum update
# shell command version for update kloxo
sh /script/upcp
# cleanup process kloxo settings
sh /script/cleanup
# restart some services
service xinetd restart
# Better reboot after that
reboot
Wednesday, December 7, 2011
Sunday, November 27, 2011
Startup Script Red5 working with ubuntu 11.x
You may wish have red5 started at boot.
This script should help you.
It is assumed that your red5 script is located at /usr/share/red5:
This script should help you.
It is assumed that your red5 script is located at /usr/share/red5:
cd /etc/init.d/ touch red5 chmod 755 red5 vi red5 Paste below code #! /bin/sh # /etc/init.d/red5 # # Check for missing file RED5_DIR=/usr/share/red5 test -x $RED5_DIR/red5.sh || exit 5 case "$1" in start) echo -n "Starting Red5 Service" echo -n " " cd $RED5_DIR su -s /bin/bash -c "$RED5_DIR/red5.sh &" red5 sleep 2 ;; stop) echo -n "Shutting down red5" echo -n " " su -s /bin/bash -c "killall -q -u red5 java" red5 sleep 2 ;; restart) ## Stop the service and regardless of whether it was ## running or not, start it again. $0 stop $0 start ;; esac then you maybe need useradd red5 and use like service red5 start service red5 stop service red5 restart
Tuesday, November 22, 2011
Drupal - smtp with gmail
To use Gmail App with Drupal, use the SMTP Authentication Support module. Install a version of this module that is compatible with your version of Drupal.
Open your modules page, find the SMTP module, and configure it with the following settings:
- SMTP Server – smtp.gmail.com
- SMTP Port – 465
- Use Encrypted Protocal - Yes, Use-ssl
- Username – gmail Email-address
- Password – gmail Password
Don't forget to turn the module on and send your first test-mail.
Wednesday, November 9, 2011
Creating a Virtual Host with Webmin
These instructions apply to Webmin version 1.570 and Ubuntu 10.04
- Create a folder where you wish to store your sites files.
- You can do this in the Others > File Manager section.
- In this example we use: /var/www/vhosts/domainname.com/http/
- Setup the vhost.
- Click on Servers > Apache Web Server in the left hand menu.
- Click the “create virtual host” tab.
- You can leave most settings as their default values, but you should fill out the following:
- Port: Generally, you’ll want to use port 80.
- Document Root: This is folder where you site’s files will be stored. Pick the folder you created in step 1.
- Server name: This is just your site’s domain name, e.g. domainname.com (leave out the www.)
- Click “Create Now”
- Add a server alias for www.domainname.com
- Click on the “Existing Virtual Hosts” tab in Servers > Apache Web Server.
- Click the virtual server you just created.
- Click on “Networking and Addresses”
- In the “Alternate Virtual Server Names” box, add any additional server aliases you want to use for this site, such as www.domainname.com
- Press “Save”.
- Click “Apply Changes” to get Webmin to restart Apache.
- vi /etc/apache2/sites-enabled/000-default and add: NameVirtualHost *
Monday, November 7, 2011
Stream your video files via CDN and play them with JW Player
Using AWS CloudFront as CDN
A Content Delivery Network (CDN) offers several advantages over a plain webserver for streaming video. For example, a CDN will be able to speedily deliver your videos across the country and globe, it will be able to stream your videos instead of a download and it will be able to scale to large numbers of videos and viewers.This 4 steps are required:
- Get an Amazon Web Services (AWS) Account
- Upload Your Content to S3
- Create a CloudFront Distribution
- Configure Your JW Player:
Tuesday, November 1, 2011
Add Google Analytics to your Kaltura Player
- enter the KMC
- click on the Studio tab.
- in the Studio, edit the player of your choice.
- enter the Features tab and reveal the Additional parameters and plugins section.
- copy and paste the following line into the "Paste your plug-in line here" text box and click the "go" button:
googleAnalytics.plugin=true&googleAnalytics.urchinCode=UA-yourgoogleanalyticscode&googleAnalytics.debugMode=false&googleAnalytics.path=http://cdnexchange.kaltura.com/sites/exchange.kaltura.com/files/applications/releases/Kalturian/16/googleAnalytics.swf&googleAnalytics.relativeTo=PlayerHolder&googleAnalytics.position=lastChild - change the googleAnalytics.debugMode parameter to true in order to get visual debugging information window over the player.
Sunday, October 23, 2011
How to generate an SSH key with Linux?
You can generate a SSH key in Linux using the ssh-keygen command. You should run it in the command line. You will be asked for a file in which the key should be saved to and for a passphrase (password) for the key:
user@localhost: ssh-keygen -t dsa
Generating public/private dsa key pair.
Enter file in which to save the key (/home/user/.ssh/id_dsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in id_dsa.
Your public key has been saved in id_dsa.pub.
The key fingerprint is:
16:8e:e8:f2:1d:c9:b9:cf:43:9a:b3:3c:c1:1f:95:93 user@localhost
Generating public/private dsa key pair.
Enter file in which to save the key (/home/user/.ssh/id_dsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in id_dsa.
Your public key has been saved in id_dsa.pub.
The key fingerprint is:
16:8e:e8:f2:1d:c9:b9:cf:43:9a:b3:3c:c1:1f:95:93 user@localhost
This will create a private key written to /home/user/.ssh/id_dsa and a public key written to/home/user/.ssh/id_dsa.pub. The passphrase is used to protect your key. You will be asked for it when you connect via SSH.
Tuesday, October 18, 2011
Alfresco 4 on amazon AWS
1. catch your ubuntu at:
http://alestic.com/
2. get alfresco quckstart package at:
http://code.google.com/p/alfresco-ubuntu-qs/
or 1 click installation when following this post:
http://blogs.alfresco.com/wp/wabson/2011/10/16/alfresco-4-0-in-amazon-ec2/
Thursday, October 6, 2011
No - the pagerank did not die today.
There are numberless complaints in the forums that the Google PageRank went missing in action and is no longer working.
The issue is not with Toolbar PageRank. Google appears to have disabled the display of PageRank on browser toolbars and online ranking checkers. It is causd by Google's lookup URL for the Pagerank. Toolbar plugins, such as SEOQuake and SEOBook, which had been displaying the Google PageRank for the site being viewed are now showing as either N/A or 0.
The issue is not with Toolbar PageRank. Google appears to have disabled the display of PageRank on browser toolbars and online ranking checkers. It is causd by Google's lookup URL for the Pagerank. Toolbar plugins, such as SEOQuake and SEOBook, which had been displaying the Google PageRank for the site being viewed are now showing as either N/A or 0.
Sunday, October 2, 2011
Move Typo3 to a new host.
To move your TYPO3 site from one host to another, you will need an FTP Client and access to an online database tool (such as phpMyAdmin). Begin the process by logging into your online account with your FTP Client. For this How To, we'll demo Firefox's FireFTP extension (which is free).
- First, using an FTP Client, such as FireFTP (shown), Connect to your current hosting account.
- Download to your local computer all the directories and files in the following directories:
/fileadmin
/t3lib
/typo3
/typo3conf
/typo3temp
/uploads
index.php
This download may take a good bit of time, even with a fast connection. - When the download is complete, open the /typo3conf on your local computer and delete all the files that begin with temp_
- Next, log in to the original hosting account and access your online database tool (generally, login to phpMyAdmin).
- When you've logged in,select your TYPO3 database from the dropdown menu on the left and then click the Export tab.
- Leave all the options at their default settings. Scroll to the bottom of the page and check the "Save as file" box and then click the Go button.
- Save the file to your local computer.
- If the File name field is blank, enter the name of your database here. Then press Go.
- When the database export is complete, log in to your new host's server with your FTP Client and upload all the TYPO3 directories and files (do not upload the .sql file that you exported in the previous step).
Again, this process will likely take some time, even with a fast connection. - When the files are all uploaded, you will need to change the permissions recursively for /fileadmin, /typo3conf, /typo3temp, /uploads, and index.php to chmod 777. (FlashFXP, Filezilla, and Firefox's FireFTP extension all include recursive features).
Click Read, Write, and Execute for Owner, Group, and Public groups. Then ensure All Contained Files and All Contained Folders are checked as well. - Click Okay and wait. Again, this isn't always a speedy process.
- Next, you will need to do some detective work to find out how to create a database, database user, and connect the two on your new server. Typically, the information can be found on your host's support pages.
Once a new database has been created and set up, use your online databae tool (phpMyAdmin) to import the database you've saved on your local computer. (Save the User Login and Password for later.) - Click the Import tab.
- Click Browse to find your saved .sql database file on your local computer. Select it and then scroll to the bottom of this page and click the Go button.
- With these steps done, it's time to log in to the Install Tool. Open your browswer and type the following in the address bar:
- www.YOUR_SITE_URL.org/typo3/install.
- When the Install Tool login appears, type in your Install Tool Password and press the Log in Button.
- Next, click the Basic Configuration link.
- Scroll down the page to the Directories List to ensure all the TYPO3 directories are writable.
- If any of the directories are unwritable, return to your FTP Client and set the permission to 777.
- Next, scroll down to the Update localconf.php fields.
- Next, connect your TYPO3 installation to your database. Enter the database Username and Password. The host should be set at localhost and select the TYPO3 database in the drop down menu.
- Enter your Site name in the appropriate field, and then scroll down the page to the Update localconf.php button.
- At this point, your TYPO3 transfer is nearly complete. The only thing left to do is to reset any of the site's Constants if they've changed (such as the site's URL or other details).
Go ahead and navigate to your site's TYPO3 backend (www.Your_Site_URL.org/typo3) and login. - To change your site's Constants, click on the WEC Config Module.
- Change any of the fields necessary and click the Update button.
- With this step complete, your site shoud be fully transferred to your new host. However, you will want to view it in the Frontend to ensure it is satisfactory.
Monday, September 19, 2011
Add Google Analytics to Typo3 without extension.
You can simple embed Google Analytics to your Typo3 site.
Just add this code in the template typoscript setup:
Friday, September 16, 2011
Rackspace Kaltura Apache conf
Where the apache settings for kaltura are located, when you use a rackspace prebuilt kaltura image:
/opt/kaltura/app/configurations/apache/my_kaltura.conf
Sunday, September 4, 2011
yum update - skip broken
Skip broken:
Skip broken is a feature in yum to skip packages from the transaction there have dependecy problems or introduce problems to the installed packages
Usage:
add the '--skip-broken' option to the yum command line to activate the skip broken feature.
yum update --skip-broken
Skip broken is a feature in yum to skip packages from the transaction there have dependecy problems or introduce problems to the installed packages
Usage:
add the '--skip-broken' option to the yum command line to activate the skip broken feature.
yum update --skip-broken
Friday, September 2, 2011
Kaltura rackspace Content internal error occured - Start/Restart Sphinx
Sometimes sphinx is down.
to restart:
[mouse@wwww etc]# cd /opt/kaltura/app/plugins/sphinx_search/scripts
[mouse@wwww scripts]# dir
cache populateFromLog.php watch.daemon.sh watch.stop.sh
configs searchd.sh watch.populate.sh
[mouse@wwww scripts]# ./watch.populate.sh
[mouse@wwww scripts]# chmod +x populateFromLog.php
[mouse@wwww scripts]# ./searchd.sh
usage: ./searchd.sh {start|stop|stopwait|status}
[mouse@www scripts]# ./searchd.sh start
Starting:Sphinx 1.10-beta (r2420)
Copyright (c) 2001-2010, Andrew Aksyonoff
Copyright (c) 2008-2010, Sphinx Technologies Inc (http://sphinxsearch.com)
to restart:
[mouse@wwww etc]# cd /opt/kaltura/app/plugins/sphinx_search/scripts
[mouse@wwww scripts]# dir
cache populateFromLog.php watch.daemon.sh watch.stop.sh
configs searchd.sh watch.populate.sh
[mouse@wwww scripts]# ./watch.populate.sh
[mouse@wwww scripts]# chmod +x populateFromLog.php
[mouse@wwww scripts]# ./searchd.sh
usage: ./searchd.sh {start|stop|stopwait|status}
[mouse@www scripts]# ./searchd.sh start
Starting:Sphinx 1.10-beta (r2420)
Copyright (c) 2001-2010, Andrew Aksyonoff
Copyright (c) 2008-2010, Sphinx Technologies Inc (http://sphinxsearch.com)
Tuesday, August 30, 2011
Which Linux Version, which Kernel version i am running?
To find out what version of Linux (distro) you are running, enter the following command at the shell prompt:
$ cat /etc/*-release
Sample output on RHEL 5:
Red Hat Enterprise Linux Server release 5 (Tikanga)
Sample outputs on Ubuntu v7.10:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.10
DISTRIB_CODENAME=gutsy
DISTRIB_DESCRIPTION="Ubuntu 7.10"
lsb_release Command
The lsb_release command displays certain LSB (Linux Standard Base) and distribution-specific information. Type the following command:
$ lsb_release -a
Sample outputs:
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 6.0.1 (squeeze)
Release: 6.0.1
Codename: squeeze
How Do I Find Out My Kernel Version?
Type the following command:
$ uname -mrs
Sample outputs:
Linux 2.6.32-5-amd64 x86_64
$ cat /etc/*-release
Sample output on RHEL 5:
Red Hat Enterprise Linux Server release 5 (Tikanga)
Sample outputs on Ubuntu v7.10:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.10
DISTRIB_CODENAME=gutsy
DISTRIB_DESCRIPTION="Ubuntu 7.10"
lsb_release Command
The lsb_release command displays certain LSB (Linux Standard Base) and distribution-specific information. Type the following command:
$ lsb_release -a
Sample outputs:
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 6.0.1 (squeeze)
Release: 6.0.1
Codename: squeeze
How Do I Find Out My Kernel Version?
Type the following command:
$ uname -mrs
Sample outputs:
Linux 2.6.32-5-amd64 x86_64
Tuesday, August 16, 2011
Installing Apache, MySQL, PHP in CentOS 5.5 on Rackspace Cloud
Most of cloud users prefer Rackspace Cloud for its better service and cost effectiveness…
All commands are performed as root to install Apache, MySQL, PHP in CentOS 5.5 Server on Rackspace Cloud.
Install Apache
# sudo yum install httpd mod_ssl
Configure ServerName
# sudo /etc/init.d/httpd start
Remove Error
Starting httpd: httpd: Could not reliably determine the server’s fully qualified domain name, using xx.xx.xxx.xx for ServerName
Modify
# sudo vi /etc/httpd/conf/httpd.conf
Add server name after #ServerName www.example.com:80
ServerName svnlabs
# sudo /etc/init.d/httpd reload
By default port 80 is blocked on server, enable in iptables…
# iptables -I RH-Firewall-1-INPUT -p tcp –dport 80 -j ACCEPT
Chkconfig to start automatically if the Cloud Server is rebooted.
# sudo /sbin/chkconfig httpd on
Install MySQL
# yum install mysql-server
# /etc/init.d/mysqld start
Install PHP
Edit Repo file
# sudo vi /etc/yum.repos.d/CentOS-Base.repo
add at last
[c5-testing]
name=CentOS-5 Testing
baseurl=http://dev.centos.org/centos/$releasever/testing/$basearch/
enabled=1
gpgcheck=1
gpgkey=http://dev.centos.org/centos/RPM-GPG-KEY-CentOS-testing
now run
# yum install php php-common php-gd php-mcrypt php-pear php-pecl-memcache php-mhash php-mysql php-xml php-mbstring
Install PhpMyAdmin
# cd /var/www/html
# wget http://downloads.sourceforge.net/project/phpmyadmin/phpMyAdmin/3.3.6/phpMyAdmin-3.3.6-english.tar.gz?r=http%3A%2F%2Fwww.phpmyadmin.net%2Fhome_page%2Fdownloads.php&ts=1283745912&use_mirror=voxel
# tar zxvf phpMyAdmin-3.3.6-english.tar.gz
# mv phpMyAdmin-3.3.6-english phpmyadmin
# cd phpmyadmin
# cp config.sample.inc.php config.inc.php
Edit config.inc.php for random string $cfg['blowfish_secret'] = ‘RandomStringHere’;
Restart server
# service httpd restart
use the following in the file config.inc.php of phpMyAdmin to restrict access to from remote machines:
$cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
$cfg['Servers'][$i]['AllowDeny']['rules'][] = 'allow % from 127.0.0.1';
$cfg['Servers'][$i]['AllowDeny']['rules'][] = 'deny % from all';
This means that only users logged into my laptop are allowed to see the phpMyAdmin pages in their browser. The percent sign (%) stands for "all users".
All commands are performed as root to install Apache, MySQL, PHP in CentOS 5.5 Server on Rackspace Cloud.
Install Apache
# sudo yum install httpd mod_ssl
Configure ServerName
# sudo /etc/init.d/httpd start
Remove Error
Starting httpd: httpd: Could not reliably determine the server’s fully qualified domain name, using xx.xx.xxx.xx for ServerName
Modify
# sudo vi /etc/httpd/conf/httpd.conf
Add server name after #ServerName www.example.com:80
ServerName svnlabs
# sudo /etc/init.d/httpd reload
By default port 80 is blocked on server, enable in iptables…
# iptables -I RH-Firewall-1-INPUT -p tcp –dport 80 -j ACCEPT
Chkconfig to start automatically if the Cloud Server is rebooted.
# sudo /sbin/chkconfig httpd on
Install MySQL
# yum install mysql-server
# /etc/init.d/mysqld start
Install PHP
Edit Repo file
# sudo vi /etc/yum.repos.d/CentOS-Base.repo
add at last
[c5-testing]
name=CentOS-5 Testing
baseurl=http://dev.centos.org/centos/$releasever/testing/$basearch/
enabled=1
gpgcheck=1
gpgkey=http://dev.centos.org/centos/RPM-GPG-KEY-CentOS-testing
now run
# yum install php php-common php-gd php-mcrypt php-pear php-pecl-memcache php-mhash php-mysql php-xml php-mbstring
Install PhpMyAdmin
# cd /var/www/html
# wget http://downloads.sourceforge.net/project/phpmyadmin/phpMyAdmin/3.3.6/phpMyAdmin-3.3.6-english.tar.gz?r=http%3A%2F%2Fwww.phpmyadmin.net%2Fhome_page%2Fdownloads.php&ts=1283745912&use_mirror=voxel
# tar zxvf phpMyAdmin-3.3.6-english.tar.gz
# mv phpMyAdmin-3.3.6-english phpmyadmin
# cd phpmyadmin
# cp config.sample.inc.php config.inc.php
Edit config.inc.php for random string $cfg['blowfish_secret'] = ‘RandomStringHere’;
Restart server
# service httpd restart
use the following in the file config.inc.php of phpMyAdmin to restrict access to from remote machines:
$cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
$cfg['Servers'][$i]['AllowDeny']['rules'][] = 'allow % from 127.0.0.1';
$cfg['Servers'][$i]['AllowDeny']['rules'][] = 'deny % from all';
This means that only users logged into my laptop are allowed to see the phpMyAdmin pages in their browser. The percent sign (%) stands for "all users".
Sunday, August 7, 2011
Moving an EC2 Instance to another Size
Instead of starting a new instance and having to configure it from scratch, you are able to simply resize the existing instance. In this example you resize a micro instance to a small instance.
Requirements:
1. You must be running an EBS boot instance (not instance-store or S3-based AMI). Any files on ephemeral storage (e.g., /mnt) will be lost.
2. You can only move to a different instance type of the same architecture (32-bit or 64-bit).
3. The private and initial public IP addresses of the instance will be different when it is running on the new hardware. Use an Elastic IP Address to keep the public IP address the same.
4. There will be a short outage while the instance is moved to new hardware (roughly equivalent to the reboot time of normal hardware).
Process:
Run a new t1.micro Ubuntu 10.04 Lucid instance to be our demo. I recommend uploading your own ssh key first.
Wait until it is running and perhaps log in to install software or touch some files so you know it’s your instance. When you are ready, stop the t1.micro instance:
At this point in a normal environment, you might want to create an EBS snapshot AMI of the instance for backup purposes in the event that anything goes wrong. (See: ec2-create-image)
While the EBS boot instance is stopped, switch the instance type from t1.micro to m1.small:
Start the instance using its new m1.small type:
Wait until it is running (again), then log in to verify that it is the same instance with all your software and data. If you were using an Elastic IP address with the instance, it would need to be reassociated after the instance is started.
Eventually, you’ll discover that an m1.small isn’t all that powerful either for moderate loads, so you’ll want to upgrade to a c1.medium, which for many purposes is a great size. It offers 5X the CPU of an m1.small for only 2X the price.
Unfortunately, with a 32-bit instance, c1.medium is as high as you can currently go as of this writing. You’ll need to switch over to a new instance running a 64-bit AMI if you want to go larger.
Vice Versa:
Though we often think “scaling” means moving to larger/faster/more hardware, Amazon EC2 has shown us that it is equally valuable to be able to scale down when we no longer need the extra capacity. The above approach can be used to move your instances to smaller instance types to reduce costs.
If you run this demo, you will be charged for 1 hour of t1.micro instance time plus 1 hour of m1.small instance time, plus fractions of a penny in EBS volume and IO charges. That’s slightly more than a dime.
If you do not need the example instance anymore do not forget to delete it:
Requirements:
1. You must be running an EBS boot instance (not instance-store or S3-based AMI). Any files on ephemeral storage (e.g., /mnt) will be lost.
2. You can only move to a different instance type of the same architecture (32-bit or 64-bit).
3. The private and initial public IP addresses of the instance will be different when it is running on the new hardware. Use an Elastic IP Address to keep the public IP address the same.
4. There will be a short outage while the instance is moved to new hardware (roughly equivalent to the reboot time of normal hardware).
Process:
Run a new t1.micro Ubuntu 10.04 Lucid instance to be our demo. I recommend uploading your own ssh key first.
instance_id=$(ec2-run-instances --instance-type t1.micro --key $USER ami-3e02f257 |
egrep ^INSTANCE | cut -f2)
Wait until it is running and perhaps log in to install software or touch some files so you know it’s your instance. When you are ready, stop the t1.micro instance:
ec2-stop-instances $instance_id
At this point in a normal environment, you might want to create an EBS snapshot AMI of the instance for backup purposes in the event that anything goes wrong. (See: ec2-create-image)
While the EBS boot instance is stopped, switch the instance type from t1.micro to m1.small:
ec2-modify-instance-attribute --instance-type m1.small $instance_id
Start the instance using its new m1.small type:
ec2-start-instances $instance_id
Wait until it is running (again), then log in to verify that it is the same instance with all your software and data. If you were using an Elastic IP address with the instance, it would need to be reassociated after the instance is started.
Eventually, you’ll discover that an m1.small isn’t all that powerful either for moderate loads, so you’ll want to upgrade to a c1.medium, which for many purposes is a great size. It offers 5X the CPU of an m1.small for only 2X the price.
Unfortunately, with a 32-bit instance, c1.medium is as high as you can currently go as of this writing. You’ll need to switch over to a new instance running a 64-bit AMI if you want to go larger.
Vice Versa:
Though we often think “scaling” means moving to larger/faster/more hardware, Amazon EC2 has shown us that it is equally valuable to be able to scale down when we no longer need the extra capacity. The above approach can be used to move your instances to smaller instance types to reduce costs.
If you run this demo, you will be charged for 1 hour of t1.micro instance time plus 1 hour of m1.small instance time, plus fractions of a penny in EBS volume and IO charges. That’s slightly more than a dime.
If you do not need the example instance anymore do not forget to delete it:
ec2-terminate-instances $instance_id
Tuesday, August 2, 2011
Install Alfresco on Rackspace Cloud with Bitnami Stack
Create new (centos) server at rackspace with at minimal 512 MB RAM
yum update
Then you install the lamp stack and alfresco stack form bitnami:
http://bitnami.org/files/stacks/lampstack/5.3.6-0/bitnami-lampstack-5.3.6-0-linux-x64-installer.bin
chmod +x bitnami-lampstack-5.3.6-0-linux-x64-installer.bin
./bitnami-lampstack-5.3.6-0-linux-x64-installer.bin
wget http://bitnami.org/files/stacks/alfresco/3.4.d-1/bitnami-alfresco-3.4.d-1-linux-x64-installer.bin
chmod +x bitnami-alfresco-3.4.d-1-linux-x64-installer.bin
./chmod +x bitnami-alfresco-3.4.d-1-linux-x64-installer.bin
if sql port 3306 is occupied try nother one e.g. 3308
yum update
Then you install the lamp stack and alfresco stack form bitnami:
http://bitnami.org/files/stacks/lampstack/5.3.6-0/bitnami-lampstack-5.3.6-0-linux-x64-installer.bin
chmod +x bitnami-lampstack-5.3.6-0-linux-x64-installer.bin
./bitnami-lampstack-5.3.6-0-linux-x64-installer.bin
wget http://bitnami.org/files/stacks/alfresco/3.4.d-1/bitnami-alfresco-3.4.d-1-linux-x64-installer.bin
chmod +x bitnami-alfresco-3.4.d-1-linux-x64-installer.bin
./chmod +x bitnami-alfresco-3.4.d-1-linux-x64-installer.bin
if sql port 3306 is occupied try nother one e.g. 3308
Sunday, July 24, 2011
Connect Diaspora with Facebook
Enable posting to Facebook from your Dispora Server:
Goto http://developers.facebook.com/setup/
Choose a name, for example "Diaspora at example.org"
Set the site address to your pod URL including a trailing /, for example http://example.org/
Choose a language
Click on Create application
Fill the Captcha
It will now give you your app id and your app_secret which you have to set in your config/oauth_keys.yml
Go to http://www.facebook.com/developers/editapp.php?app_id=< your app id >
Go to Website and fill the domain of your pod (without http://) in Website-Domain, then click Save changes
Restart Diaspora on your server
You're done. It's now possible to post to Facebook from your pod :)
Goto http://developers.facebook.com/setup/
Choose a name, for example "Diaspora at example.org"
Set the site address to your pod URL including a trailing /, for example http://example.org/
Choose a language
Click on Create application
Fill the Captcha
It will now give you your app id and your app_secret which you have to set in your config/oauth_keys.yml
Go to http://www.facebook.com/developers/editapp.php?app_id=< your app id >
Go to Website and fill the domain of your pod (without http://) in Website-Domain, then click Save changes
Restart Diaspora on your server
You're done. It's now possible to post to Facebook from your pod :)
Friday, July 15, 2011
Mobile internet bob.at and Linux
These are the network settings which should work for the austrian mobile internet provider bob.at:
profil name: data.bob
number: *99#
Benutzername: data@bob.at
password: ppp
APN: bob.at
authentication protocol: CHAP and/or PAP
DNS: dynamic
APN und erweiterte Einstellungen: static
IP: dynamic
WINS: dynamic
profil name: data.bob
number: *99#
Benutzername: data@bob.at
password: ppp
APN: bob.at
authentication protocol: CHAP and/or PAP
DNS: dynamic
APN und erweiterte Einstellungen: static
IP: dynamic
WINS: dynamic
Tuesday, June 7, 2011
AWS EC2 mail with SendGrid
mail is a beast. Sending email is easy but getting it pass spam filters when you’re a legitimate service is rather hard. Sending good email is especially hard when on EC2. The reason is due to spammers using and abusing elastic IPS. So, for startups your best bet of sending out a lot of email and getting it to the user is to use a service. You can pick Sendgrid. It’s cheap, fast, has good email tracking and builds all the appropriate email headers to get the mail white listed and into the destinations inbox. Sendgrid is the sender (think of them as an extension to sendmail).
New signups will usually get activated in less than four hours and then you simply add your username/password to the Postfix installation by editing the main.cf file.
First install postfix:
In Ubuntu, or any other apt using Linux distro, type in:
sudo apt-get install postfix
or if your system uses yum:
yum install postfix
Next choice your type of mail configuration: “Internet with Smarthost”.
From there, it’ll ask you questions that are entirely up to you.
It’s going to ask you for the smarthost address. Since we’re using SendGrid, use
smtp.sendgrid.net
Second edit the main.cf file:
Type in
sudo pico /etc/postfix/main.cf
or
sudo vi /etc/postfix/main.cf
to prepare the main.cf file
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = static:yourSendgridUsername:yourSendgridPassword
smtp_sasl_security_options = noanonymous
smtp_tls_security_level = may
header_size_limit = 4096000
relayhost = [smtp.sendgrid.net]:587
Replace yourSendgridUsername and yourSendgridPassword with your username and password.
sudo service postfix restart
Signup for SendGrid here
New signups will usually get activated in less than four hours and then you simply add your username/password to the Postfix installation by editing the main.cf file.
First install postfix:
In Ubuntu, or any other apt using Linux distro, type in:
sudo apt-get install postfix
or if your system uses yum:
yum install postfix
Next choice your type of mail configuration: “Internet with Smarthost”.
From there, it’ll ask you questions that are entirely up to you.
It’s going to ask you for the smarthost address. Since we’re using SendGrid, use
smtp.sendgrid.net
Second edit the main.cf file:
Type in
sudo pico /etc/postfix/main.cf
or
sudo vi /etc/postfix/main.cf
to prepare the main.cf file
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = static:yourSendgridUsername:yourSendgridPassword
smtp_sasl_security_options = noanonymous
smtp_tls_security_level = may
header_size_limit = 4096000
relayhost = [smtp.sendgrid.net]:587
Replace yourSendgridUsername and yourSendgridPassword with your username and password.
sudo service postfix restart
Signup for SendGrid here
Thursday, June 2, 2011
Google +1 /Plus One and your website
The +1 button is a shorthand for "this is pretty cool" or "you should check this out." Click +1 to publicly give something your stamp of approval. Your +1's can help friends, contacts and others find the stuff they search.
Learn more at http://google.com/+1button
Learn more at http://google.com/+1button
Google has provided a “configurator” for web site owners to quickly and easily grab several variations on the necessary Google +1 code.
If you visited the link above, you’ll see that the basic +1 configuration options are self-explanatory.
http://www.google.com/webmasters/+1/button/
Wednesday, June 1, 2011
Google URL Shortener for your website
Google URL Shortener at goo.gl is a service that takes long URLs and squeezes them into fewer characters
Google shortener at Google
to share, tweet, or email to friends. The core goals of this service are:
Stability – ensuring that the service has very good uptime
Security – protecting users from malware and phishing pages
Speed – fast resolution of short URL
Security – protecting users from malware and phishing pages
Speed – fast resolution of short URL
Google provides a gadget for this service. The good news is you can add this gadget to your website.
Google shortener at Google
Sunday, May 22, 2011
Update your LG GW 620
Open firmware for your LG GW 620 android phone.
The project wants to provide an open firmware for the LG GW620/KH5200. They currently have an experimental android 2.2 'froyo' firmware in the Downloads section.
http://openetna.com/openetna/
The project wants to provide an open firmware for the LG GW620/KH5200. They currently have an experimental android 2.2 'froyo' firmware in the Downloads section.
http://openetna.com/openetna/
Tuesday, May 3, 2011
How to restart my-sql-Server
Each distribution comes with a shell script (read as service) to restart / stop / start MySQL server. First login as root user and open shell prompt (command prompt).
Login as root user. Now type the following command as per your Linux distro:
A) If you are using mysql on RedHat Linux (Fedora Core/Cent OS) then use following command:
* To start mysql server:
/etc/init.d/mysqld start
* To stop mysql server:
/etc/init.d/mysqld stop
* To restart mysql server
/etc/init.d/mysqld restart
Tip: Redhat Linux also supports service command, which can be use to start, restart, stop any service:
# service mysqld start # service mysqld stop # service mysqld restart
(B) If you are using mysql on Debian / Ubuntu Linux then use following command:
* To start mysql server:
/etc/init.d/mysql start
* To stop mysql server:
/etc/init.d/mysql stop
* To restart mysql server
/etc/init.d/mysql restart
Thursday, April 28, 2011
Free google apps for domains - Get your mailserver done by google
Free google mail for your domain is the convenient way to connect your domain with a mail-Server. Up to 10 email-adresses are in the free edition of google apps.
You can register for the service here: https://www.google.com/a/cpanel/domain/new
You can register for the service here: https://www.google.com/a/cpanel/domain/new
Saturday, April 23, 2011
Basic Software installation on a new PC
Wednesday, April 20, 2011
Make your own share this script
Maintain control about your share options with this open source software.
You can use it as standalone or as word press plugin.
Features of the Share script include:
Ability to save pages to social sites like Facebook, Digg, Delicious, Google, Yahoo, and more
You can use it as standalone or as word press plugin.
Features of the Share script include:
Ability to save pages to social sites like Facebook, Digg, Delicious, Google, Yahoo, and more
- Ability to email your friends
- Ability to save the page as a PDF or Word doc
- Ability to print the page
- Fully extensible with a plugin system. Add any social site you want. You can even add IM, SMS, and more!
- Complete stat tracking - see what pages are being shared, how they are being shared, over any time period
Tuesday, April 19, 2011
Accessing SSH on a non-standard port via the command line
vento> ssh -p 6896 targetserver
or special directory:
vento> ssh -p 6896 user@targetserver
Sunday, April 17, 2011
Howto disable recursive DNS queries
To disable Recursive DNS follow the steps:
1) SSH server as root and edit file /etc/named.conf
root@server[~]#vi /etc/named.conf
2) add line recursion no; in options clause and it will look something like.
options {directory “/var/named”;dump-file “/var/named/data/cache_dump.db”;statistics-file “/var/named/data/named_stats.txt”;/** If there is a firewall between you and nameservers you want* to talk to, you might need to uncomment the query-source* directive below. Previous versions of BIND always asked* questions using port 53, but BIND 8.1 uses an unprivileged* port by default.*/// query-source address * port 53;recursion no;};
3) Now restart or reload named service.
root@server[~]#/etc/init.d/named reload
Google Chrome: about: und chrome: Befehle im Browser
Die Befehle im Einzelnen:
Neben den about-Aufrufen gibt es spezielle chrome-Seiten, die Sie auch über die Menüs erreichen:
Über chrome-Seiten sind auch einige about-Befehle zu erreichen, wie chrome://about/sync/
- about:memory liefert Informationen rund um den verwendeten Speicher, sortiert nach einzelnen Tabs und Plugins.
- about:dns zeigt die zwischengespeicherten DNS-Einträge.
- about:histograms zeigt Chrome-interne Messungen.
- about:cache zeigt die im Cache gespeicherten URLs.
- about:plugins listet die installierten Plug-ins, diese können an dieser Stelle auch deaktiviert werden.
- about:version zeigt die aktuelle Version von Chrome, Webkit und der JavaScript-Engine V8 an, zudem wird der User-Agent im Detail aufgelistet.
- about:net-internals zeigt einen Dump der Informationen des Netzwerk-Stacks an.
- about:crash lässt den aktuelle Tab zu Testzwecken "abstürzen"
- about:credits listet die verschiedenen Bibliotheken und Techniken auf, die in Chrome zum Einsatz kommen
- about:terms zeigt die Nutzungsbedingungen von Google Chrome
- about:about listet (fast) alle about-Befehle auf, die die verwendete Version von Google Chrome unterstützt
- about:sync zeigt eine Zusammenfassung zur letzten Chrome-Synchronisation
- about:tcmalloc listet detailliert den angeforderten Speicher für den letzten Seitenaufruf
- about:gpu gibt Informationen zur Grafikkarte aus. Die Anzeige ist erst relevant, wenn Chrome die Grafik-Hardware zum Rendern nutzt.
- about:net-internals zeigt für Debugging-Zwecke in Reitern ausführliche Informationen zu Proxys, Requests, DNS-Abrufen, Sockets, HTTP-Cache und Testmöglichkeiten für anzugebende URLs an.
Neben den about-Aufrufen gibt es spezielle chrome-Seiten, die Sie auch über die Menüs erreichen:
- chrome://downloads/ zeigt eine Seite mit allen durchgeführten Downloads an
- chrome://history listet den Browser-Verlauf auf, also die zuletzt besuchten Webseiten
- chrome://extensions zeigt alle installierten Browser-Erweiterungen inklusive Zugriff auf Deinstallieren, Deaktivieren und Optionen der Plugins
- chrome://bookmarks aktiviert den Lesezeichen-Manager von Google Chrome
- chrome://newtab/ öffnet die vorgegebene Startseite (nicht etwa einen neuen Tab)
Über chrome-Seiten sind auch einige about-Befehle zu erreichen, wie chrome://about/sync/
Thursday, April 7, 2011
Secure your Kloxo Installation with your Firewall/IPTABLES
Stop iptables service:
/etc/init.d/iptables stop
Disable iptables service:
chkconfig iptables off
Copy this code to /etc/init.d/firewall (Reminder: Disable "word wrap" in your text editor. Ex.: nano -w /etc/init.d/firewall)
#!/bin/sh
# firewall
# chkconfig: 3 21 91
# description: Starts, stops iptables firewall
case "$1" in
start)
# Clear rules
iptables -t filter -F
iptables -t filter -X
echo - Clear rules : [OK]
# SSH In
iptables -t filter -A INPUT -p tcp --dport 22 -j ACCEPT
echo - SSH : [OK]
# Don't break established connections
iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
iptables -A OUTPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
echo - established connections : [OK]
# Block all connections by default
iptables -t filter -P INPUT DROP
iptables -t filter -P FORWARD DROP
iptables -t filter -P OUTPUT DROP
echo - Block all connections : [OK]
# Loopback
iptables -t filter -A INPUT -i lo -j ACCEPT
iptables -t filter -A OUTPUT -o lo -j ACCEPT
echo - Loopback : [OK]
# ICMP (Ping)
iptables -t filter -A INPUT -p icmp -j ACCEPT
iptables -t filter -A OUTPUT -p icmp -j ACCEPT
echo - PING : [OK]
# DNS In/Out
iptables -t filter -A OUTPUT -p tcp --dport 53 -j ACCEPT
iptables -t filter -A OUTPUT -p udp --dport 53 -j ACCEPT
iptables -t filter -A INPUT -p tcp --dport 53 -j ACCEPT
iptables -t filter -A INPUT -p udp --dport 53 -j ACCEPT
echo - DNS : [OK]
# NTP Out
iptables -t filter -A OUTPUT -p udp --dport 123 -j ACCEPT
echo - NTP : [OK]
# FTP Out
iptables -t filter -A OUTPUT -p tcp --dport 20:21 -j ACCEPT
iptables -t filter -A OUTPUT -p tcp --dport 30000:50000 -j ACCEPT
# FTP In
iptables -t filter -A INPUT -p tcp --dport 20:21 -j ACCEPT
iptables -t filter -A INPUT -p tcp --dport 30000:50000 -j ACCEPT
iptables -t filter -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
echo - FTP : [OK]
# HTTP + HTTPS Out
iptables -t filter -A OUTPUT -p tcp --dport 80 -j ACCEPT
iptables -t filter -A OUTPUT -p tcp --dport 443 -j ACCEPT
# HTTP + HTTPS In
iptables -t filter -A INPUT -p tcp --dport 80 -j ACCEPT
iptables -t filter -A INPUT -p tcp --dport 443 -j ACCEPT
echo - HTTP/HTTPS : [OK]
# Mail SMTP:25
iptables -t filter -A INPUT -p tcp --dport 25 -j ACCEPT
iptables -t filter -A OUTPUT -p tcp --dport 25 -j ACCEPT
echo - SMTP : [OK]
# Mail POP3:110
iptables -t filter -A INPUT -p tcp --dport 110 -j ACCEPT
iptables -t filter -A OUTPUT -p tcp --dport 110 -j ACCEPT
echo - POP : [OK]
# Mail IMAP:143
iptables -t filter -A INPUT -p tcp --dport 143 -j ACCEPT
iptables -t filter -A OUTPUT -p tcp --dport 143 -j ACCEPT
echo - IMAP : [OK]
# Kloxo
iptables -t filter -A INPUT -p tcp --dport 7777:7778 -j ACCEPT
iptables -t filter -A OUTPUT -p tcp --dport 7777:7778 -j ACCEPT
echo - Kloxo : [OK]
echo - Firewall [OK]
exit 0
;;
stop)
echo "Stopping Firewall: "
iptables -P INPUT ACCEPT
iptables -P OUTPUT ACCEPT
iptables -t filter -F
exit 0
;;
*)
echo "Usage: /etc/init.d/firewall {start|stop}"
exit 1
;;
esac
Enable/Start Firewall Service
chmod 700 /etc/init.d/firewall
add firewall service:
chkconfig -–add firewall
auto start firewall:
chkconfig -–level 2345 firewall on
start firewall:
/etc/init.d/firewall start
If you have slave server, add this on the master
iptables -t filter -A INPUT -p tcp -s SLAVE_IP --dport 7779 -j ACCEPT
iptables -t filter -A OUTPUT -p tcp -d SLAVE_IP --dport 7779 -j ACCEPT
Note: replace SLAVE_IP with your Slave server IP.
Add this on slave server
iptables -t filter -A INPUT -p tcp -s MASTER_IP --dport 7779 -j ACCEPT
iptables -t filter -A OUTPUT -p tcp -d MASTER_IP --dport 7779 -j ACCEPT
Note: replace MASTER_IP with your Master server IP.
After all always a good idea
/sbin/service httpd restart
/etc/init.d/iptables stop
Disable iptables service:
chkconfig iptables off
Copy this code to /etc/init.d/firewall (Reminder: Disable "word wrap" in your text editor. Ex.: nano -w /etc/init.d/firewall)
#!/bin/sh
# firewall
# chkconfig: 3 21 91
# description: Starts, stops iptables firewall
case "$1" in
start)
# Clear rules
iptables -t filter -F
iptables -t filter -X
echo - Clear rules : [OK]
# SSH In
iptables -t filter -A INPUT -p tcp --dport 22 -j ACCEPT
echo - SSH : [OK]
# Don't break established connections
iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
iptables -A OUTPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
echo - established connections : [OK]
# Block all connections by default
iptables -t filter -P INPUT DROP
iptables -t filter -P FORWARD DROP
iptables -t filter -P OUTPUT DROP
echo - Block all connections : [OK]
# Loopback
iptables -t filter -A INPUT -i lo -j ACCEPT
iptables -t filter -A OUTPUT -o lo -j ACCEPT
echo - Loopback : [OK]
# ICMP (Ping)
iptables -t filter -A INPUT -p icmp -j ACCEPT
iptables -t filter -A OUTPUT -p icmp -j ACCEPT
echo - PING : [OK]
# DNS In/Out
iptables -t filter -A OUTPUT -p tcp --dport 53 -j ACCEPT
iptables -t filter -A OUTPUT -p udp --dport 53 -j ACCEPT
iptables -t filter -A INPUT -p tcp --dport 53 -j ACCEPT
iptables -t filter -A INPUT -p udp --dport 53 -j ACCEPT
echo - DNS : [OK]
# NTP Out
iptables -t filter -A OUTPUT -p udp --dport 123 -j ACCEPT
echo - NTP : [OK]
# FTP Out
iptables -t filter -A OUTPUT -p tcp --dport 20:21 -j ACCEPT
iptables -t filter -A OUTPUT -p tcp --dport 30000:50000 -j ACCEPT
# FTP In
iptables -t filter -A INPUT -p tcp --dport 20:21 -j ACCEPT
iptables -t filter -A INPUT -p tcp --dport 30000:50000 -j ACCEPT
iptables -t filter -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
echo - FTP : [OK]
# HTTP + HTTPS Out
iptables -t filter -A OUTPUT -p tcp --dport 80 -j ACCEPT
iptables -t filter -A OUTPUT -p tcp --dport 443 -j ACCEPT
# HTTP + HTTPS In
iptables -t filter -A INPUT -p tcp --dport 80 -j ACCEPT
iptables -t filter -A INPUT -p tcp --dport 443 -j ACCEPT
echo - HTTP/HTTPS : [OK]
# Mail SMTP:25
iptables -t filter -A INPUT -p tcp --dport 25 -j ACCEPT
iptables -t filter -A OUTPUT -p tcp --dport 25 -j ACCEPT
echo - SMTP : [OK]
# Mail POP3:110
iptables -t filter -A INPUT -p tcp --dport 110 -j ACCEPT
iptables -t filter -A OUTPUT -p tcp --dport 110 -j ACCEPT
echo - POP : [OK]
# Mail IMAP:143
iptables -t filter -A INPUT -p tcp --dport 143 -j ACCEPT
iptables -t filter -A OUTPUT -p tcp --dport 143 -j ACCEPT
echo - IMAP : [OK]
# Kloxo
iptables -t filter -A INPUT -p tcp --dport 7777:7778 -j ACCEPT
iptables -t filter -A OUTPUT -p tcp --dport 7777:7778 -j ACCEPT
echo - Kloxo : [OK]
echo - Firewall [OK]
exit 0
;;
stop)
echo "Stopping Firewall: "
iptables -P INPUT ACCEPT
iptables -P OUTPUT ACCEPT
iptables -t filter -F
exit 0
;;
*)
echo "Usage: /etc/init.d/firewall {start|stop}"
exit 1
;;
esac
Enable/Start Firewall Service
chmod 700 /etc/init.d/firewall
add firewall service:
chkconfig -–add firewall
auto start firewall:
chkconfig -–level 2345 firewall on
start firewall:
/etc/init.d/firewall start
If you have slave server, add this on the master
iptables -t filter -A INPUT -p tcp -s SLAVE_IP --dport 7779 -j ACCEPT
iptables -t filter -A OUTPUT -p tcp -d SLAVE_IP --dport 7779 -j ACCEPT
Note: replace SLAVE_IP with your Slave server IP.
Add this on slave server
iptables -t filter -A INPUT -p tcp -s MASTER_IP --dport 7779 -j ACCEPT
iptables -t filter -A OUTPUT -p tcp -d MASTER_IP --dport 7779 -j ACCEPT
Note: replace MASTER_IP with your Master server IP.
After all always a good idea
/sbin/service httpd restart
Installing Kloxo on Centos 64
Take a fresh installation of centos 5.5
Don't yum update now.
Install Mysql
su root
setenforce 0
wget http://download.lxcenter.org/download/kloxo/production/kloxo-install-master.sh
Take the install option with existing mysql database (PASSWORD = your root password SQL)
sh ./kloxo-install-master.sh --db-rootpassword=PASSWORD
go through the installation process. Answer all questions wit yes and take a break for 15 minutes.
Don't yum update now.
Install Mysql
su root
setenforce 0
wget http://download.lxcenter.org/download/kloxo/production/kloxo-install-master.sh
Take the install option with existing mysql database (PASSWORD = your root password SQL)
sh ./kloxo-install-master.sh --db-rootpassword=PASSWORD
go through the installation process. Answer all questions wit yes and take a break for 15 minutes.
Install MySql on Centos 5.5
Install:
yum install mysql-server
Start:
service mysqld start OR /etc/init.d/mysqld start
Secure it:
/usr/bin/mysql_secure_installation
It is going to ask you handful of questions:
Current Root Password
You will be asked for your current root password. Because this is a new installation it is set to none. Press enter.
Set Root Password
If the above step worked correctly you should be prompted with a question asking you if you would like to set your root password. Please press Y and press Enter.
You will be asked for your root password twice. If it works you will see Success!
Removing Anonymous Users
You will be prompted to remove the MySQL anonymous users. For security reasons we want to do this. The text above the question explains this topic in more detail. Press Y and then Enter.
Disallow Root Login
You will be asked if you would like to disallow remote login for the root user and only allow connections from the server itself. To keep our server secure you want to say Y and press Enter.
Delete test Database
MySQL ships with a default database called test. This is not needed and can be deleted. Press Y and then Enter to delete the test database and it’s associated users.
Reload Privilege Tables
This step will reload the user settings (called privilege tables) so all user changes will take effect. Press Y and then Enter to continue.
yum install mysql-server
Start:
service mysqld start OR /etc/init.d/mysqld start
Secure it:
/usr/bin/mysql_secure_installation
It is going to ask you handful of questions:
Current Root Password
You will be asked for your current root password. Because this is a new installation it is set to none. Press enter.
Set Root Password
If the above step worked correctly you should be prompted with a question asking you if you would like to set your root password. Please press Y and press Enter.
You will be asked for your root password twice. If it works you will see Success!
Removing Anonymous Users
You will be prompted to remove the MySQL anonymous users. For security reasons we want to do this. The text above the question explains this topic in more detail. Press Y and then Enter.
Disallow Root Login
You will be asked if you would like to disallow remote login for the root user and only allow connections from the server itself. To keep our server secure you want to say Y and press Enter.
Delete test Database
MySQL ships with a default database called test. This is not needed and can be deleted. Press Y and then Enter to delete the test database and it’s associated users.
Reload Privilege Tables
This step will reload the user settings (called privilege tables) so all user changes will take effect. Press Y and then Enter to continue.
Tuesday, April 5, 2011
httpd restart - start - stop
to restart:
/sbin/service httpd restart
to start:
/sbin/service httpd start
to stop:
/sbin/service httpd stop
/sbin/service httpd restart
to start:
/sbin/service httpd start
to stop:
/sbin/service httpd stop
Friday, April 1, 2011
cpanel Alternativen
Ja es gibt Alternativen zu cpanel:
1. Gnu Panel: Hosting Control Panel für Debian
2. ispCP für Debian, Centos Fedora, Gentoo Linux, openSUSE, Red Hat Linux und Ubuntu als ein Multi-Server-Verwaltungs- sowie Administrationstoo
3. Webmin: Per Webbrowser können die verschiedenen Server-Prozesse oder Daemonen administriert werden, die auf einem Unix-Rechner laufen - häufig in Verbindung mit
4- Virtualmin: Für die einfache Konfiguration verschiedener Serverdienste wie beispielsweise Mailserver, Domains und MySQL.
Ein Vergleich von gängigen Programmen hier: http://isp-control.net/documentation/about/comparsion
1. Gnu Panel: Hosting Control Panel für Debian
2. ispCP für Debian, Centos Fedora, Gentoo Linux, openSUSE, Red Hat Linux und Ubuntu als ein Multi-Server-Verwaltungs- sowie Administrationstoo
3. Webmin: Per Webbrowser können die verschiedenen Server-Prozesse oder Daemonen administriert werden, die auf einem Unix-Rechner laufen - häufig in Verbindung mit
4- Virtualmin: Für die einfache Konfiguration verschiedener Serverdienste wie beispielsweise Mailserver, Domains und MySQL.
Ein Vergleich von gängigen Programmen hier: http://isp-control.net/documentation/about/comparsion
Thursday, March 10, 2011
Fastenkur für CSS-Code - 30 % sind drin.
CSSTidy ist ein Tool um CSS-Code zu optimiern. Farbcode wird in Kurzform gebracht, Shorthands werden optimiert und überflüssige Zeichen entfernt. Die Option "CSS erhalten" empfieht sich z.B., wenn Kommentarte beigehalten werden sollen. Auf ungültige Eigenschaften wird hingewiesen, auf Wunsch werden diese auch entfernt. CSSTidy ist aber kein Validator und erkennt nur teilweise Fehlercode. In der höchsten Komprimierungsstufe wird der Code komplett in eine Zeile gepackt und daher extrem unübersichtlich. Hier empfiehlt es sich die Originalversion zusätzlich zu sichern.
Zu CSS-Tidy auf leerraum.org
Zu CSS-Tidy auf leerraum.org
Tuesday, March 1, 2011
Google Docs mit OCR
Google Docs hat jetz ein OCR Toll eingebaut. OCR für 34 Sprachen wird angeboten. Ein sehr praktischer Weg um aus dem PDF File, Textdateien zu erhalten. Verwendet wird nach Angabe von Google, die gleiche Technologie welche bei Google Books angewendet wird.
mehr auf googledocs.blogsport.com
mehr auf googledocs.blogsport.com
Sunday, February 20, 2011
Site Verification in Typo3 Setup
Google verlangt für die Webmaster Tools und andere Services die Seitenverifizierung.
Ein einfacher und schneller Weg ist den Verification-Code in die Metaangaben einzubauen.
Dies erfolgt im Template-Setup auf folgende Weise:
page.meta.google-site-verification = dein-verification-code
Ein einfacher und schneller Weg ist den Verification-Code in die Metaangaben einzubauen.
Dies erfolgt im Template-Setup auf folgende Weise:
page.meta.google-site-verification = dein-verification-code
Wednesday, January 5, 2011
URL-Shortener für die eigene Webseite im Selbstbau
URL-Shortener sind praktisch um lange URL's in kurzer Form darzustellen.
Drei Shortener bieten sich zur Isntallation auf der eigenen Webseite an:
PHP-URL Shortener; PHP-Skript Download bei github:
PHP-Url-Shortener
get shorty
Download
yourls - auch wordpress plugin erhältlich
download yourls
Drei Shortener bieten sich zur Isntallation auf der eigenen Webseite an:
PHP-URL Shortener; PHP-Skript Download bei github:
PHP-Url-Shortener
get shorty
Download
yourls - auch wordpress plugin erhältlich
download yourls
Subscribe to:
Posts (Atom)