Amahi Wiki - User contributions [en]

User talk:Scope

2011-10-08T18:25:33Z

Bk: Welcome!

'''Welcome to ''Amahi''!'''
We hope you will contribute much and well.
You will probably want to read the [[Help:Contents|help pages]].
Again, welcome and have fun! [[User:Bk|Bk]] 11:25, 8 October 2011 (PDT)

User talk:ASH

2011-10-08T18:24:01Z

Bk: Welcome!

User talk:Kevin Baumhover

2011-10-04T00:37:20Z

Bk: Welcome!

User talk:Rolami

2011-09-21T16:38:24Z

Bk: Welcome!

Amahi 6.1

2011-09-19T01:02:57Z

Bk:

= Release Notes =

* Huge amount of fixes and improvements for Ubuntu! A few people are rumored to be running Amahi 6 on Ubuntu/Debian. Thanks to the U/D team!
* Fix for running install scripts with elevated privileges for apps without a webapp, e.g. the new [http://www.amahi.org/apps/vnc VNC] one-click app works out of the box
* Fix for properly setting the timezone in php.ini at installation time
* CSS fixes for RTL (right to left) languages
* New translation to Arabian, contributed by Abdulrhman Al-Khamees. Check out [http://dl.dropbox.com/u/196664/Screenshot-6.png one] [http://dl.dropbox.com/u/196664/Screenshot-7.png the] [http://dl.dropbox.com/u/196664/Screenshot-8.png many] [http://dl.dropbox.com/u/196664/Screenshot-9.png screenshots]!
* New translation to Latvian, contributed by Ivo
* New translation to [http://www.kosacrta.hr/ Croatian], contributed by [http://www.kosacrta.hr/ Vladimir]
* Finish off Latvian, Arabian, Hebrew, Russian and Finnish(Suomi) translations
* Update logos to new Amahi logo - thanks BK!
* Fix to add delay to amahi-download for more reliability in webapp installs
* New module in the platform code to capture many/most/all platform-dependent things!
* Dummy mode for development, where hdactl is ignored, so most system stuff is dropped on the floor and no errors are raised
* Add platform bits to be able to run the platform on Mac OS X, mostly for development (don't get too excited :) )
* Switch the available apps to be the first submenu and Installed Apps as the second will make things easier usability-wise - here is a screenshot of the prototype: http://cpg.amahi.me/Public/Screenshots/new-app-area.png
* Enhanced support for uber advanced [[Network customizations]], for the ninja networking guru in you

= To-Do =

* Add new disk wizard
* Make it even easier to host apps from outside

Express Disc

2011-08-26T00:28:59Z

Bk:

= Advantages of the Express Installation =

The Amahi Express CD gives you numerous advantages over the traditional Amahi installation
* Headless means that there is no desktop after install. This means faster and meaner system, with no wasted resources on graphics or desktop.
* All-in-one means most necessary packages are included, much less downloading necessary
* Up-to-date means we have included the latest upstream updates from Fedora in it as well as the latest goodies from Amahi at the time the CD was pressed!

= '''WARNING''' =

Please make sure your understand this:

<div style="color:darkred; background: #f8e6e6; border: 1px solid #aa0000; padding: 1em; margin: 1em 3em">Express means that it will automatically WIPE OUT your entire computer (unless you chose the expert option). '''All the drives''' connected at the time of the install will be WIPED OUT. Unplug from the system or take out any drive you do not want wiped out (you can [[Adding_a_second_hard_drive_to_your_HDA | add it later]]).</div>

= Download via Bittorrent =

'''32 bits ISO''': For use with 32 bit and 64 bit processors to include Intel Pentium III and IV, Core Duo, AMD Athlon etc.

'''64 bits ISO''': For use with new dual, triple, quad, hex core processors to include Intel Core 2 Duo/Quad, AMD Phenom, Athlon II, Athlon X2 etc.

Bittorrent (recommended):

[http://dl.amahi.org/isos/Amahi-6.1-Express-v1-i386.iso.torrent 32bit Bittorrent Download]

[http://dl.amahi.org/isos/Amahi-6.1-Express-v1-x86_64.iso.torrent 64bit Bittorrent Download]

= ISO Verification =

The downloads above can be verified with the following [http://dl.amahi.org/isos/CHECKSUMS.txt Express CD Checksums].

You can obtain the checksums by running:

sha1sum some.iso

md5sum some.iso

And one Windows you can use one of the utilities listed here:

[http://wiki.amahi.org/index.php/Packaging_tools_for_windows Md5 Checking Tools]

= Download via HTTP =

Direct (http) download ('''NOT recommended'''):

[http://download.amahi.org/Amahi-6.1-Express-v1-i386.iso Express CD Direct (http) 32bit download]

[http://download.amahi.org/Amahi-6.1-Express-v1-x86_64.iso Express CD Direct (http) 64bit download]

= CD Cover =

If you would like to print a CD cover for the Express CD, visit the [[Express CD cover]] page!

= Installing =

You will need a monitor and a keyboard to install. Pop the CD into the PC and follow the prompts!

= Log in on your Amahi Dashboard =

Once you have installed using the Amahi Express CD, you can login on http://hda using the following credentials:<br/>
Username: '''admin'''<br/>
Password: '''admin'''<br/>

= Troubleshooting =

We have a page to track [[Express CD troubleshooting]].

= GUI Installation =

As a desktop environment is not installed we have complied two methods. Please take a look at our [http://wiki.amahi.org/index.php/GUI_Install_for_Express_CD GUI install wiki page] for this. Alternatively we are testing the [http://www.amahi.org/apps/gnome-desktop gnome desktop app] for future implementation.

= Kudos and Credits =

Special thanks to Solomon (aka slm4996), and Rod Waldren ... great work!

GUI Install for Express Disc

2011-08-26T00:13:49Z

Bk:

GUI Install for Express Disc

2011-08-26T00:12:45Z

Bk:

GUI Install for Express Disc

2011-08-26T00:10:34Z

Bk:

GUI Install for Express Disc

2011-08-26T00:07:27Z

Bk:

GUI Install for Express Disc

2011-08-25T23:56:46Z

Bk: moved Gnome install for express cd to GUI Install for Express CD: Renaming seems right :P

Gnome install for express cd

2011-08-25T23:56:46Z

Bk: moved Gnome install for express cd to GUI Install for Express CD: Renaming seems right :P

#REDIRECT [[GUI Install for Express CD]]

GUI Install for Express Disc

2011-08-25T23:56:17Z

Bk:

GUI Install for Express Disc

2011-08-25T23:54:17Z

Bk:

== Synopsis ==

The Amahi Express install does not install the graphical user interface gnome. This Guide instructs you on how to install the X Server as well as to make the X Server boot everytime. To install after Amahi Express has finished installing execute the following commands:

== Commands ==

Become root:

{{Code|su -}}

Enter your password for the root user

{{Code|yum -y groupinstall "X Window System" "GNOME Desktop Environment"}}

For the users who want KDE

{{Code|yum -y groupinstall "X Windows System" "KDE"}}

== Optional ==

You can remove the packages i.e.:

{{Code|yum groupremove "KDE"}}

== Configure Your Display ==

You may also need to configure your display:

{{Code|Xorg :1 -configure}}

Then we need to move the new config file so Xorg can read it.

{{Code|cp /root/xorg.conf.new /etc/X11/xorg.conf}}

Next we need to make sure it boots into init 5. Run the following command to accomplish this:

{{Code|sed -i 's/id:3:initdefault:/id:5:initdefault:/g' /etc/inittab}}

You can either reboot or boot into the GNOME/KDE Desktop:

{{Code|startx}}

== To change your Amahi HDA to boot into gnome ==

First and foremost you should be logged in as root.

The /etc folder on these Linux installations contain a file named inittab - mind you no extensions to the filename. This file contains lots of important parameters & runlevel configurations that the kernel reads while booting and configures the system accordingly. Open this file in your favourite editor and scroll down just a little bit say, till the 18th-20th line (usually) till you find something similar to this:

id:3:initdefault:

As you can see the last line id:3:initdefault: specifies WHAT MODE (Graphical/Text/MultiUser etc) to boot the system into. The number "3" which according to the options - is Full multiuser mode - involving all the networking features of Linux, but in a non-graphical environment.

Change this value to "5" - here, according to the Commented out options above tells the system to boot straight into X11 (X-Windows) i.e. the Graphical Mode.

That's it. We are done. Save the file and quit. Reboot your system for the setting to take effect.

WARNING: When you are editing these critical system files in Linux, be absolutely sure of WHAT you are editing. One SINGLE MISTAKE can render the whole system non-bootable. These are as dangerous as (if not more) Windows Registry. So there...

* Default runlevel. The runlevels used by RHS are:
* 0 - halt (Do NOT set initdefault to this)
* 1 - Single user mode
* 2 - Multiuser, without NFS (The same as 3, if you do not have networking)
* 3 - Full multiuser mode
* 4 - unused
* 5 - X11
* 6 - reboot (Do NOT set initdefault to this)

== Automatic Login ==

If you want a specified user to login (if you are using MythTV or some other app which requires the X Server) then please do so with [http://wiki.amahi.org/index.php/VNC these instructions].

Cheers!

The Amahi Team

GUI Install for Express Disc

2011-08-25T23:53:29Z

Bk:

{{NeedsUpdate}}'''
Appears to be Fedora 12 Guidance'''

== Synopsis ==

The Amahi Express install does not install the graphical user interface gnome. This Guide instructs you on how to install the X Server as well as to make the X Server boot everytime. To install after Amahi Express has finished installing execute the following commands:

== Commands ==

Become root:

{{Code|su -}}

Enter your password for the root user

{{Code|yum -y groupinstall "X Window System" "GNOME Desktop Environment"}}

For the users who want KDE

{{Code|yum -y groupinstall "X Windows System" "KDE"}}

== Optional ==

You can remove the packages i.e.:

{{Code|yum groupremove "KDE"}}

== Configure Your Display ==

You may also need to configure your display:

{{Code|Xorg :1 -configure}}

Then we need to move the new config file so Xorg can read it.

{{Code|cp /root/xorg.conf.new /etc/X11/xorg.conf}}

Next we need to make sure it boots into init 5. Run the following command to accomplish this:

{{Code:sed -i 's/id:3:initdefault:/id:5:initdefault:/g' /etc/inittab}}

You can either reboot or boot into the GNOME/KDE Desktop:

{{Code|startx}}

== To change your Amahi HDA to boot into gnome ==

First and foremost you should be logged in as root.

The /etc folder on these Linux installations contain a file named inittab - mind you no extensions to the filename. This file contains lots of important parameters & runlevel configurations that the kernel reads while booting and configures the system accordingly. Open this file in your favourite editor and scroll down just a little bit say, till the 18th-20th line (usually) till you find something similar to this:

id:3:initdefault:

As you can see the last line id:3:initdefault: specifies WHAT MODE (Graphical/Text/MultiUser etc) to boot the system into. The number "3" which according to the options - is Full multiuser mode - involving all the networking features of Linux, but in a non-graphical environment.

Change this value to "5" - here, according to the Commented out options above tells the system to boot straight into X11 (X-Windows) i.e. the Graphical Mode.

That's it. We are done. Save the file and quit. Reboot your system for the setting to take effect.

WARNING: When you are editing these critical system files in Linux, be absolutely sure of WHAT you are editing. One SINGLE MISTAKE can render the whole system non-bootable. These are as dangerous as (if not more) Windows Registry. So there...

* Default runlevel. The runlevels used by RHS are:
* 0 - halt (Do NOT set initdefault to this)
* 1 - Single user mode
* 2 - Multiuser, without NFS (The same as 3, if you do not have networking)
* 3 - Full multiuser mode
* 4 - unused
* 5 - X11
* 6 - reboot (Do NOT set initdefault to this)

== Automatic Login ==

If you want a specified user to login (if you are using MythTV or some other app which requires the X Server) then please do so with [http://wiki.amahi.org/index.php/VNC these instructions].

Cheers!

The Amahi Team

GUI Install for Express Disc

2011-08-25T23:52:52Z

Bk:

{{NeedsUpdate}}'''
Appears to be Fedora 12 Guidance'''

== Synopsis ==

The Amahi Express install does not install the graphical user interface gnome. This Guide instructs you on how to install the X Server as well as to make the X Server boot everytime. To install after Amahi Express has finished installing execute the following commands:

== Commands ==

Become root:

{{Code|su -}}

Enter your password for the root user

{{Code|yum -y groupinstall "X Window System" "GNOME Desktop Environment"}}

For the users who want KDE

{{Code|yum -y groupinstall "X Windows System" "KDE"}}

== Optional ==

You can remove the packages i.e.:

{{Code|yum groupremove "KDE"}}

== Configure Your Display ==

You may also need to configure your display:

{{Code|Xorg :1 -configure}}

Then we need to move the new config file so Xorg can read it.

{{Cod|cp /root/xorg.conf.new /etc/X11/xorg.conf}}

Next we need to make sure it boots into init 5. Run the following command to accomplish this:

{{Coode:sed -i 's/id:3:initdefault:/id:5:initdefault:/g' /etc/inittab}}

You can either reboot or boot into the GNOME/KDE Desktop:

{{Code|startx}}

== To change your Amahi HDA to boot into gnome ==

First and foremost you should be logged in as root.

The /etc folder on these Linux installations contain a file named inittab - mind you no extensions to the filename. This file contains lots of important parameters & runlevel configurations that the kernel reads while booting and configures the system accordingly. Open this file in your favourite editor and scroll down just a little bit say, till the 18th-20th line (usually) till you find something similar to this:

id:3:initdefault:

As you can see the last line id:3:initdefault: specifies WHAT MODE (Graphical/Text/MultiUser etc) to boot the system into. The number "3" which according to the options - is Full multiuser mode - involving all the networking features of Linux, but in a non-graphical environment.

Change this value to "5" - here, according to the Commented out options above tells the system to boot straight into X11 (X-Windows) i.e. the Graphical Mode.

That's it. We are done. Save the file and quit. Reboot your system for the setting to take effect.

WARNING: When you are editing these critical system files in Linux, be absolutely sure of WHAT you are editing. One SINGLE MISTAKE can render the whole system non-bootable. These are as dangerous as (if not more) Windows Registry. So there...

* Default runlevel. The runlevels used by RHS are:
* 0 - halt (Do NOT set initdefault to this)
* 1 - Single user mode
* 2 - Multiuser, without NFS (The same as 3, if you do not have networking)
* 3 - Full multiuser mode
* 4 - unused
* 5 - X11
* 6 - reboot (Do NOT set initdefault to this)

== Automatic Login ==

If you want a specified user to login (if you are using MythTV or some other app which requires the X Server) then please do so with [http://wiki.amahi.org/index.php/VNC these instructions].

Cheers!

The Amahi Team

File:Adminerss.png

2011-08-08T07:29:21Z

Bk: uploaded a new version of "File:Adminerss.png"

File:Adminerss.png

2011-08-08T07:28:51Z

Bk: uploaded a new version of "File:Adminerss.png"

File:Adminerss.png

2011-08-08T07:26:01Z

Bk: uploaded a new version of "File:Adminerss.png"

Self-install-existing

2011-06-30T21:58:35Z

Bk:

= Installation in an existing Fedora machine =

'''NOTE:''' this is '''NOT''' a recommended method to install, unless it's done on a fairly clean install of the distribution. The reason is that some things that may have been done to the machine that may affect the way Amahi behaves. The recommended method is doing it [[self-install|from scratch]].

It is important to note that, '''Amahi cannot be fully uninstalled''' in the traditional sense, because the settings affect some subsystems across the machine and the original state of those subsystems is not preserved.

Regardless, here are the install instructions, all of them executed [[Open Terminal as root|as root]].

----------
== Fedora 14 ==
* *DO NOT INSTALL UPDATES*
* Installed standard Fedora 14, but did not add the Amahi repository.
1. Create '''/etc/yum.repos.d/amahi.repo''' as '''root''' user and include following text:
[amahi]
name=Amahi repository for Fedora $releasever
baseurl=<nowiki>http://f$releasever.amahi.org/</nowiki>
gpgcheck=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-amahi
2. We must tell it to use the Amahi repo:
yum clean all
3. Lets make sure its working (Answer '''NO''', we do not want to update all):
yum update
4. Install the Amahi pieces and dependencies (173MB/65 packages; Answer '''YES'''):
yum install hda-suite
* Installer takes a few minutes to download the packages.
* A Warning about GPG keys appears after download, answer '''YES''' here:
<div style="border: 1px solid; padding: .5em 1em; background-color: #ffffcc; margin: 0 1em;">
...
(64/65): samba-3.5.6-69.fc14.i686.rpm | 5.0 MB 00:03
(65/65): wol-0.7.1-4.fc12.i686.rpm | 38 kB 00:00
-------------------------------------------------------------------------------------------------------
Total 253 kB/s | 56 MB 03:48
warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 Signature, key ID 97a1071f: NOKEY
fedora/gpgkey | 3.2 kB 00:00
...
Importing GPG key 0x97A1071F:
Userid : Fedora (14) <fedora@fedoraproject.org>
Package: fedora-release-14-1.noarch (@anaconda-InstallationRepo-201010211814.i386)
From : /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-i386
Is this ok [y/N]:
</div>
* Install takes a few minutes, ends with a ''Complete!'' message.
* Update dhclient:
yum -y update dhclient
* Start the Amahi web installer:
service amahi-installer start
* Goto: http://localhost:2000 to complete install. You can get your Install Code by logging into http://amahi.org and going to your control panel.

------------

== Fedora 12 ==
1. Install the hda-release
rpm -Uvh <latest_rpm repo="amahi-f12" rpm="hda-release" arch="noarch" output="url" />
2. Install hdactl (64 or 32bit)
* 32bit
rpm -Uvh --nodeps <latest_rpm repo="amahi-f12" rpm="hdactl" arch="i386" output="url" />
* 64bit
rpm -Uvh --nodeps <latest_rpm repo="amahi-f12" rpm="hdactl" arch="x86_64" output="url" />
3. Now install <code>hda-platform</code>
rpm -Uvh --nodeps <latest_rpm repo="amahi-f12" rpm="hda-platform" arch="noarch" output="url" />
4. Install dependencies:
yum -y install rubygems ruby-libs ruby-mysql
5. Start the Amahi installer.
service amahi-installer start
6. And last but not least, get the installer going by accessing it with a browser at <nowiki>http://localhost:2000</nowiki>

'''NOTE:''' If after starting the install via the web interface (<nowiki>http://localhost:2000</nowiki>) you accidently kill the terminal window in which you started the 'service ' from, it does appear to complete OK.

From time to time this method may miss some dependencies. At the end, try this as root:
rpm -Va --nofiles

In both cases,
* Replace '''YOURINSTALLCODE''' with your install code, obviously
* [http://bugs.amahi.org Report bugs in the platform category]!
* Save the output and paste it to the bug report.

Self-install-existing

2011-06-30T21:57:52Z

Bk:

= Installation in an existing Fedora machine =

'''NOTE:''' this is '''NOT''' a recommended method to install, unless it's done on a fairly clean install of the distribution. The reason is that some things that may have been done to the machine that may affect the way Amahi behaves. The recommended method is doing it [[self-install|from scratch]].

It is important to note that, '''Amahi cannot be fully uninstalled''' in the traditional sense, because the settings affect some subsystems across the machine and the original state of those subsystems is not preserved.

Regardless, here are the install instructions, all of them executed [[Open Terminal as root|as root]].

----------
== Fedora 14 ==
* *DO NOT INSTALL UPDATES*
* Installed standard Fedora 14, but did not add the Amahi repository.
1. Create '''/etc/yum.repos.d/amahi.repo''' as '''root''' user and include following text:
[amahi]
name=Amahi repository for Fedora $releasever
baseurl=<nowiki>http://f$releasever.amahi.org/</nowiki>
gpgcheck=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-amahi
2. We must tell it to use the Amahi repo:
yum clean all
3. Lets make sure its working (Answer '''NO''', we do not want to update all):
yum update
4. Install the Amahi pieces and dependencies (173MB/65 packages; Answer '''YES'''):
yum install hda-suite
* Installer takes a few minutes to download the packages.
* A Warning about GPG keys appears after download, answer '''YES''' here:
<div style="border: 1px solid; padding: .5em 1em; background-color: #ffffcc; margin: 0 1em;">
...
(64/65): samba-3.5.6-69.fc14.i686.rpm | 5.0 MB 00:03
(65/65): wol-0.7.1-4.fc12.i686.rpm | 38 kB 00:00
-------------------------------------------------------------------------------------------------------
Total 253 kB/s | 56 MB 03:48
warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 Signature, key ID 97a1071f: NOKEY
fedora/gpgkey | 3.2 kB 00:00
...
Importing GPG key 0x97A1071F:
Userid : Fedora (14) <fedora@fedoraproject.org>
Package: fedora-release-14-1.noarch (@anaconda-InstallationRepo-201010211814.i386)
From : /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-i386
Is this ok [y/N]:
</div>
* Install takes a few minutes, ends with a ''Complete!'' message.
* Update dhclient: yum -y update dhclient
* Start the Amahi web installer:
service amahi-installer start
* Goto: http://localhost:2000 to complete install. You can get your Install Code by logging into http://amahi.org and going to your control panel.

------------

== Fedora 12 ==
1. Install the hda-release
rpm -Uvh <latest_rpm repo="amahi-f12" rpm="hda-release" arch="noarch" output="url" />
2. Install hdactl (64 or 32bit)
* 32bit
rpm -Uvh --nodeps <latest_rpm repo="amahi-f12" rpm="hdactl" arch="i386" output="url" />
* 64bit
rpm -Uvh --nodeps <latest_rpm repo="amahi-f12" rpm="hdactl" arch="x86_64" output="url" />
3. Now install <code>hda-platform</code>
rpm -Uvh --nodeps <latest_rpm repo="amahi-f12" rpm="hda-platform" arch="noarch" output="url" />
4. Install dependencies:
yum -y install rubygems ruby-libs ruby-mysql
5. Start the Amahi installer.
service amahi-installer start
6. And last but not least, get the installer going by accessing it with a browser at <nowiki>http://localhost:2000</nowiki>

'''NOTE:''' If after starting the install via the web interface (<nowiki>http://localhost:2000</nowiki>) you accidently kill the terminal window in which you started the 'service ' from, it does appear to complete OK.

From time to time this method may miss some dependencies. At the end, try this as root:
rpm -Va --nofiles

In both cases,
* Replace '''YOURINSTALLCODE''' with your install code, obviously
* [http://bugs.amahi.org Report bugs in the platform category]!
* Save the output and paste it to the bug report.

PhpVirtualBox

2011-04-18T23:56:44Z

Bk:

[[category:apps]]
[http://www.amahi.org/apps/phpvirtualbox phpVirtualBox] has been packaged for Amahi and is currently in ''ALPHA'' testing.

==== How to Install Manually: ====
* Ensure '''''Advanced Settings''''' is be enabled on your HDA. This can be done via the '''''Settings''''' tab in the Amahi Dashboard.
* Navigate to the Amahi '''''Applications tab''''', create a web app called '''phpvb'''.
* Become '''root''' user:
{{Code|su -}}
* Install dependency:
{{Code|yum -y install php-soap}}
* Download and extract the source file:
{{Code|cd /var/hda/web-apps/phpvb
wget <nowiki>http://phpvirtualbox.googlecode.com/files/phpvirtualbox-4.0-5.zip</nowiki>
unzip phpvirtualbox-4-0-5.zip
mv phpvirtualbox-4-0-5/* html
chown -R apache:users html}}
* Edit '''''/var/hda/web-apps/phpvb/html/config.php''''' and change the values below to your user name and password (must be the same user name as added to the ''vboxusers'' group during VirtualBox install):
var $username = 'ian';
var $password = 'pass';
* Start Web Service:
{{Code|/usr/bin/vboxwebsrv -b --logfile /dev/null >/dev/null}}

* Enable Web Service start on boot:
Exit '''root''' user and edit crontab for your user (''whoami'' will display the current user name and must match the one in the previous step):
{{Code|whoami
crontab -e}}
and add the following line. (to save, enter ''':''' followed by '''wq'''):
{{Text|Text=@reboot /usr/bin/vboxwebsrv -b --logfile /dev/null >/dev/null}}

* Create Web Service daemon (this will allow start/stop for updating VirutalBox versions):
As '''root''' user, create the file '''''/etc/init.d/vboxwebsrv''''' and add the following (ensure you replace ''username'' on line 6 with the same user name as added to the ''vboxusers'' group during VirtualBox install):
#! /bin/sh
PATH=/usr/sbin:/usr/bin:/sbin:/bin
DESC="VirtualBox Web Service"
NAME=vboxwebsrv
SCRIPTNAME=/etc/init.d/$NAME
USER=username
[ -r /etc/default/$NAME ] && . /etc/default/$NAME
[ -f /etc/default/rcS ] && . /etc/default/rcS
. /etc/rc.d/init.d/functions
VBPID=`ps -U ${USER} --no-heading -o pid,cmd | grep vboxwebsrv | grep -v ${SCRIPTNAME} | grep -v grep | tail -1 | awk '{ print $1 }'`
do_start()
{
if [ "$VBPID" != "" ] && [ "$VBPID" -gt 0 ]; then
echo $NAME already running with PID $VBPID
else
su ${USER} -c 'vboxwebsrv -b --logfile /dev/null >/dev/null'
fi
}
do_stop()
{
if [ "$VBPID" != "" ] && [ "$VBPID" -gt 0 ]; then
echo Stopping $NAME ...
kill $VBPID
else
echo $NAME not running
fi
}
do_status()
{
if [ "$VBPID" != "" ] && [ "$VBPID" -gt 0 ]; then
echo Running with pid $VBPID
else
echo $NAME not running
fi
}
case "$1" in
start)
[ "$VERBOSE" != no ] && echo "Starting $DESC" "$NAME"
do_start
;;
stop)
[ "$VERBOSE" != no ] && echo "Stopping $DESC" "$NAME"
do_stop
;;
restart|force-reload)
echo "Restarting $DESC" "$NAME"
do_stop
sleep 1
VBPID=0
echo Starting $NAME ...
do_start
;;
status)
do_status
;;
*)
echo "Usage: $SCRIPTNAME {start|stop|restart|force-reload|status}" >&2
exit 3
;;
esac
Set permissions:
{{Code|chmod 755 /etc/init.d/vboxwebsrv}}
To use the service, do the following as '''root''' user (option: start, stop, restart, force-reload, status):
{{Code|service vboxwebsrv option}}
* That's it. You should now be able to access VirtualBox from your browser at <nowiki>http://phpvb</nowiki>. It will restart automatically on reboot as well. Be aware moving the mouse pointer in this app is quirky and often difficult to navigate.
* Refer to [http://code.google.com/p/phpvirtualbox/wiki/Installation phpVirtualBox Installation] for additional guidance.

'''NOTE:''' See [[Amahi_on_VirtualBox|Amahi on VirtualBox]] for detailed guidance on installing Amahi on a virtual machine (VM).

File:Ams.png

2011-04-17T19:57:33Z

Bk: uploaded a new version of "File:Ams.png"

Amahi Mail System Logo

App release process

2011-04-15T23:26:40Z

Bk:

Applications for Amahi have a release process as they progress to full release. Each app has a support status in one or more Amahi platforms (Fedora 9, Fedora 10, 12, and 14, and eventually Ubuntu/Debian, etc.)

The application page lists the status of the application for each platform. Here are the states:

* Alpha (red): when an application is created, it's in Alpha. Only the user who packaged this app can see it and install it.
* Beta (Orange): when an app reaches Beta it has to be installable (and uninstallable) at a minimum and it can only be seen by the group of users in the [[Tester program]] or users that have signed up for the Pro and Ninja plans. Find out more on the [http://www.amahi.org/plans Plans Page]
* Live (Green): when an app is well tested and suited for every new user, it goes live and it should work for everyone

Here is a sample of an app in Alpha on Fedora 9, in Beta for Fedora 10 and Live in Fedora 12 and 14:

[[Image:app-status.png]]

App release process

2011-04-15T23:22:50Z

Bk:

Applications for Amahi have a release process as they progress to full release. Each app has a support status in one or more Amahi platforms (Fedora 9, Fedora 10, 12, and 14, and eventually Ubuntu/Debian, etc.)

The application page lists the status of the application for each platform. Here are the states:

* Alpha (red): when an application is created, it's in Alpha. Only the user who packaged this app can see it and install it.
* Beta (Orange): when an app reaches Beta it has to be installable (and uninstallable) at a minimum and it can only be seen by the group of users in the [[Tester program]]
* Live (Green): when an app is well tested and suited for every new user, it goes live and it should work for everyone

Here is a sample of an app in Alpha on Fedora 9, in Beta for Fedora 10 and Live in Fedora 12 and 14:

[[Image:app-status.png]]

App release process

2011-04-15T23:22:07Z

Bk:

Applications for Amahi have a release process as they progress to full release. Each app has a support status in one or more Amahi platforms (Fedora 9, Fedora 10, 12, and 14, and eventually Ubuntu/Debian, etc.)

The application page lists the status of the application for each platform. Here are the states:

* Alpha (red): when an application is created, it's in Alpha. Only the user who packaged this app can see it and install it.
* Beta (Orange): when an app reaches Beta it has to be installable (and uninstallable) at a minimum and it can only be seen by the group of users in the [[Testers program]]
* Live (Green): when an app is well tested and suited for every new user, it goes live and it should work for everyone

Here is a sample of an app in Alpha on Fedora 9, in Beta for Fedora 10 and Live in Fedora 12 and 14:

[[Image:app-status.png]]

App release process

2011-04-15T23:21:36Z

Bk:

Applications for Amahi have a release process as they progress to full release. Each app has a support status in one or more Amahi platforms (Fedora 9, Fedora 10 or 12, and eventually Ubuntu 910, etc.)

The application page lists the status of the application for each platform. Here are the states:

* Alpha (red): when an application is created, it's in Alpha. Only the user who packaged this app can see it and install it.
* Beta (Orange): when an app reaches Beta it has to be installable (and uninstallable) at a minimum and it can only be seen by the group of users in the [[Testers program]]
* Live (Green): when an app is well tested and suited for every new user, it goes live and it should work for everyone

Here is a sample of an app in Alpha on Fedora 9, in Beta for Fedora 10 and Live in Fedora 12 and 14:

[[Image:app-status.png]]

File:App-status.png

2011-04-15T23:20:44Z

Bk: uploaded a new version of "File:App-status.png"

IRC Rules and Tips

2011-04-15T06:41:20Z

Bk:

* The usual civility rules of IRC apply
* Keep the good vibe, be polite and to the topic
* For anything longer than three lines, please use fpaste http://fpaste.org/ , you can also use fpaste from the command line in Fedora using the command "fpaste".
* For screenshots, you can use http://www.imgur.com or http://www.uploadscreenshot.com
* You may want to search the [http://www.amahi.org/faq Amahi FAQ] for basic questions
* Remember, for debugging, details matter. Be as precise as possible!
* For specific problems that require a good description, the [http://forums.amahi.org Amahi Forums] are probably best. Post the specifics there and discuss in IRC.
* The [http://wiki.amahi.org Amahi Wiki] is another great resource. Remember you can contribute too, enhancing or creating new guides.
* Post all bugs and feature request on the [http://bugs.amahi.org Bug Tracker] under the respective project.
* Command and control the [[IRC Bot | AmahiBot]]

'''Note''': While we try to respond promptly to whatever questions you may come in with, please keep in mind that we can’t always respond ''instantaneously.'' So please, stick around for a little while and give us a chance to realize there’s channel activity before you give up.

'''DO NOT MESSAGE A USER FOR HELP, ALL HELP IS TO BE DONE IN THE CHANNEL'''

==IRC Channels==
* Amahi General Discussion and Support: [http://webchat.freenode.net/?channels=amahi #amahi]
* Amahi Pro/Ninja and Paid App Support: [http://webchat.freenode.net/?channels=amahi-support #amahi-support]
* Amahi on Debian/Ubuntu: [http://webchat.freenode.net/?channels=amahi-debian #amahi-debian]

However, if we really all do seem asleep, feel free to ask your question over on the [http://forums.amahi.org forums].

Debian/Apps

2011-04-14T22:56:45Z

Bk:

=Apps on Debian=

==Apps that work==
* SpeedTest.net MINI
* Hello World
* phpSysInfo
* WikkaWiki
* Adminer
* WordPress
* phpBB

==Apps that DO NOT work==
* phpMan
* SheevaTheme (because it installs via yum)
* MediaTomb-Debian (see http://bugs.amahi.org/issues/show/809 )

Debian/Apps

2011-04-13T21:36:40Z

Bk:

=Apps on Debian=

==Apps that work==
* SpeedTest.net MINI
* helloworld
* phpsysinfo
* WikkaWiki
* Adminer
* WordPress

==Apps that DO NOT work==
* phpBB
* phpMan
* SheevaTheme (because it installs via yum)

Debian/Apps

2011-04-13T21:30:54Z

Bk:

=Apps on Debian=

==Apps that work==
* SpeedTest.net MINI

==Apps that DO NOT work==
* phpBB

Debian/Apps

2011-04-13T21:29:44Z

Bk: Created page with "==Apps on Debian== =Apps that work= * SpeedTest.net MINI =Apps that DO NOT work= * phpBB"

==Apps on Debian==

=Apps that work=
* SpeedTest.net MINI

=Apps that DO NOT work=
* phpBB

IRC Rules and Tips

2011-04-10T21:01:39Z

Bk:

* The usual civility rules of IRC apply
* Keep the good vibe, be polite and to the topic
* For anything longer than three lines, please use fpaste http://fpaste.org/ , you can also use fpaste from the command line in Fedora using the command "fpaste".
* For screenshots, you can use http://www.imgur.com
* or you can use http://www.uploadscreenshot.com
* You may want to search the [http://www.amahi.org/faq Amahi FAQ] for basic questions
* Remember, for debugging, details matter. Be as precise as possible!
* For specific problems that require a good description, the [http://forums.amahi.org Amahi Forums] are probably best. Post the specifics there and discuss in IRC.
* The [http://wiki.amahi.org Amahi Wiki] is another great resource. Remember you can contribute too, enhancing or creating new guides.
* Post all bugs and feature request on the [http://bugs.amahi.org Bug Tracker] under the respective project.
* Command and control the [[IRC Bot | AmahiBot]]

'''Note''': While we try to respond promptly to whatever questions you may come in with, please keep in mind that we can’t always respond ''instantaneously.'' So please, stick around for a little while and give us a chance to realize there’s channel activity before you give up.

'''DO NOT MESSAGE A USER FOR HELP, ALL HELP IS TO BE DONE IN THE CHANNEL'''

However, if we really all do seem asleep, feel free to ask your question over on the [http://forums.amahi.org forums].

IRC Bot

2011-04-03T18:19:53Z

Bk:

The IRC Bot, AmahiBot is a Mathetes (http://github.com/Pistos/Mathetes) bot run by Brandon, AKA bk, that sits in the #amahi channel on IRC.

Don't be shy using it - the bot has no soul or emotions!

AmahiBot has a few interesting and useful functions.

=Amahi Specific=

==Amahi.org==
Search amahi.org by using the following command:
<pre>!sa <search terms></pre>

==Wiki==
To call a wiki article do the following:
<pre>!w <Article></pre>
or to search the wiki use the following command:
<pre>!sw <search terms></pre>

==Forums==
To search the forums do the following:
<pre>!sf <search terms></pre>

==Apps==
To search for an application in the appstore do the follwing:
<pre>!a <app name or keyword></pre>
or
<pre>!app <app name or keyword></pre>

==Bugs==
You can call up bugs from the Amahi bug tracker by saying:
<pre>!bug BUG#</pre>
Or search for a bug by doing the following:
<pre>!sb <search terms></pre>

Bugs are also posted automatically to the channel when they are created.

==Google==
Any of the following commands will search Google and return the results + URLs.
<pre>!google <define:|spell:> <search terms> <1+1> <1 cm in ft> <patent > <weather city|zip> <??? airport> <city,state/zip></pre>
<pre>!images <search terms></pre>
<pre>!groups <search terms></pre>

=Factoids=
You can store factoids for later with the following command:
<pre>! NAME=DESCRIPTION</pre>
and then recall the fact by saying <pre>! NAME</pre>

=Memo=
To leave a memo for a user that is no here run the following command
<pre>!memo USERNAME MemoForUser</pre>

=Seen=
Say <pre>!seen USERNAME</pre> to find the last time that the user was in the channel.

=Pun=
To get the bot to say a pun, do the following:
<pre>!pun</pre>

=Time (currently broken)=
Use the following command to call the time:
<pre>!time</pre>
Default time is in UTC, to call a different timezone do the following:
<pre>!time <timezone></pre>

=Translate=
The bot can translate text for you if you need it, translate by doing the following:
<pre>!translate <current lang (ie. es)> <to lang (ie. en)> <text to translate></pre>

=Down for Me=
You can check to see if a website is down or not by issuing the following command:
<pre>!up site.url</pre>

=Feedback=
And dont forget, leave us some [[IRCBot/Feedback | feedback]]!

IRC Bot Old

2011-04-03T18:19:07Z

Bk: Created page with "<div style="color:darkred; background: #f8e6e6; border: 1px solid #aa0000; padding: 1em; margin: 1em 3em">'''We have a new bot, please visit IRCBot for the new bot's commands..."

<div style="color:darkred; background: #f8e6e6; border: 1px solid #aa0000; padding: 1em; margin: 1em 3em">'''We have a new bot, please visit [[IRCBot]] for the new bot's commands and features'''</div>

The IRC Bot, AmahiBot is a eggdrop bot run by Guillaume Boudreau, AKA Mouton, that sits in the #amahi channel on IRC.

Don't be shy using it - the bot has no soul or emotions!

==Functions==
AmahiBot has a few interesting and useful functions

==Amahi Wiki Articles==
<pre>!wiki Wiki Article Name</pre> will return a wiki link for this wiki

==Amahi-specific Google Searches==

The following with launch a Google search restricted to ''site:wiki.amahi.org''.
<pre>!gw <search terms></pre>

The following with launch a Google search restricted to ''site:forums.amahi.org''.
<pre>!gf <search terms></pre>

The following with launch a Google search restricted to ''site:amahi.org''.
<pre>!ga <search terms></pre>

Any of the following commands will search Google and return the results + URLs.
<pre>!google <define:|spell:> <search terms> <1+1> <1 cm in ft> <patent > <weather city|zip> <??? airport> <city,state/zip></pre>
<pre>!images <search terms></pre>
<pre>!groups <search terms></pre>

==Bug lookup==
You can look up bugs from the Amahi bug tracker by saying:
<pre>!bug BUG_NUMBER</pre>

==Factoids==
You can store factoids for later with the following command:
<pre>!add NAME DESCRIPTION</pre>
and then recall the fact by saying <pre>? NAME</pre> or delete the fact by saying <pre>!del NAME</pre>

To list all available commands say <pre>!stored</pre>

==Twitter Feed==
Saying <pre>!twitter</pre> in the channel will show you the last twitter message posted to twitter.com/amahi

==GetSatisfaction Feed==
Saying <pre>!gs</pre> in the channel will show you the last topic posted to getsatisfaction.com/amahi

==Seen==
Say <pre>!seen USERNAME</pre> to find the last time that the user was in the channel

Mount Shares Locally

2011-03-27T00:48:48Z

Bk:

Mounting your Samba shares locally is useful when you are using Greyhole, and want to write or in any way work with those files locally. Greyhole data should only be accessed through shares, so mounting those shares locally is an easy way to work with Greyhole data safely.

* Install the mount_shares_locally initd script:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; overflow: scroll">
curl -o /etc/init.d/mount_shares_locally http://dl.dropbox.com/u/3022105/Amahi/mount_shares_locally
chmod +x /etc/init.d/mount_shares_locally
chkconfig --add mount_shares_locally
</div>

* Edit /etc/init.d/mount_shares_locally (as user root) in a text editor, and replace ''your_username'' (on line 12) with your username.

* Create the ''/home/your_username/.smb_credentials'' file. This is a simple text file (use your favorite text editor).
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
username=your_username
password=your_password
domain=HOME
</div>

To test your new mounts, you can execute '''service mount_shares_locally start'''<br/>
You will find the mounted shares in ''/mnt/samba/*''<br/>
'''service mount_shares_locally stop''' will unmount the local shares.<br/>

Note: if you used /etc/rc.local and /etc/fstab to mount shares locally in the past, you can remove what you added in those files now. The above initd script replaces all this.

== Unable to mount localy after upgrading to Amahi6 ==
If you try to run mount using this script after you upgraded to Amahi6 you might get greeted by this type of error.

[root@localhost ~]# /etc/init.d/mount_shares_locally start
Mounting Samba shares locally: /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
[ OK ]

It's easily fixed by installing the missing dependency.

{{Code|yum install cifs-utils}}

Now it should work fine to run

{{Code|/etc/init.d/mount_shares_locally start}}

Template:MessageBox

2011-03-26T19:35:14Z

Bk:

{| align=center style="background: {{{backgroundcolor}}}; border: 2px solid #aa0000; padding: .2em;width: 60%;"
!rowspan="2" style="text-align:center"|[[Image:{{{image}}}|50px|link=]]
! width=75% style="text-align:center;font-size:large;font-weight: bold" | '''{{{heading}}}'''
|-
!style="text-align:center; font-size:small;font-weight: normal"|{{{message}}}
|}

<noinclude>
This is a generic message box that can be used in several cases like a
warning or information
</noinclude>

File:Msgbox.update.png

2011-03-19T12:25:19Z

Bk: uploaded a new version of "File:Msgbox.update.png"

VPNMacViscosity

2011-03-19T11:52:02Z

Bk:

== Mac VPN Client - Viscosity ==

There is a Mac OS X VPN client for OpenVPN called [http://www.viscosityvpn.com/ Viscosity].

It appears to work well with Amahi. The beta is free (as in beer, not open source), and they appear to be planning a shareware approach for the 1.0 release.

== Configuration ==

* There are three .ctr/.key files needed (make sure you follow the links to these in this wiki properly) Right click and save as to save these to your computer:
** [http://dl.amahi.org/vpn/AmahiHDAClient.crt AmahiHDAClient.crt]
** [http://dl.amahi.org/vpn/AmahiHDAClient.key AmahiHDAClient.key]
** [http://dl.amahi.org/vpn/ca-cert.crt ca-cert.crt]
* Download the .ctr/.key files and save them anywhere you want, Viscosity will rename and resave these files.
* Open Viscosity from the Applications folder. You will now see [[Image:Viscosity.png]].
* Click on the [[Image:Viscosity.png]]
* Click on "Preferences" when the drop down appears. <br />
[[Image:Setupviscosity.png]]
* Under "Preferences" you need to click on the + icon and add a new connection. <br />
[[Image:Newconnviscosity.png]]
* A new connection screen will open up, in the General tab you need to setup the name of this connection (I chose Amahi), then enter your VPN address (youruser.yourhda.com), all other settings are correct by default.
[[Image:Generalviscosity.png]]
* Next you need to go to the Authentication tab, select "Use Username/Password authentication" and then add the .crt/.key files in their respective slots as shown in the image below.
[[Image:Authenticationviscosity.png]]
* After you fill out the "Authentication" tab, everything else is complete and optional, so click save when you are done.
* Next you will need to connect to this connection by clicking on the Amahi (or whatever you named it) connection under [[Image:Viscosity.png]]<br />
[[Image:Connectviscosity.png]]
* Now you are complete :) Have fun.

Note:
* The procedure above has been tested with an Intel-based Mac.

[[Category: VPN]]

File:Viscosity.png

2011-03-19T11:33:42Z

Bk: uploaded a new version of "File:Viscosity.png"

File:Viscosity.png

2011-03-19T11:32:14Z

Bk:

File:Setupviscosity.png

2011-03-19T11:31:30Z

Bk:

File:Newconnviscosity.png

2011-03-19T11:31:14Z

Bk:

File:Generalviscosity.png

2011-03-19T11:31:01Z

Bk:

File:Connectviscosity.png

2011-03-19T11:30:41Z

Bk:

File:Authenticationviscosity.png

2011-03-19T11:30:13Z

Bk:

IRC Bot

2011-03-19T11:05:12Z

Bk:

Main Page

2011-03-19T10:59:54Z

Bk:

=Welcome to the Amahi Wiki=
<big>
'''CURRENT STABLE RELEASE:''' [[Amahi 6.0]], on [[Fedora 14]]'''
</big>

----

__TOC__<br />
This is where Amahi community members can best help other Amahi users. Please add or edit any information in the Wiki that you feel is lacking, missing, or need improvement.

----

* [[Intro]]: Introduction to the Amahi HDA
* [[Requirements]]: What's needed
* [http://www.amahi.org/faq FAQ]: Frequently Asked Questions
* [[Feedback]]: Issues, feedback.

For questions or help do not hesitate to [[contact us]].

= Installation =
* See [http://www.amahi.org/support/instructions Installation instructions] in your control panel at amahi.org
* [[Self-install]]: Alternative, unsupported installation instructions
* [[Amahi on a VM]]: Installing Amahi in a Virtual Machine
* [[Express CD]]: Headless all-in-one Install

=Getting Started=

First you can take a look at the [[Special:PopularPages|Popular Pages]] to see if your topic of interest is there. Otherwise find the major topics below in groups.

'''[[Storage and file sharing]]''' - How to store your music, pictures, movies and other files and share them with the rest of the devices in your network.
* Accessing files from:
#[[SharingToMacOSX|Mac OS X]]
#[[SharingToLinux|Other Linux Systems]]

'''Networking''' - Using your HDA to manage your home network
* [[Networking - Static IPs]]: How to assign static IPs to your network devices.
* [[Punching DNS Holes]]: How to assign IP addresses outside of your network for your home domain.

'''Remote Access''' - Accessing your HDA from anywhere on the network
* Accessing your HDA remotely from:
# [[VPN]]: '''outside''' your network.
# [[VNC]]: '''inside''' your network (e.g. if your HDA is "headless").
* [[FreeNX]]: Accessing your HDA with FreeNX
* SSH based access to your HDA: [[Key-Based SSH Logins]]

= Troubleshooting =
* [[Installation troubleshooting]]
* [[Network troubleshooting]]
* [[Shares troubleshooting]]
* [[VPN troubleshooting]]
* [[Vista Networking Issue]]
* [[Disabling Automatic Updates]]
* [[Data Recovery]]

=Doing More=
* '''[[:Category:Apps|Apps Directory]]:''' These are the help pages for some of the apps in the [http://www.amahi.org/apps/ Apps Gallery]
* [[Adding an HDA networked printer]]: Guide to set up print server on your HDA.
* [[Backups]]: Guides on backup and restore: [[XPBackups|Windows XP]], [[VistaWindows7Backups|Windows Vista and Windows 7]], [[Sbackup|Ubuntu Linux]], and [[Backups#Mac_OS_X|MacOSX]].
* [[Adding a second hard drive to your HDA]]: How to add a additional hard drives.
* [[Greyhole]]: Add drive pooling to your HDA (ie Turn multiple drives into one!)
* [[RAID]] guides for [[RAID 1]] and [[RAID 5]]
* [[DropBox|Add DropBox service]]: Allows a HDA DropBox share folder to automatically synchronize with a DropBox account.
* [[Database_Backup|Automatic Database Backup]]: Automatically have your HDA database backed up daily.
* [[Enable_Outgoing_Emails|Enable Outgoing Mail]]: Use your ISP to send mail from your HDA.
* [[Monitor System Logs via E-mail]]: Sends logs to designated e-mail address daily.
* [[Outgoing_mail_via_gmail|Send Outgoing Emails via Gmail]]: Use your Gmail account to send mail from your HDA.

=Using Applications=
For a more detailed list refer to the '''[[:Category:Apps|Apps Directory]]'''
* Remote File Management using [http://www.amahi.org/apps/ajaxplorer AjaxPlorer]
* [[Calendars]]: How to use the calendar server in the HDA, including Outlook and iCal sync.
* [[Dashboard_Design|Dashboard]]: Using the amahi Dashboard

=Getting "Under the Hood"=
* [[Password protection for your HDA setup pages]]: Guide to set up password protection to your HDA pages.
* [[How to Create a new Theme]]
* [[Linux-hda_commands|Linux/HDA Commands]]: Common used command for linux and HDA.
* [[Webapps | Making your own web apps]]: how to make your own web apps, with your code or other's code
* [[Hosting a website | Hosting your own web site]]: how to host your own web site on the web from your Amahi home server
* [[Changing your DNS provider]]
* [[Configuring OpenDNS]]
* [[How_to_use_two_HDA_on_the_same_network| Use two HDAs on same network]]

=Contribute=
* [[Translate Amahi]] to your language
* [http://bugs.amahi.org Create a Bug/Feature/Support ticket!]
* Contribute by:
# [[Contribute|Packaging apps]]
# [[Tester program|Testing apps]]
* [http://www.flickr.com/photos/amahi/sets/72157606815797764/ Amahi Wallpapers]
* [http://www.flickr.com/photos/amahi/sets/72157606828513620/ Amahi Banners]

= Roadmap & Development =
* [[Fedora 14]]: Current Stable Release
* [[Ubuntu]]: Limited Development
* [[CentOS]]: Development Stalled

= Related Links =
* [[Developers]]: How to write HDA apps, questions, API suggestions, etc.
* [[Credits]]: How are we doing all this? We have many OSS projects to thank!

Hosting a website

2011-03-18T14:43:10Z

Bk:

*To access the HDA itself from outside the network using VPN, check out the [[Adito]] application, available to install through the HDA. Adito enables you to access the HDA, and all applications and folders, using just your free username.yourhda.com webaddress.

So you want to run a web server in your Amahi server and make it visible from the web outside your home.

<div style="border: 1px solid #B66; padding: .5em 1em; color: #000; background-color: #FEE; margin: 3px 3px 1em 3px;">
'''NOTICE: making anything visible outside your network can open security issues, so you are doing this at your own risk. Some apps are more secure than others, but there is nothing ultimately secure. Best is to use the [[VPN]] to login back home.
</div>

== Requirements ==
For the purposes of this guide you need either of the following:

* [[VNC]] access to your HDA if headless
** ''Terminal is available under Applications -> System Tools -> Terminal''
* [http://www.amahi.org/apps/ajaxterm Ajaxterm] if headless and no VNC
* A monitor if you are not headless

To host your own web site you need the following:

* Forward a port to your HDA ip address, either for plain insecure http: 80, for https, 443 (advanced users can use other ports). Some routers call this or require a "virtual server"
* Chose a domain name that you own (or your free username.yourhda.com that comes with Amahi). This is how the app will be accessed outside
* Chose the app you want to make accessible outside, let's say, '''yourwebappname'''

== Hosting a single Webapp ==

What you need to do in a terminal (as root) is find the apps conf file then edit the conf file for the app:
{{Code|
Code=su
[enter password]
ls /etc/httpd/conf.d
}}
Find your app .conf file. It will look like 10##-yourwebappname.conf
{{Code|
Code=nano /etc/httpd/conf.d/10##-'''yourwebappname'''.conf
}}

Your conf file should look something like this at the top of the page:
{{Text|
<VirtualHost *:80>

ServerName app
ServerAlias app.YourDomain.lan
}}
Add this (immediately after the ServerName directive):
{{Text|
ServerAlias username.yourhda.com
}}
So it looks like this:
{{Text|
<VirtualHost *:80>

ServerName app
ServerAlias app.YourDomain.lan
ServerAlias username.yourhda.com
}}
You can add more server aliases if you want to access the app under those names (for example: ServerAlias myphotos.DomainName.com). Once you are satisfied with the server aliases, you may save and quit nano by following these steps in Windows:

ctrl X
At the prompt, type "y" to save
At the prompt, hit "Enter" to save the file

Restart the server using:
{{Code|
service httpd reload
}}
And you are done, enjoy your website.

== Hosting multiple Webapps ==

''If you wish to have access to multiple webapps, described below is one way to accomplish this:''

# obtain a domain name (i.e., via godaddy.com) --for example yourdomain.com
# for each web app you wish to have access to, establish a CNAME or subdomain--for example something.yourdomain.com---and point it to username.yourhda.com (for example see http://help.godaddy.com/article/679 )
# edit the webapp .conf file (see above) to match the CNAME/subdomain you just established by adding ServerAlias something.yourdomain.com
# don't forget to restart the server each time you edit a .conf file.

:#For example, you could create the subdomain/CNAME: address.yourdomain.com for the AddressBook webapp---point that subdomain to: username.yourhda.com---in the AddressBook .conf file add: ServerAlias address.yourdomain.com---restart the server---you are done, enjoy using multiple webapps!

== Hosting a Website ==

''Prerequisites'': The first order of business is to make sure that your domain name is pointing to your server's IP address. Each website is different, but GoDaddy goes like this:
:* Go to your GoDaddy's ''My Account'' page. Under Dashboard, click yourdomain.com
:** Point your cursor at the Nameserver icon, click ''Set Nameservers''
::: [[File:Nameserverlink.jpg|caption]]
:** Select ''I want to '''forward''' my domains'' and click OK
::: [[File:forwarddomainname.jpg|frameless|caption]]
:* Now go back to your account homepage, and instead of clicking yourdomain.com, check it and click ''View in Domain Manager''
:** Click yourdomain.com
:** Scroll down to '''DNS Manager''' and click ''Launch''
:::[[File:DNSmanagger.jpg|frameless|caption]]
:** Under '''A(Host)''' edit the IP Address(es) to reflect the IP Address of your server. Hit enter and then ''Save Zone File'' when that option appears.
:::[[File:ahostpointsto.jpg|frameless|caption]]
:* The effects should appear within one hour

''Hosting'': Hosting a website on your HDA server is basically the same as hosting a webapp, so if we are able to do the previous guides on hosting a webapp(s) the rest will be a cinch.

We will create the website by creating a webapp. This is a lot easier than it sounds, so don't give up just yet!
# Got your HDA page (http://hda or http://hda.yourhda.com), click ''Setup'' and go to ''Settings''.
## Make sure your ''Advanced Settings'' option is checked (if not, check and click OK past the warning)
# Go to ''Apps'' and then ''Webapps''
# At the very bottom, click ''New Web App'' and type in a name like Website
:This is where your webpage will reside in, you can name this anything you'd like. This is not the title of your website or webpage. Website will be used as the name for this guide
:::[[File:newebapp.jpg|frameless|caption]]
# Do everything as told under the "Hosting a single Webapp" heading above, but of course our app is called Website.
:''Hint:'' Instead of using user.yourhda.com for your ServerAlias, go ahead and use yourdomain.com ('''without the www.''') if you have one from, for example, GoDaddy.
# To easily access your website files, we will make the webapp folder a share by doing the following:
:* In your HDA Dashboard, click ''Setup'' and then ''Shares''
:* Click ''New Share'' at the very bottom
:* We will name our share Website
:** Notice that the path is automatically filled out for us. This is not the path that will be used, so the path that will be typed in will be ''/var/hda/web-apps/Website/''
:::[[File:newshare.jpg|frameless|caption]]
:* Click ''Create this Share'', now the folder will be available from your normal \\hda spot.
:** You can test your new website by creating an index.html (put something simple, like "hi", as a text) in the html folder in your Website share folder, and then going to yourdomain.com

And we are finished. To create your website on Fedora, we can use Bluefish program.
: yum install bluefish
If we would like to use Windows, we can use any program to make the website. Just drag and drop into the share, and under the folders as needed.

== FAQ ==

* Q: Do i need to do anything for <code>username.yourhda.com</code> to work?
No. That comes free and automatically set up with your Amahi HDA

* Q: What if i want to do it for a .html or .php file?
You can do this by creating a Webapp of your own. In the apps tab,
select Webapps and create a new one.
What you do is, create a web app, and put the files into the root
directory of the webap, something like this directory:

/var/hda/web-apps/'''yourwebappname'''/html

this directory belongs to apache. you will have to change the
ownership to your user (recommended) or otherwise add things as root.
* Q: How do I change the ownership?
You can do this by going to the command screen:

su -
{password}
chown {user} /var/hda/web-apps/