Amahi Wiki - User contributions [en]

Talk:Enhancing the testing program

2010-03-25T05:22:25Z

Anzenketh:

Please Click on the + Sign to add your comments and put your name for the subject line.

== Anzenketh ==

RE: On A Link to the list of known bugs.

It we might have to create a page to read the bug tracker mysql by category to do this.

RE: A link on how to report a bug for the application

This could be just a simple wiki page explaining how.

RE: A link to the upstream application (DONE - maybe make it more visible?)
I think the best place to put this is up by the application name.

RE:A better way to know the app status than currently color coding (Re: There needs to be known stages for that the application needs to go though and what states the application is in should also be noted)

Color coding is nice but is not helpful if you do not know what the color coding means.

RE: A "watch" button to an app to get notifications on the app progress/issues/news.

Basically it looks like we may have to write a application to work with the bug system and application system. It would also be nice to have the git repo if possible close bugs.

Talk:Enhancing the testing program

2010-03-25T05:21:21Z

Anzenketh: /* My ideas. */ new section

Please Click on the + Sign to add your comments.

== My ideas. ==

RE: On A Link to the list of known bugs.

It we might have to create a page to read the bug tracker mysql by category to do this.

RE: A link on how to report a bug for the application

This could be just a simple wiki page explaining how.

RE: A link to the upstream application (DONE - maybe make it more visible?)
I think the best place to put this is up by the application name.

RE:A better way to know the app status than currently color coding (Re: There needs to be known stages for that the application needs to go though and what states the application is in should also be noted)

Color coding is nice but is not helpful if you do not know what the color coding means.

RE: A "watch" button to an app to get notifications on the app progress/issues/news.

Basically it looks like we may have to write a application to work with the bug system and application system. It would also be nice to have the git repo if possible close bugs.

Talk:Enhancing the testing program

2010-03-25T05:21:02Z

Anzenketh: Replaced content with 'Please Click on the + Sign to add your comments.'

Please Click on the + Sign to add your comments.

Talk:Enhancing the testing program

2010-03-25T05:20:17Z

Anzenketh: Added Talk

RE: On A Link to the list of known bugs.

It we might have to create a page to read the bug tracker mysql by category to do this.

RE: A link on how to report a bug for the application

This could be just a simple wiki page explaining how.

RE: A link to the upstream application (DONE - maybe make it more visible?)
I think the best place to put this is up by the application name.

RE:A better way to know the app status than currently color coding (Re: There needs to be known stages for that the application needs to go though and what states the application is in should also be noted)

Color coding is nice but is not helpful if you do not know what the color coding means.

RE: A "watch" button to an app to get notifications on the app progress/issues/news.

Basically it looks like we may have to write a application to work with the bug system and application system. It would also be nice to have the git repo if possible close bugs.

Enhancing the testing program

2010-03-25T03:24:52Z

Anzenketh: Created page.

= Problem =

The current testing program does not work. People do not participate in it. That could be due people just are impatient and do not want to try the app or it is difficult to contribute back. We can not fix the people who just want to test a app and are not willing to provide feedback or testing. This can cause a issue of a application being released to early with bugs.

= Known Issues =
* SSO between wiki,fourms,and bug tracker do not work well.
* Bug Tracker is hard to find. (Yes I know it is bugs.amahi.org but for someone who does not guess that I there is not a static link.)

== Policy/ Procedure needed for it to work ==
= If you develop a wiki page for a policy please update this wiki with the link=

* There needs to be known stages for that the application needs to go though and what states the application is in should also be noted.

* Policy on what the application information page on the mainpage should contain.

* Policy on what tests a application must past to get included.

* Policy of of general testing procedures for most application.

* I know A lot of people hate policy. However there MUST to be policy for testing. There is a reason for ISO Certification. People like checklists if they don't have a checklist they do not know what to do. Each application should have a checklist of things actions someone needs to preform to make sure the application works.

* Furthermore said checklist MUST have a template for all apps on recommended things to include.

* Better use of the bug system. The bug system is great however we need to use it better. Each application should have at least its own category if not it's own subproject depending on the size and complexity of the application. This is so reports can be run on a specific application.

* Every application must have a place to discuss the application.

== There needs to be a good template for applications on the wiki. ==
The template MUST including the following information.
* The name of the application
* The Description of the application
* The Features of the application.
* The Status of the application. (Current Version and State ( Eg. HDA-ized app)
* Information on how to install the application.
* Information on how to uninstall the application.
* Information on how to configure the application.
* A link to the checklist for testing the application. This should be simple and easy to follow.
* A link to known bugs. (If every bug has it's own category if we can run a report on that category a link to that would be the best).
* Link to Upstream bug reporting system or support. Also we must include exception on what should not be forwarded upstream.

= The homepage for the application must contain more information =
* A link to the upstream application.(This is mostly for legal reasons).
* A Link to the list of known bugs.
* A link on how to report a bug for the application.
* A link to the place of discussion of the application.

UbuntuPorting

2010-03-24T08:34:48Z

Anzenketh: added known bugs and removed Architecture differences as they should be taken care of in the install files.

'''This page is being edited actively and a lot of sections are missing currently'''

=Current state=
We just started porting Amahi to Ubuntu. The support is highly experimental. There are a few important things to be fixed before you can run it with minimal tweaking. Please don't try it on a production server yet. We are using Ubuntu 9.04 (jaunty) Desktop 32 bit for development. We strongly recommend you to use the same for experiments. You can download this version from [http://www.ubuntu.com/getubuntu/download here].

=Requirements=
You may want to have two different installations of Ubuntu.
* A development platform, running Ubuntu 9.04 Desktop 32 bit and/or 64 bit with the recommended development packages installed.
* An Amahi sandbox, running Ubuntu 9.04 Desktop 32 bit '''preferably''' under [http://www.virtualbox.org/ VirtualBox].
Please don't install the Amahi packages on the development platform as this might break your networking.

=Setting up the development platform=
# Install Ubuntu 9.04 Desktop 32 bit.
# Install essential build toolchain.
## sudo apt-get update
## sudo apt-get install build-essential
## sudo apt-get install devscripts
## sudo apt-get install debhelper
## sudo apt-get install fakeroot
## sudo apt-get install lintian
# Install git. # sudo aptitude install git-core
# Read [https://wiki.ubuntu.com/PackagingGuide/Complete Ubuntu packaging guide] to get an idea of other additional packages that you may want to install to create Ubuntu packages. I will list the packages to make your part easier at a later point.

=Setting up the Amahi sandbox=
# Install [http://www.virtualbox.org/ Sun VirtualBox]. # sudo aptitude install virtualbox-ose
# Open VirtualBox and create a new guest platform for Ubuntu and install Ubuntu 9.04 Desktop 32 bit.
# Install VirtualBox guest additions in your Amahi sandbox.
# Setup VirtualBox folder sharing between your development platform and Amahi sandbox.

=Amahi source code=
On your development platform, download Amahi source code from our git repository. Follow these steps to build Ubuntu packages.

Update Changelog

1. If you are repackaging for a newhttp://bugs.amahi.org/issues/show/487 version Run dch -v with the version number currently in the makefile. Where you run the command depends on if you are changing hdactl or hda-platform.

# cd deb/ubuntu/karmic/hdactl
OR
# cd deb/ubuntu/karmic/hda-platform

# dch -v <version number>

Add the changes that you made to the system. If you are just updating for a new version state so.

If you are not changing the version number run dch -a. Where you run the command depends on if you are changing hdactl or hda-platform.
# cd deb/ubuntu/karmic/hdactl
OR
# cd deb/ubuntu/karmic/hda-platform

# dch -a

NOTE: If you are just building a .deb for your own testing you can just run make deb or continue to step 2.

2. To build hdactl package, change to 'platform/hdactl' directory and
run 'make deb'.

# cd platform/hdactl
# rm -rf hdactl-hup
# rm -rf platform/hdactl/release
# make deb

NOTE: The removing of hdactl-hup is only needed if it is present.

You will find the .deb file generated under platform/hdactl/release
directory.

NOTE: For ease of use use gdebi to install.

3. To build hda-platform package, change to 'platform/platform' directory and
run 'make deb'.

# cd platform/platform
# make deb

You will find the .deb file generated under platform/platform/release
directory.

=Architecture differences=

=Post install gotchas (asp's notes)=

= Known Bugs =
*Debian control script for platform may be missing some dependencies. [http://bugs.amahi.org/issues/show/487 bug 487]
*Passenger does not install see Considerations [http://bugs.amahi.org/issues/show/483 bug 483]
*HDACTL init scripts do not work [http://bugs.amahi.org/issues/show/484 bug 484]
=Considerations=
Instead of using FastCGI, perhaps package Amahi with capability to use Ubuntu's native phusion passenger (aka mod_rails) package.

Add the following line to the Third Party Software Sources:

deb http://apt.brightbox.net hardy main

(The simplest way to do that is to create a file in /etc/apt/sources.list.d/ containing the deb instruction, and then run 'apt-get update').

Once you've done this then you can install Phusion Passenger by running:

apt-get install libapache2-mod-passenger

'''This page is being edited actively and a lot of sections are missing currently'''

VirtualBox

2010-03-21T14:54:23Z

Anzenketh: added vboxweb

[[Category:Apps]]

This is a step by step tutorial on how to get VirtualBox 3 up and running on Fedora 12. Specifically, this guide was written using the VirtualBox 3.0.8 version and an i386 CPU (32-bit). It can be adapted to upcoming versions and different CPUs (64-bit). The folks at VirtualBox have made it easy to install for Fedora users and I’m going to show you how in a few easy steps. Right, open a terminal window and let’s get to it…

# Become privileged
su -
# Get the VirtualBox repo installed (you may need to install wget)
wget http://download.virtualbox.org/virtualbox/rpm/fedora/virtualbox.repo && cp virtualbox.repo /etc/yum.repos.d/
# Install VirtualBox (along with a few other needed packages)! If you’re having issues here, try installing “kernel-PAE-devel”
yum install -y VirtualBox dkms gcc
/etc/init.d/vboxdrv setup
# Add yourself to the “vboxusers” group and fix the SELinux Permissions (just in case):
usermod -G vboxusers -a <yourusername>
chcon -t textrel_shlib_t /usr/lib/virtualbox/VirtualBox.so
# Run, and enjoy!
VirtualBox

'''NOTE:''' See [http://www.derekhildreth.com/blog/how-to-install-virtualbox-3-on-fedora-12-tutorial/ how-to-install-virtualbox-3-on-fedora-12-tutorial] for more info.

''' NOTE '''' The following is in the alpha stages.
Get the virtual-box web installed.
SITE:
http://code.google.com/p/vboxweb/

Install Instructions
http://code.google.com/p/vboxweb/wiki/install

Contribute

2010-03-21T11:50:04Z

Anzenketh:

There are a few ways to contribute and get involved and with Amahi!

Here is a list of ideas that the community has been suggesting:

* Contribute to this wiki! That is probably the most direct and quick way to contribute. Your experience helps others install and run their HDA!
* Share your experience in the area or running a server and answer questions in the [http://forums.amahi.org community forums] or in the [https://lists.sourceforge.net/lists/listinfo/amahi-users users mailing list]. If you are an experienced user, others will appreciate your efforts and this will make the project more usable and successful in the long run
* Talk about Amahi! Let people know what Amahi is about, help them install their HDA
* Promote Amahi, such as doing a presentation to your local LUG (Linux User Group), share your presentation with others!
* Blog about your experience with Amahi
* Make recommendations
* Do reviews or HOWTOs
* Help us create a polished "press kit" of sorts that we can give when manazines and website editors ask us about Amahi
* [[How to Create a new Theme|Create a theme or two]]
* Help us write a "manual" so that it's printable (in pdf and also [http://lulu.com in paper])
* Submit to other sites that may like it! :-)

... remember, it has to be fun and enjoyable for you, take as little time as possible, and help the community!

Aside from the above, there are two major ways to contribute in a more active role.

= Types of Contributor =

We have three types of contributor, from less involved to more involved:

* '''Editor:''' editing the apps "visual" part for English readability, HTML validation, logo/screenshot "shinyness" and generally making beta apps look good
* '''Tester''': testing, rating and sending feedback on beta apps
* '''Packager''': packaging apps. no programming required

You can become any (or all) of these three roles by making yourself known to the community in the forums or in the IRC channel and asking to become a contributor!

= Becoming an Application Packager/Contributor =

* This is very easy. Whether you are an expert or you only know the basics of some application installation and configuration, this is a great way to contribute
* Read the [[Application Contributor]] Guide

= What if I want to contribute but don't have the time to package an app? =

Well heres a solution, you can find some apps for our developement team to package and we can do that for you. All you have to do is supply a link to the apps homepage and we will jump right on it. [[New_App_Ideas|Click Here]] to add you app ideas to the list. Any and all apps are ok.

= Contributing Code =

* Join the [https://sourceforge.net/mailarchive/forum.php?forum_name=amahi-devel amahi-devel list]
* If it's your first time, grab a copy of the git repo

git clone git://git.amahi.org/amahi.git

* If not, pull any changes from the master repo

cd amahi (the root of the git tree)
git pull

* Get yourself familiar with the pieces, and ask questions!
* Make some changes to the code, then test them:
* e.g. for testing the platform:

cd platform/platform/html
./script/server

and access it at http://hda:3000

* You can see your changes with two git tools: status and diff

git status

* The status gives you a list of what files were modified, added or removed. you can see changes in your area with:

git diff --cached

* When you know you want to modify a file, you add it to the changes to be committed, for example, say a README file:

git add README

* For the parts that are added and checked in, you can see the changes with

git diff

* This is what will be committed!

* Then actually commit your changes to your git repo:

git commit

* After that you can generate a patch to be sent upstream, e.g. for a patch of the latest commit.:

1. Go into the patch folder located in the root of the git tree.
2. git format-patch HEAD^..HEAD

NOTE: When creating the patch title(first line) please put it in YYMMDD-PATCHSEQUENCE#-long-patch-name.patch format. In the long name please include what module you are working on. AKA what application etc..

* This will generate a file called 0001-my-patch.mbox or similar (type ls -l 00*), which then you can email or pastebin it to someone to be committed upstream. You probably want to [[Configure Git]] to your liking first to display the email properly.

* Please note, once the patch is applied upstream, your name and email WILL be officially in the [http://git.amahi.org amahi git repo] as as contributor, which mean it's in the open and it's crawlable, so please use your PUBLIC name/email accordingly.

* For more details, ask in the [http://forums.amahi.org forums], [https://sourceforge.net/mailarchive/forum.php?forum_name=amahi-devel amahi-devel list], or come by the [http://talk.amahi.org IRC channel]

Contribute

2010-03-21T11:36:16Z

Anzenketh: Added updated patch policy

There are a few ways to contribute and get involved and with Amahi!

Here is a list of ideas that the community has been suggesting:

* Contribute to this wiki! That is probably the most direct and quick way to contribute. Your experience helps others install and run their HDA!
* Share your experience in the area or running a server and answer questions in the [http://forums.amahi.org community forums] or in the [https://lists.sourceforge.net/lists/listinfo/amahi-users users mailing list]. If you are an experienced user, others will appreciate your efforts and this will make the project more usable and successful in the long run
* Talk about Amahi! Let people know what Amahi is about, help them install their HDA
* Promote Amahi, such as doing a presentation to your local LUG (Linux User Group), share your presentation with others!
* Blog about your experience with Amahi
* Make recommendations
* Do reviews or HOWTOs
* Help us create a polished "press kit" of sorts that we can give when manazines and website editors ask us about Amahi
* [[How to Create a new Theme|Create a theme or two]]
* Help us write a "manual" so that it's printable (in pdf and also [http://lulu.com in paper])
* Submit to other sites that may like it! :-)

... remember, it has to be fun and enjoyable for you, take as little time as possible, and help the community!

Aside from the above, there are two major ways to contribute in a more active role.

= Types of Contributor =

We have three types of contributor, from less involved to more involved:

* '''Editor:''' editing the apps "visual" part for English readability, HTML validation, logo/screenshot "shinyness" and generally making beta apps look good
* '''Tester''': testing, rating and sending feedback on beta apps
* '''Packager''': packaging apps. no programming required

You can become any (or all) of these three roles by making yourself known to the community in the forums or in the IRC channel and asking to become a contributor!

= Becoming an Application Packager/Contributor =

* This is very easy. Whether you are an expert or you only know the basics of some application installation and configuration, this is a great way to contribute
* Read the [[Application Contributor]] Guide

= What if I want to contribute but don't have the time to package an app? =

Well heres a solution, you can find some apps for our developement team to package and we can do that for you. All you have to do is supply a link to the apps homepage and we will jump right on it. [[New_App_Ideas|Click Here]] to add you app ideas to the list. Any and all apps are ok.

= Contributing Code =

* Join the [https://sourceforge.net/mailarchive/forum.php?forum_name=amahi-devel amahi-devel list]
* If it's your first time, grab a copy of the git repo

git clone git://git.amahi.org/amahi.git

* If not, pull any changes from the master repo

cd amahi (the root of the git tree)
git pull

* Get yourself familiar with the pieces, and ask questions!
* Make some changes to the code, then test them:
* e.g. for testing the platform:

cd platform/platform/html
./script/server

and access it at http://hda:3000

* You can see your changes with two git tools: status and diff

git status

* The status gives you a list of what files were modified, added or removed. you can see changes in your area with:

git diff --cached

* When you know you want to modify a file, you add it to the changes to be committed, for example, say a README file:

git add README

* For the parts that are added and checked in, you can see the changes with

git diff

* This is what will be committed!

* Then actually commit your changes to your git repo:

git commit

* After that you can generate a patch to be sent upstream, e.g. for a patch of the latest commit.:

1. Go into the patch folder located in the root of the git folders.
2. git format-patch HEAD^..HEAD

NOTE: When creating the patch title(first line) please put it in YYMMDD-PATCHSEQUENCE#-long-patch-name.patch format. In the long name please include what module you are working on. AKA what application etc..

* This will generate a file called 0001-my-patch.mbox or similar (type ls -l 00*), which then you can email or pastebin it to someone to be committed upstream. You probably want to [[Configure Git]] to your liking first to display the email properly.

* Please note, once the patch is applied upstream, your name and email WILL be officially in the [http://git.amahi.org amahi git repo] as as contributor, which mean it's in the open and it's crawlable, so please use your PUBLIC name/email accordingly.

* For more details, ask in the [http://forums.amahi.org forums], [https://sourceforge.net/mailarchive/forum.php?forum_name=amahi-devel amahi-devel list], or come by the [http://talk.amahi.org IRC channel]

UbuntuPorting

2010-03-21T09:34:10Z

Anzenketh: removed postinstall notes until new package is built.

'''This page is being edited actively and a lot of sections are missing currently'''

=Current state=
We just started porting Amahi to Ubuntu. The support is highly experimental. There are a few important things to be fixed before you can run it with minimal tweaking. Please don't try it on a production server yet. We are using Ubuntu 9.04 (jaunty) Desktop 32 bit for development. We strongly recommend you to use the same for experiments. You can download this version from [http://www.ubuntu.com/getubuntu/download here].

=Requirements=
You may want to have two different installations of Ubuntu.
* A development platform, running Ubuntu 9.04 Desktop 32 bit and/or 64 bit with the recommended development packages installed.
* An Amahi sandbox, running Ubuntu 9.04 Desktop 32 bit '''preferably''' under [http://www.virtualbox.org/ VirtualBox].
Please don't install the Amahi packages on the development platform as this might break your networking.

=Setting up the development platform=
# Install Ubuntu 9.04 Desktop 32 bit.
# Install essential build toolchain.
## sudo apt-get update
## sudo apt-get install build-essential
## sudo apt-get install devscripts
## sudo apt-get install debhelper
## sudo apt-get install fakeroot
## sudo apt-get install lintian
# Install git. # sudo aptitude install git-core
# Read [https://wiki.ubuntu.com/PackagingGuide/Complete Ubuntu packaging guide] to get an idea of other additional packages that you may want to install to create Ubuntu packages. I will list the packages to make your part easier at a later point.

=Setting up the Amahi sandbox=
# Install [http://www.virtualbox.org/ Sun VirtualBox]. # sudo aptitude install virtualbox-ose
# Open VirtualBox and create a new guest platform for Ubuntu and install Ubuntu 9.04 Desktop 32 bit.
# Install VirtualBox guest additions in your Amahi sandbox.
# Setup VirtualBox folder sharing between your development platform and Amahi sandbox.

=Amahi source code=
On your development platform, download Amahi source code from our git repository. Follow these steps to build Ubuntu packages.

Update Changelog

1. If you are repackaging for a new version Run dch -v with the version number currently in the makefile. Where you run the command depends on if you are changing hdactl or hda-platform.

# cd deb/ubuntu/karmic/hdactl
OR
# cd deb/ubuntu/karmic/hda-platform

# dch -v <version number>

Add the changes that you made to the system. If you are just updating for a new version state so.

If you are not changing the version number run dch -a. Where you run the command depends on if you are changing hdactl or hda-platform.
# cd deb/ubuntu/karmic/hdactl
OR
# cd deb/ubuntu/karmic/hda-platform

# dch -a

NOTE: If you are just building a .deb for your own testing you can just run make deb or continue to step 2.

2. To build hdactl package, change to 'platform/hdactl' directory and
run 'make deb'.

# cd platform/hdactl
# rm -rf hdactl-hup
# rm -rf platform/hdactl/release
# make deb

NOTE: The removing of hdactl-hup is only needed if it is present.

You will find the .deb file generated under platform/hdactl/release
directory.

NOTE: For ease of use use gdebi to install.

3. To build hda-platform package, change to 'platform/platform' directory and
run 'make deb'.

# cd platform/platform
# make deb

You will find the .deb file generated under platform/platform/release
directory.

=Architecture differences=

* Apache runs as 'www-data' instead of 'apache'.
** Fix - Edit /var/hda/platform/html/script/install-app the following:
uid = Etc.getpwnam("apache").uid
* Alternative Fix:
** Edit the file /etc/apache2/envvars to set the apache user to 'apache' as opposed to 'www-data'
=Post install gotchas (asp's notes)=

### removed past post install notes as many changes have happened that may have deprecated some issues.

=Considerations=
Instead of using FastCGI, perhaps package Amahi with capability to use Ubuntu's native phusion passenger (aka mod_rails) package.

Add the following line to the Third Party Software Sources:

deb http://apt.brightbox.net hardy main

(The simplest way to do that is to create a file in /etc/apt/sources.list.d/ containing the deb instruction, and then run 'apt-get update').

Once you've done this then you can install Phusion Passenger by running:

apt-get install libapache2-mod-passenger

'''This page is being edited actively and a lot of sections are missing currently'''

UbuntuPorting

2010-03-19T08:36:45Z

Anzenketh: Formatting changes

'''This page is being edited actively and a lot of sections are missing currently'''

=Current state=
We just started porting Amahi to Ubuntu. The support is highly experimental. There are a few important things to be fixed before you can run it with minimal tweaking. Please don't try it on a production server yet. We are using Ubuntu 9.04 (jaunty) Desktop 32 bit for development. We strongly recommend you to use the same for experiments. You can download this version from [http://www.ubuntu.com/getubuntu/download here].

=Requirements=
You may want to have two different installations of Ubuntu.
* A development platform, running Ubuntu 9.04 Desktop 32 bit and/or 64 bit with the recommended development packages installed.
* An Amahi sandbox, running Ubuntu 9.04 Desktop 32 bit '''preferably''' under [http://www.virtualbox.org/ VirtualBox].
Please don't install the Amahi packages on the development platform as this might break your networking.

=Setting up the development platform=
# Install Ubuntu 9.04 Desktop 32 bit.
# Install essential build toolchain.
## sudo apt-get update
## sudo apt-get install build-essential
## sudo apt-get install devscripts
## sudo apt-get install debhelper
## sudo apt-get install fakeroot
## sudo apt-get install lintian
# Install git. # sudo aptitude install git-core
# Read [https://wiki.ubuntu.com/PackagingGuide/Complete Ubuntu packaging guide] to get an idea of other additional packages that you may want to install to create Ubuntu packages. I will list the packages to make your part easier at a later point.

=Setting up the Amahi sandbox=
# Install [http://www.virtualbox.org/ Sun VirtualBox]. # sudo aptitude install virtualbox-ose
# Open VirtualBox and create a new guest platform for Ubuntu and install Ubuntu 9.04 Desktop 32 bit.
# Install VirtualBox guest additions in your Amahi sandbox.
# Setup VirtualBox folder sharing between your development platform and Amahi sandbox.

=Amahi source code=
On your development platform, download Amahi source code from our git repository. Follow these steps to build Ubuntu packages.

Update Changelog

1. If you are repackaging for a new version Run dch -v with the version number currently in the makefile. Where you run the command depends on if you are changing hdactl or hda-platform.
# cd deb/ubuntu/karmic/hdactl
OR
# cd deb/ubuntu/karmic/hda-platform

# dch -v <version number>

Add the changes that you made to the system. If you are just updating for a new version state so.

If you are not changing the version number run dch -a. Where you run the command depends on if you are changing hdactl or hda-platform.
# cd deb/ubuntu/karmic/hdactl
OR
# cd deb/ubuntu/karmic/hda-platform

# dch -a

NOTE: If you are just building a .deb for your own testing you can just run make deb or continue to step 2.

2. To build hdactl package, change to 'platform/hdactl' directory and
run 'make deb'.

# cd platform/hdactl
# make deb

You will find the .deb file generated under platform/hdactl/release
directory.

3. To build hda-platform package, change to 'platform/platform' directory and
run 'make deb'.

# cd platform/platform
# make deb

You will find the .deb file generated under platform/platform/release
directory.

=Architecture differences=

* Apache runs as 'www-data' instead of 'apache'.
** Fix - Edit /var/hda/platform/html/script/install-app the following:
uid = Etc.getpwnam("apache").uid
* Alternative Fix:
** Edit the file /etc/apache2/envvars to set the apache user to 'apache' as opposed to 'www-data'
=Post install gotchas (asp's notes)=
After building the deb packages above and installing using the Ubuntu pkg installer, was able to then startup hdactl (using '/etc/init.d/hdactl start') and then http;//hda worked.

# Had to install the pluginfactory gem by running 'gem install -no-rdoc -no-ri pluginfactory'
# Noticed that Apache runs as 'www-data' on Ubuntu instead of 'apache' user like on Fedora. Amahi-app-installer.log indicated 'apache' user was not found after attempting to install an app on Application tab of platform.

=Considerations=
Instead of using FastCGI, perhaps package Amahi with capability to use Ubuntu's native phusion passenger (aka mod_rails) package.

Add the following line to the Third Party Software Sources:

deb http://apt.brightbox.net hardy main

(The simplest way to do that is to create a file in /etc/apt/sources.list.d/ containing the deb instruction, and then run 'apt-get update').

Once you've done this then you can install Phusion Passenger by running:

apt-get install libapache2-mod-passenger

'''This page is being edited actively and a lot of sections are missing currently'''

UbuntuPorting

2010-03-19T08:34:45Z

Anzenketh: Updated for update of deb

'''This page is being edited actively and a lot of sections are missing currently'''

=Current state=
We just started porting Amahi to Ubuntu. The support is highly experimental. There are a few important things to be fixed before you can run it with minimal tweaking. Please don't try it on a production server yet. We are using Ubuntu 9.04 (jaunty) Desktop 32 bit for development. We strongly recommend you to use the same for experiments. You can download this version from [http://www.ubuntu.com/getubuntu/download here].

=Requirements=
You may want to have two different installations of Ubuntu.
* A development platform, running Ubuntu 9.04 Desktop 32 bit and/or 64 bit with the recommended development packages installed.
* An Amahi sandbox, running Ubuntu 9.04 Desktop 32 bit '''preferably''' under [http://www.virtualbox.org/ VirtualBox].
Please don't install the Amahi packages on the development platform as this might break your networking.

=Setting up the development platform=
# Install Ubuntu 9.04 Desktop 32 bit.
# Install essential build toolchain.
## sudo apt-get update
## sudo apt-get install build-essential
## sudo apt-get install devscripts
## sudo apt-get install debhelper
## sudo apt-get install fakeroot
## sudo apt-get install lintian
# Install git. # sudo aptitude install git-core
# Read [https://wiki.ubuntu.com/PackagingGuide/Complete Ubuntu packaging guide] to get an idea of other additional packages that you may want to install to create Ubuntu packages. I will list the packages to make your part easier at a later point.

=Setting up the Amahi sandbox=
# Install [http://www.virtualbox.org/ Sun VirtualBox]. # sudo aptitude install virtualbox-ose
# Open VirtualBox and create a new guest platform for Ubuntu and install Ubuntu 9.04 Desktop 32 bit.
# Install VirtualBox guest additions in your Amahi sandbox.
# Setup VirtualBox folder sharing between your development platform and Amahi sandbox.

=Amahi source code=
On your development platform, download Amahi source code from our git repository. Follow these steps to build Ubuntu packages.

Update Changelog
1. If you are repackaging for a new version Run dch -v with the version number currently in the makefile. Where you run the command depends on if you are changing hdactl or hda-platform.
# cd deb/ubuntu/karmic/hdactl
OR
# cd deb/ubuntu/karmic/hda-platform

# dch -v <version number>
Add the changes that you made to the system. If you are just updating for a new version state so.

If you are not changing the version number run dch -a. Where you run the command depends on if you are changing hdactl or hda-platform.
# cd deb/ubuntu/karmic/hdactl
OR
# cd deb/ubuntu/karmic/hda-platform

# dch -a
##NOTE: If you are just building a .deb for your own testing you can just run make deb or continue to step 2.

2. To build hdactl package, change to 'platform/hdactl' directory and
run 'make deb'.

# cd platform/hdactl
# make deb

You will find the .deb file generated under platform/hdactl/release
directory.

3. To build hda-platform package, change to 'platform/platform' directory and
run 'make deb'.

# cd platform/platform
# make deb

You will find the .deb file generated under platform/platform/release
directory.

=Architecture differences=

* Apache runs as 'www-data' instead of 'apache'.
** Fix - Edit /var/hda/platform/html/script/install-app the following:
uid = Etc.getpwnam("apache").uid
* Alternative Fix:
** Edit the file /etc/apache2/envvars to set the apache user to 'apache' as opposed to 'www-data'
=Post install gotchas (asp's notes)=
After building the deb packages above and installing using the Ubuntu pkg installer, was able to then startup hdactl (using '/etc/init.d/hdactl start') and then http;//hda worked.

# Had to install the pluginfactory gem by running 'gem install -no-rdoc -no-ri pluginfactory'
# Noticed that Apache runs as 'www-data' on Ubuntu instead of 'apache' user like on Fedora. Amahi-app-installer.log indicated 'apache' user was not found after attempting to install an app on Application tab of platform.

=Considerations=
Instead of using FastCGI, perhaps package Amahi with capability to use Ubuntu's native phusion passenger (aka mod_rails) package.

Add the following line to the Third Party Software Sources:

deb http://apt.brightbox.net hardy main

(The simplest way to do that is to create a file in /etc/apt/sources.list.d/ containing the deb instruction, and then run 'apt-get update').

Once you've done this then you can install Phusion Passenger by running:

apt-get install libapache2-mod-passenger

'''This page is being edited actively and a lot of sections are missing currently'''

Ubuntu

2010-03-19T08:28:22Z

Anzenketh: Removed hda-installer as it is no longer used.

==Can I install Amahi on Ubuntu?==

Not yet. We hope to get Ubuntu contributions soon.

The long term goal for Amahi is to be an "easy to use" product rather than "for geeks only."

This is why the Amahi home server is managed through a Web 2.0 browser-based interface and is designed to run headless. Of course file sharing and related activities are supported cross platform - Linux, Windows and Mac.

The underlying distribution that Amahi is currently built on is Fedora.

There are frequent requests to make an Ubuntu version available - but to date there are not enough "truly experienced" Ubuntu developers ready to commit to make this happen. As developers get involved they realize that the underlying distribution does not impact the end user experience.

Amahi is designed to run headless, so porting to Ubuntu has not been a very high priority task (there is a lot of learning, since the developers are more familiar with Fedora). The development time is mostly spent improving Amahi while we gather real Ubuntu contributions.

If you are ready to lead the effort, let us know and the team will help get you started. Please subscribe to the amahi-devel mailing list!

== What To Do ==

NOTE: some [[UbuntuPorting | Ubuntu Porting Notes]]

Here are the rough suggested steps to make Amahi on Ubuntu possible.

# Focus on an installed system first, '''writing down''' (say in a wiki page here) the things needed to get things running. Later focus on the installer, which will have many more platform dependencies.
# Install Ubuntu server
# Install ruby, rails and the appropropriate gems (write down the exact commands needed to do this)
# Make the interface work first. Use RoR in development mode on a base amahi platform tree. This should be platform independent.
# Once the interface is working, install the Amahi control daemon. This will need some hooks to make work under Ubuntu for sure.
# This will complete the two basic things needed to get the ball rolling. The next one will be applications. This is potentially complex.
# After all of this is done, the various parts will need to be packaged as debs and put in a repo for ubuntu
# Finally, testing, testing, testing! :)

Some open questions/topics:

* Can we somehow live with RPMs in the short term (which is what we have today)? Using something that we have today would make it easier right away, i.e. if we can go with a repo that we already have, it would be a massive step to get started.
* Should we start with ubuntu desktop or ubuntu server? - my first impression would be server, which makes more sense. Any gotchas with that?
* How are updates handled in ubuntu?

Given how there is a lot of learning to be achieved on both sides,
you should probably stop by the [http://webchat.freenode.net/?channels=amahi #amahi irc channel]
at irc.freenode.net. At least one or two of the usuals
there are also interested in Ubuntu.

You can also discuss this in the amahi-devel mailing list.