Amahi Forums

I tried to install on virtual box last night following the instructions on the wiki with fedora 17, and the system refused to configure. I guess the problem was that on my desktop the Ethernet refuses to map to "eth0" and I was using it in bridged mode, hence amahi couldn't change the device name to eth0 from the system's device name.
I was wondering how to go around this in virtual box, if anyone knows... I wanted to use bridged mode so I could access the "server" from the rest of the network, however if this can't be done with the device name, that could cause an issue.
I don't think this is a "bug report", although that aside, the entire thing installed without a glitch upto that point.

We have a wiki entry about eth0/1 interface changes. VBox doesn't change interface names... it abstracts the interface for the VM.

Recently did a yum update and the page shows.
Added some music to my music shares folder. Transfer go well and the files are there!

Hi there, ... sorry for the lack of updates. We are working on some amahi.org issues and also further styling of the amahi 7 UI. We're working on error checking and validations.

More soon ...

Quick update .. Here is where we're stuck at ...

https://dl.dropbox.com/u/364883/Screens ... ations.png

trying to do validations for the forms we have. The way we have them in the top of the tree is kind of tricky, with validations done in the client (the browser).

It's too hard to follow, debug and fix. I am about to scrap it it all.

If you have lots of Javascript experience and want to get involved, please let us know!

Is this holding up Fedora 17 progress? Is it possible to get things working with the current platform, then modify as we go?

Is this holding up Fedora 17 progress? Is it possible to get things working with the current platform, then modify as we go?

Thats a good idea, but I have another suggestion: What about jumbing over f17? Fedora 18 will be released on 2013-01-08. I'm sure this will be shock for many Amahi-on-fedora-users (like me). But on the other side there is a chance to release the new Amahi platform as bleeding edge technology. In case you will decide to release on f18 the whole work done until now wont be a waste of time as F18 still will use Ruby 1.9.3. But they will ship Rails 3.2

What do you think?

If F18 is fairly near, and if it's a good fit, we can jump right to it!

I agree that bigfoot65's idea is a good idea.

We will have to put together another release. This release of the platform is fairly different than before and we still need to automate the release generation. I will have to think about this a little and see if we can make headway in the next couple of days.

Sounds great guys!

I'm running the F18 Alpha with XFCE and it's quite great to be bleeding edge on a desktop. Here's a supportive post for the F18 release!

Hi, we released a new version of the platform (hda-platform-6.2.4) to the f17 repo and it's ready for testing.

This new release has a lot of the changes that were getting us stuck (so-called client-side validations -- ways to validate the input the user enters, in the browser). We also made some changes to make packaging the release a little easier, speeding up the process.

Because these are some sweeping changes, it's possible we broke something. Please report major issues here. We need to come up with a checklist of things to test, though, really, it's every single feature in every single page of the platform. I really mean it, ... from changing a user password to deleting a non-admin, etc.

Basically, anything you can do to break it and succeed in doing so should be considered a bug!

Please report issues here!

- I don't know if it's intentional, but in Midori or Firefox, the apps page only shows the clickable hand when rolling over the app name, and not while rolling over the entire app bar space.

- current admin user cannot un-admin self

- cannot delete a user that is admin status

- perhaps for security sake, initially force user passwords to have certain complexities, and allow this to be changed in the advanced options of the dashboard.

- after a successful password change, there is no space between "ChangePassword changed successfully"

-