thelinuxlink.net

Last night's show I found to be very interesting (every show is interesting, but this one was even more so to me). The eyeOS is a great idea and I'm looking forward to seeing it develop.

So, this morning I set up eyeOS on a L.A.M.P. I have here and now I'm thinking about all the ways one could use an eyeOS system (present and future).

I suppose the "major" use is collaboration, but I thought perhaps we could specify some projects that could benefit.

At the moment, eyeOS can't do much, but it can be a very easy and hassle-free way for users to exchange messages (no spam, viruses, etc.) and create documents between them.

Who/where could use it:

• * A local LUG
  * A classroom
  * In the office on a specific project
  * Religious organizations or other such volunteer group

Anyone like to contribute some ideas?

Maybe this could be a good alternative to Xanga and shit like that.

Tsuroerusu wrote:Maybe this could be a good alternative to Xanga and shat like that.

I was thinking people would have this instead of weblogs but maybe Xanga and MySpace too although then I would have to hate it Although it has more space/bandwidth requirements I would think. I would run it all the time but my dad doesn't want me to waste electricity but I can have my computer automatically turn on while Im at school so I could get around that. Although I would like eyeAMP to support OGG so I could get my music to play from home. Guess my iAudio will work though. It would also be nice if it had a good IDE to program with but that would be very hard to program.

CptnObvious999 wrote:It would also be nice if it had a good IDE to program with but that would be very hard to program.

You just use PHP and AJAX as the guest said on last night's show.

Tsuroerusu wrote:

CptnObvious999 wrote:It would also be nice if it had a good IDE to program with but that would be very hard to program.

You just use PHP and AJAX as the guest said on last night's show.

I don't know AJAX and it would be pretty hard to make an IDE with syntax highlighting and autocompletion like I want even in python. I just would want it so I could program at school without installing anything.

Judland wrote:Who/where could use it:

• * A local LUG
  * A classroom
  * In the office on a specific project
  * Religious organizations or other such volunteer group

Anyone like to contribute some ideas?

I personally see a huge gap in bioinformatics and research that could be easily fulfilled by eyeos; right now, the commonly used tools are few, non-portable and poorly integrated (not to mention closed-source). Especially in academia (where I am), a consistent, web-accessible workarea would be tremendously useful.

I'm definitely going to try and port my phylogenomic tree viewer (looks something like this) to ruby/ajax as soon as I have the time.

CptnObvious999 wrote:I don't know AJAX and it would be pretty hard to make an IDE with syntax highlighting and autocompletion like I want even in python. I just would want it so I could program at school without installing anything.

I offer $50 to whoever ports Vi to eyeOS.

After setting up eyeOS I wanted to have people from outside my router be able to access it. I needed to use an alternate HTTP port since the regular 80 was taken by the admin CP. So I tried using port 8080 because I think thats the alternate http port but after putting "Listen 8080" into my /etc/apache2/httpd.conf and restarting it give me a 404 not found error. I know its using the 8080 because nmap shows it as open on my ip address (192.168.1.103). Anyways anyone know whats wrong or how to fix it?

Are you forwarding 8080 to your eyeos box?

Snarkout wrote:Are you forwarding 8080 to your eyeos box?

Yes but it doesn't even work when I try http://192.168.1.103:8080/eyeos however when I set apache to use port 80 http://192.168.1.103/eyeos it works. I think this is an apache problem.

I wouldn't have anything to do with your router would it?

Found a solution although not the one I was looking for it might actually be better though. I just disabled HTTP for the Access Server option in Administration > Management in the ACP so it uses HTTPS to use the ACP then port forwarded 80 to my box after setting apache to use 80. It works perfectly.

You could also try name-based virtual hosting. That's what I do. Apache will route traffic based on the hostname, and you can hit different sites based on which URL you use.

Look at the comments at the end of httpd.conf.

Uncomment NameVirtualHost *:80, then set up sections for each host.
Here's an example from the Apache docs: Then you can point the browser to http://www.domain.tld to get to documents in /www/domain, and http://www.otherdomain.tld to get pages from /www/otherdomain.

Users outside your LAN would have to make sure these domains resolve to your LAN IP. That might wind up being too complicated, unless you want to use DynDNS or have them edit their hosts file to point to your IP.