A couple things..

[magn2o]

First off, let me just say that Amahi installed without a hitch and is running great. Really, it was easier than I expected. That being said, I have a few questions:

a) Do you recommend performing a regular "yum update"? Or should we just simply leave package versions as they were installed?

b) Apache. Are there any known issues regarding mod_proxy with Amahi? I've got SABnzbd installed and running fine, however, I'm trying to hide it behind an Apache proxy but for some reason or another Apache doesn't seem to want to handle regular proxy directives. I have 3 other boxes running Apache using the same proxy configuration and it works fine.

c) Is there a way (via the UI) to disable samba/shares? I have all of my files stored on a separate OpenFiler NAS shared to Amahi via NFS which is all working fine. For the time being, I've disabled SMB via console; just wanted to know if there was a preferred way.


More info on the proxy:

Note: I can access the SABnzbd interface flawlessy via http://hda:8080/sabnzbd

Code: Select all

[root@localhost ~]# telnet localhost 8080 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. ^] telnet> quit Connection closed.

/etc/httpd/conf.d/sabnzbd.conf (I've also tried appending to 04-platform.conf with the same results)

Code: Select all

<Location /sabnzbd> Order deny,allow Deny from all Allow from all ProxyPass http://localhost:8080/sabnzbd ProxyPassReverse http://localhost:8080/sabnzbd </Location>

/etc/httpd/conf/httpd.conf

Code: Select all

LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_balancer_module modules/mod_proxy_balancer.so LoadModule proxy_ftp_module modules/mod_proxy_ftp.so LoadModule proxy_http_module modules/mod_proxy_http.so LoadModule proxy_connect_module modules/mod_proxy_connect.so

Whenever I try to access http://hda/sabnzbd I get a 400 Bad Request, "Your browser sent a request that this server could not understand."

[cpg]

First off, let me just say that Amahi installed without a hitch and is running great. Really, it was easier than I expected.

nice to hear!

a) Do you recommend performing a regular "yum update"? Or should we just simply leave package versions as they were installed?

it's really up to you. it depends on how aggressively you want to manage your server and how hands-on you want to be.

personally, i like stability, so i only update when i need a particular thing (say for a security update or a feature), or want to get to the latest and have the time to handle any potential breakages.

speaking for the amahi team, we update amahi packages automatically, however, we do not update all of fedora automatically, unless it;s a serious security issue. that's what seems to be what most users wanted.

we only had to release updates of fedora packages twice in the past. one for a widespread DNS issue and the other for the fedora 9.5 release.

b) Apache. Are there any known issues regarding mod_proxy with Amahi? I've got SABnzbd installed and running fine, however, I'm trying to hide it behind an Apache proxy but for some reason or another Apache doesn't seem to want to handle regular proxy directives. I have 3 other boxes running Apache using the same proxy configuration and it works fine.

no known issues (that i know of - others may). i am not familiar with mod_proxy, though.

c) Is there a way (via the UI) to disable samba/shares? I have all of my files stored on a separate OpenFiler NAS shared to Amahi via NFS which is all working fine. For the time being, I've disabled SMB via console; just wanted to know if there was a preferred way.

no preferred way - maybe one day we add settings to do it. for now -- chkconf smb off; chkconf nmb off;

Note: I can access the SABnzbd interface flawlessy via http://hda:8080/sabnzbd

did you try installing it as a web app?

that is the very purpose of web apps.

i think i made sabnzbd work before as a web app and you would just access it as http://sabnzbd

[magn2o]

did you try installing it as a web app?

that is the very purpose of web apps.

i think i made sabnzbd work before as a web app and you would just access it as http://sabnzbd

From what I could tell, when creating a "web app" it prompts for the path to the app -- SABnzbd+ runs on top CherryPy and as such is a port-based daemon, much like mt-daapd.

I did get it working, however. Here's my config file:

/etc/httpd/conf.d/1029-nzb.conf

Code: Select all

<VirtualHost *:80> ServerName nzb ServerAlias nzb.localdomain.local ProxyRequests off <Proxy *> Order deny,allow Allow from all </Proxy> ProxyPass / http://localhost:8080/sabnzbd/ </VirtualHost>

Now, ideally I would like the servername called sabnzbd -- however, for some reason or another it doesn't work (for me at least), so nzb will have to do.

If I create a new web app named sabnzbd, everything creates fine -- however, if I click the http://sabnzbd link I get a 404. If I give it any other name (ie, nzb), I get the Apache welcome page. That threw me for a loop for about an hour..

[cpg]

BTW, we have made sbnzbd work as a one-click app with the help of the information in your post!

as we maintain more and more apps we will start releasing them and at that point we create a new forum per app.

the forum for sab is the first one: http://forums.amahi.org/viewforum.php?f=23

the idea is that as we move along the main package maintainer and the experts in this app can share tips in how to package it in a more seamless manner.

thanks for your patience also.

we're very close to releasing the new installer, which is going to make things much easier.