Amahi Wiki - User contributions [en]

TorrentFlux-b4rt

2009-12-31T03:55:59Z

IseeAliens:

[[Category:Apps]]

= Steps in installing Torrentflux b4rt =

* Install as a one-click app.
* The default username is admin and the password is admin.
* Login and start downloading!
* Change configuration options if you want to.

= Known Issues =

* You will see an error on the configuration page that says: "Executable is not TorrentFlux-bundled transmissioncli". This is a known bug and it is safe to ignore. Torrentflux-bart will still work. It is being looked into.
* You cannot use the bittorrent client 'transmissioncli' at this point in time due to the previous issue. The default bittorrent client is BitTornado and it is recommended.
* If you install RPMFusion repositories first than VLC will install and will enable streaming audio/video.
* If you install RPMFusion repositories first than unrar will install with the package.
* If you find a bug not covered here please file a bug report at http://bugs.amahi.org/

== Manual steps to get transmissioncli working ==

Only ‘patched’ versions of Transmissioncli work with Torrentflux-b4rt, remove already installed Transmission client before starting this.

• Install required programs:
# yum install gcc openssl-devel libcurl-devel gettext

• Get the latest Transmission version that there is a patch available for to work with 'b4rt':
# wget http://download.m0k.org/transmission/files/transmission-1.34.tar.bz2

• Extract the file:
# tar -xvf transmission-1.34.tar.bz2

• Change to the directory in the extracted folder and remove the standard 'transsimtioncli' file:
# cd transmission-1.34/cli
# rm cli.c

• Staying in the 'cli' directory of the extracted folder, get the 'patched cli':
# wget http://svn.berlios.de/svnroot/repos/tf-b4rt/branches/clients/transmission/transmission-1.34/cli/cli.c

• Compile and install:
# cd .. (back to the folder 'transmission-1.34)
# ./configure
# make
# make install

If all goes well, you should get a compiled executable, transmissioncli, in the cli folder; copy/simlink it to your bin folder.

• Copy over 'transmissioncli' from the 'cli' folder to ‘/user/bin’ folder replacing existing one:
# cp cli/transmissioncli /usr/bin/

Now go back to the 'b4rt' server page, 'transmissioncli’ should now be green lighted.

Source; http://tf-b4rt.berlios.de/forum/index.php/topic,1845.0.html

== Images ==
[[Image:tflux-b4rt-logo.png]]

[[Image:tflux-b4rt-sshot.jpg]]

TorrentFlux-b4rt

2009-12-31T03:55:14Z

IseeAliens:

TorrentFlux-b4rt

2009-12-31T03:52:12Z

IseeAliens:

[[Category:Apps]]

= Steps in installing Torrentflux b4rt =

* Install as a one-click app.
* The default username is admin and the password is admin.
* Login and start downloading!
* Change configuration options if you want to.

= Known Issues =

* You will see an error on the configuration page that says: "Executable is not TorrentFlux-bundled transmissioncli". This is a known bug and it is safe to ignore. Torrentflux-bart will still work. It is being looked into.
* You cannot use the bittorrent client 'transmissioncli' at this point in time due to the previous issue. The default bittorrent client is BitTornado and it is recommended.
* If you install RPMFusion repositories first than VLC will install and will enable streaming audio/video.
* If you install RPMFusion repositories first than unrar will install with the package.
* If you find a bug not covered here please file a bug report at http://bugs.amahi.org/

== Manual steps to get transmissioncli working ===

Only ‘patched’ versions of Transmissioncli work with Torrentflux-b4rt, remove already installed Transmission client before starting this.

• Install required programs:
# yum install gcc openssl-devel libcurl-devel gettext

• Get the latest Transmission version that there is a patch available for to work with 'b4rt':
# wget http://download.m0k.org/transmission/files/transmission-1.34.tar.bz2

• Extract the file:
# tar -xvf transmission-1.34.tar.bz2

• Change to the directory in the extracted folder and remove the standard 'transsimtioncli' file:
# cd transmission-1.34/cli
# rm cli.c

• Staying in the 'cli' directory of the extracted folder, get the 'patched cli':
# wget http://svn.berlios.de/svnroot/repos/tf-b4rt/branches/clients/transmission/transmission-1.34/cli/cli.c

• Compile and install:
# cd .. (back to the folder 'transmission-1.34)
# ./configure
# make
# make install

If all goes well, you should get a compiled executable, transmissioncli, in the cli folder; copy/simlink it to your bin folder.

• Copy over 'transmissioncli' from the 'cli' folder to ‘/user/bin’ folder replacing existing one:
# cp cli/transmissioncli /usr/bin/

Now go back to the 'b4rt' server page, 'transmissioncli’ should now be green lighted.

Source; http://tf-b4rt.berlios.de/forum/index.php/topic,1845.0.html

== Images ==
[[Image:tflux-b4rt-logo.png]]

[[Image:tflux-b4rt-sshot.jpg]]

Jinzora

2009-08-12T20:57:20Z

IseeAliens:

[[Category:Apps]]

[http://en.jinzora.com/ Jinzora] is a web based media streaming and management system, written in PHP.

= "One-click" Jinzora Installer =

The default administrator in the "One-click" install of Jinzora2 on Amahi is
login: admin
password: admin

The One-click installer is configured to have the music library stored in the share called "music."

Jinzora looks for a '''very specific structure when it looks for media'''. It expects to find a folder structure like this inside the music folder:
* Level 1: Genre
* Level 2: Artist
* Level 3: Album
* Level 4: sound tracks
If it does then Jinzora does a great job organizing the collection.

To scan your library into Jinzora:
# login as the user "admin"
# click the "Admin Tools" icon - in the little window at the top left of the screen
# in the pop-up window click "Media Management"
# click "Rescan media"
# select the options you prefer (All sub-items for me) and click the "Scan Now" button

To change the location where jinzora searches for audio files:

# Admin tools> system tools> settings manager> main settings> System> media_dirs

Point the “media_dirs” to the location where your audio files resides and then re-run the “Rescan media” function.

Require Login

2009-07-28T19:37:36Z

IseeAliens:

We have a budding feature to require login to individual webapps.

Note - each app may have created a corresponding webapp. It's in this webapp that the Login Required may be selected.

If selected, this settings makes it such that the application will ask for a user name and a password.

Unfortunately this is no integrated yet with the rest of the user/password system already in place, so for now, it has to be done using htaccess controls.

We have decided to make these a global setting, i.e. the users and password are all the same to all the apps that require login.

== How to do it ==

This requires that an htaccess file and an htpassword file be created in a place that it's accessible to the web server.

To create an <code>htpasswd</code> file containing the users and passwords
* you can go to a [http://www.webmaster-toolkit.com/htaccess-generator.shtml public htaccess/htpasswd generator] and copy the contents of what the "And this is what your .htpasswd file should look like..." box has
* or you can use the htpasswd command (first time with -c)
htpasswd -c .htpasswd USERNAME

The file should contain lines like this: USERNAME:3Ce3F4zRcVf42

The file should be owned by apache:apache and have 600 permissions, so copy it over, then, as root:

cp .htpasswd /var/hda/web-apps/htpasswd
chmod 600 /var/hda/web-apps/htpasswd
chown apache:apache /var/hda/web-apps/htpasswd

= If you have webmin installed =

After logging into webmin select “Others” on the left-hand side, click on “Protected Web Directories” and then select “Add protection for a new directory”.

In “Directory path” browse to/or enter the path to the ‘html’ web directory you wish to protect, in “Authentication realm” enter something like for example “Authentication required” (this will show up on the popup login box) and then click on create.

Now you need to setup users to allow login by clicking on “Add a new user” in “Associated users and groups”, when users have been created you should be good to go.

Note: After you have completed this process using webmin you can then select "un-protect selected directory" and use the HDA-Dashboard to enable/disable password protection.

Require Login

2009-07-28T19:18:42Z

IseeAliens:

Require Login

2009-07-28T19:17:06Z

IseeAliens:

Require Login

2009-07-28T19:13:51Z

IseeAliens:

We have a budding feature to require login to individual webapps.

Note - each app may have created a corresponding webapp. It's in this webapp that the Login Required may be selected.

If selected, this settings makes it such that the application will ask for a user name and a password.

Unfortunately this is no integrated yet with the rest of the user/password system already in place, so for now, it has to be done using htaccess controls.

We have decided to make these a global setting, i.e. the users and password are all the same to all the apps that require login.

== How to do it ==

This requires that an htaccess file and an htpassword file be created in a place that it's accessible to the web server.

To create an <code>htpasswd</code> file containing the users and passwords
* you can go to a [http://www.webmaster-toolkit.com/htaccess-generator.shtml public htaccess/htpasswd generator] and copy the contents of what the "And this is what your .htpasswd file should look like..." box has
* or you can use the htpasswd command (first time with -c)
htpasswd -c .htpasswd USERNAME

The file should contain lines like this: USERNAME:3Ce3F4zRcVf42

The file should be owned by apache:apache and have 600 permissions, so copy it over, then, as root:

cp .htpasswd /var/hda/web-apps/htpasswd
chmod 600 /var/hda/web-apps/htpasswd
chown apache:apache /var/hda/web-apps/htpasswd

= If you have webmin installed =

After logging into webmin select “Others” on the left-hand side, click on “Protected Web Directories” and then select “Add protection for a new directory”.

In “Directory path” browse to/or enter the path to the ‘html’ web directory you wish to protect, in “Authentication realm” enter something like for example “Authentication required” (this will show up on the popup login box) and then click on create.

Now you need to add users to allow by clicking on “Add a new user” in “Associated users and groups”.

Require Login

2009-07-28T19:09:59Z

IseeAliens:

We have a budding feature to require login to individual webapps.

Note - each app may have created a corresponding webapp. It's in this webapp that the Login Required may be selected.

If selected, this settings makes it such that the application will ask for a user name and a password.

Unfortunately this is no integrated yet with the rest of the user/password system already in place, so for now, it has to be done using htaccess controls.

We have decided to make these a global setting, i.e. the users and password are all the same to all the apps that require login.

== How to do it ==

This requires that an htaccess file and an htpassword file be created in a place that it's accessible to the web server.

To create an <code>htpasswd</code> file containing the users and passwords
* you can go to a [http://www.webmaster-toolkit.com/htaccess-generator.shtml public htaccess/htpasswd generator] and copy the contents of what the "And this is what your .htpasswd file should look like..." box has
* or you can use the htpasswd command (first time with -c)
htpasswd -c .htpasswd USERNAME

The file should contain lines like this: USERNAME:3Ce3F4zRcVf42

The file should be owned by apache:apache and have 600 permissions, so copy it over, then, as root:

cp .htpasswd /var/hda/web-apps/htpasswd
chmod 600 /var/hda/web-apps/htpasswd
chown apache:apache /var/hda/web-apps/htpasswd

= If you have webmin installed =

After logging into webmin select “Others” on the left-hand side, click on “Protected Web Directories” and then select “Add protection for a new directory”.

In “Directory path” browse to/or enter the path to the ‘html’ web directory you wish to protect, in “Authentication realm” enter something like for example “Authentication required” (this will show up on the popup login box) and then click save.

Now you need to add users to allow by clicking on “Add a new user” in “Associated users and groups”.

Require Login

2009-07-28T19:09:09Z

IseeAliens:

We have a budding feature to require login to individual webapps.

Note - each app may have created a corresponding webapp. It's in this webapp that the Login Required may be selected.

If selected, this settings makes it such that the application will ask for a user name and a password.

Unfortunately this is no integrated yet with the rest of the user/password system already in place, so for now, it has to be done using htaccess controls.

We have decided to make these a global setting, i.e. the users and password are all the same to all the apps that require login.

== How to do it ==

This requires that an htaccess file and an htpassword file be created in a place that it's accessible to the web server.

To create an <code>htpasswd</code> file containing the users and passwords
* you can go to a [http://www.webmaster-toolkit.com/htaccess-generator.shtml public htaccess/htpasswd generator] and copy the contents of what the "And this is what your .htpasswd file should look like..." box has
* or you can use the htpasswd command (first time with -c)
htpasswd -c .htpasswd USERNAME

The file should contain lines like this: USERNAME:3Ce3F4zRcVf42

The file should be owned by apache:apache and have 600 permissions, so copy it over, then, as root:

cp .htpasswd /var/hda/web-apps/htpasswd
chmod 600 /var/hda/web-apps/htpasswd
chown apache:apache /var/hda/web-apps/htpasswd

= If you have webmin installed =

After logging into webmin select “Others” on the left-hand side, click on “Protected Web Directories” and then select “Add protection for a new directory”.

In “Directory path” browse to/or enter the path to the ‘html’ web directory you wish to protect, in “Authentication realm” enter something like for example “Authentication required” (this will show up on the popup login box) and then click save.

Now you need add users to allow by clicking on “Add a new user” in “Associated users and groups”.

Category:Apps

2009-04-15T00:12:40Z

IseeAliens:

Applications for the HDA - including ones that come with it and ones you can add-on afterwards.

Category:Apps

2009-04-15T00:11:02Z

IseeAliens:

Applications for the HDA - including ones that come with it and ones you can add-on afterwards.

[[Category:Apps]]

Webmin

Category:Apps

2009-04-15T00:10:02Z

IseeAliens:

[[Category:Apps]]

Webmin

Applications for the HDA - including ones that come with it and ones you can add-on afterwards.

Category:Apps

2009-04-15T00:08:06Z

IseeAliens:

Applications for the HDA - including ones that come with it and ones you can add-on afterwards.

[[Category:Apps]]

Webmin

TorrentFlux-b4rt

2009-04-14T02:40:06Z

IseeAliens:

[[Category:Apps]]

= Steps in installing Torrentflux b4rt =

Current test install needs further testing and if and when successful, steps on installing torrentflux-b4rt will be noted here.

Thanks for looking.

Jinzora

2009-04-10T15:03:00Z

IseeAliens:

[[Category:Apps]]

http://en.jinzora.com/

Jinzora is a web based media streaming and management system, written in PHP.

Streaming your media with Jinzora gives you quick and easy access to your online music and video collection from any device with a web browser.

Enjoy your media from your PC, notebook, PDA, Smart Phone, Xbox, PS3 or Wii.

Use Jinzora in Jukebox Mode to control a hardware device like your stereo set or Squeezebox and third-party software, including MPD, VLC and Shoutcast.

= "One-click" Jinzora Installer =

The default administrator in the "One-click" install of Jinzora2 on Amahi is
login: admin
password: admin

The One-click installer is configured to have the music library stored in the share called "music." To scan your library into Jinzora:
# login as the user "admin"
# click the "Admin Tools" icon - in the little window at the top left of the screen
# in the pop-up window click "Media Management"
# click "Rescan media"
# select the options you prefer (All sub-items for me) and click the "Scan Now" button

To change the location where jinzora searches for audio files:

# Admin tools> system tools> settings manager> main settings> media_dirs

Point the “media_dirs” to the location where your audio files resides and then re-run the “Rescan media” function.

= Manual Install Instructions for Jinzora =
(Note this will be automated with one-click install)

* Create the install directory/web-app
** goto http://setup
** select the web-apps tab
** click create new button and use the name "jinzora"

* navigate to the web-apps directory
** from the command prompt
cd /var/hda/web-apps/jinzora

* Download the Jinzora tarball - As of this writing, at: http://downloads.sourceforge.net/jinzora/jz275.tar.gz
** Form the command line enter
wget http://downloads.sourceforge.net/jinzora/jz275.tar.gz
* remove the automatically created directory html. From the command line:
rmdir html
* Untar the app: From the command line:
tar -xzvf jz275.tar.gz
* This puts the .tar contents into the folder called jinzora2
* rename the folder "jinzora2" to the new name "html"
mv jinzora2 html

* configure the security access .htaccess file (edit the file):
nano /var/hda/web-apps/jinzora/html/.htaccess
* As the first character in all lines put a # then press ctrl-x, and y and "enter" to save

* After that, jinzora should be ready to continue install ...
* Navigate to the jinzora directory
cd /var/hda/web-apps/jinzora/html
* Your web server needs write permissions to some of the Jinzora files. To write log files and cached pages for example. We've created a script called 'configure.sh' that sets the required permissions. First, the script needs to be made executable:
chmod 744 configure.sh
* Run the script to set permissions:
sh ./configure.sh

* Create a database for jinzora to use
hda-create-db-and-user jinzora2
(database name=jinzora2, username=jinzora2 and password=jinzora2)

At this point your basic app configuration should be up and running.

Launch Jinzora and follow the instructions.
* Use a browser and go to http://jinzora/
* Now you can setup jinzora

(at the end you will have to remove the install directory at some point):
rm -rf /var/hda/web-apps/jinzora/html/install

Adding a second hard drive to your HDA

2009-03-25T22:25:15Z

IseeAliens:

A secondary hard drive (fat32, ntfs, etc) can be added for additional storage in your Amahi HDA. First thing's first, make sure your drive is connected properly and detected by the bios.

It can be configured to mount permanently using the [http://wiki.amahi.org/images/c/c6/Diskmounter.sh diskmounter] script (thanks to Dennis Kaarsemaker and Luigi Capriotti).

* Execute the script as ''root'' and answer YES to the prompt to make the drive writable to all users.
* Once complete, reboot and the secondary drive should automatically mount.
* As user ''root'', edit '''''/etc/fstab''''' to change location of shared ''//hda'' folders to the secondary drive.

This is what the script added for my drive:
''Added by diskmounter utility''
''/dev/sdb1 /var/hda/files vfat rw,user,fmask=0111,dmask=0000 0 0''

I changed second path to '''''/var/hda/files''''' to enable all shared files to be stored on the secondary hard drive. This is the default path for ''//hda'' file storage system.

If you get the following error "bash: ./Diskmounter.sh: Permission denied" try executing the following without the commas:

'chmod 755 Diskmounter.sh' - After executing that command you should be able to execute the Diskmounter.sh script.

If you get "./Diskmounter.sh: line 48: pmount: command not found" try running the following without the commas:

'yum -y install pmount' - Then try again executing the Diskmounter.sh script.

If you get something similar like "Disk /dev/dm-0 doesn't contain a valid partition table" or "mount: unknown file system type 'lvm2pv'" its because you have LVM's that 'fdisk' cant recognise, (or something like that) its nothing to worry about if you get that when executed the Diskmounter.sh script.

(Credit to cpg)

=If the script doesn't work for you=

These instructions are adapted from [http://www.mjmwired.net/resources/mjm-fedora-f9.html#ntfs here]

If you're planning to mount a NTFS disk, you'll need to make sure you have ntfs-3g, fuse and fuse libs all installed. If not, login as root and run:

$ yum install fuse fuse-libs ntfs-3g

Then use fdisk to find the disk by running fdisk -l (this is a lower case L not a 1). You may have to give the path (/sbin/fdisk) to make it work.

$ /sbin/fdisk -l

This should return the needed information about all your disks. Look out for your newly attached disk. In my case in among the results I can find:

Disk /dev/sdb: 120.0GB 120034123776 bytes
255 heads, 63 sectors/track.... etc etc.

I know my disk is 120GB so that's the right one. This tells us the name of the new disk which is "sdb" in my case. Running

$ sudo /sbin/fdisk -lu /dev/sdb | grep NTFS

..will give you a break down of partitions. In my case, there's just one partition, sdb1, so this is the partition I will mount.

Now we can go on to create the mount points if needs be. But because my disk contains all my music, I want it to be mounted as if it were my local "Music" folder, so for me the mount point already exists. But if just want to access your disk easily you could just as easily mount it anywhere. Commonly mount points are put in either /mnt/ or /media/. It doesn't matter where - just be consistent when you are doing this.
To do this run these commands as root:
$ cd /mnt/
$ mkdir my_ntfs_disk

Substituting my_ntfs_disk for whatever you want to call it.

Now we can mount the disk in the desired location. Again as root run this command:
$ mount /dev/sdb1 /mnt/my_ntfs_drive -t ntfs-3g -r -o umask=0222

This command will make the mounted drive read only. That's great if that's what you want, but for me, since I want to save my music there, I need it to be read and writeable. For this you'll use:

$ mount /dev/sdb1 /mnt/my_ntfs_drive -t ntfs-3g -rw -o umask=0000

or in my case

$ mount /dev/sdb1 /home/USERNAME/Music -t ntfs-3g -rw -o umask=0000

because I want it mounted in my "Music" file.

Remember in both of these commands you'll need to substitute sdb1 with whatever the partition name/number is on your machine. And in the second command USERNAME is your linux username.

If you now go to your desktop, you should see the drive is mounted there. Click on it to see the contents are there. If you've mounted it as say So far so good? Ok, let's continue.

What you've achieved so far is a temporary mounting of the drive/partition. That shows it can be done but you'll need to make it permanent otherwise when you reboot it'll disappear again. For this you need to edit fstab with your favourite text editor. As root run:

$ gedit /etc/fstab

A text editor window will pop up. Enter this on the last line:

/dev/sdb1 /mnt/my_ntfs_drive ntfs-3g ro,defaults,umask=0222 0 0

* change '''ro to rw''' and '''umask=0222 to umask=0000''' if you want it to be writable.

You'll need to do this for every partition, so if you have several partitions on sdb, the last lines of you fstab may look something like this

/dev/sdb1 /mnt/my_ntfs_drive_C ntfs-3g ro,defaults,umask=0222 0 0
/dev/sdb2 /mnt/my_ntfs_drive_D ntfs-3g ro,defaults,umask=0222 0 0
/dev/sdb3 /mnt/my_ntfs_drive_E ntfs-3g ro,defaults,umask=0222 0 0

When you reboot, you should find your data where you want it.

= Guide to Adding a Hard Drive to Fedora =

This is a good guide, for advanced users, to adding a hard drive to Fedora:

http://fedoranews.org/tchung/storage/

And a good fedora 9 guide here, including a section on adding a hard drive here:

http://www.mjmwired.net/resources/mjm-fedora-f9.html