Apache and Tomcat on a Kubuntu machine

[MAHillsgrove]

Yes, I know. Someone will suggest just downloading the LAMP server. But I really like the interface for Kubuntu. The LAMP server is essentially useless for anything except being a command line based server. I wish that a GUI was an install option on Ubuntu Server.

I don't need a high power web server, just a Tomcat/Apache server to play with while I learn it for work. Somehow I've (through no fault of my own) become the expert at work. It seems that admiting that you run it at home is sufficient these days. Current project is Apache Tomcat. I also need to learn how to build web pages. What product are people using these days under Linux? Any good WYSIWYG drag and drop things for dummies you would recommend?

At work we are using Red Hat. Not my choice. All my machines at home are Kubuntu so I would rather use that to learn on.

Any thoughts?

[arochester]

Re: Apache and Tomcat on a Kubuntu machine

Perhaps someone will correct me... normally a server doesn't have a GUI, but there is no reason why you can't put a GUI on a server...

I also need to learn how to build web pages. What product are people using these days under Linux? Any good WYSIWYG drag and drop things for dummies you would recommend?

Have a look at http://linuxappfinder.com/developmen...websiteeditors . I would use something relatively simple like KompoZer but some people might use something more comlex like Quanta or Amaya

[Ole Juul]

Re: Apache and Tomcat on a Kubuntu machine

I recently set up a server at home and was looking for some easy tools myself. The idea I had was that a GUI might help me get started. I didn't really find anything except dtc which you can find with adept. It's way more than most people need and doesn't easily do the small things. In looking around I found this list too:
http://www.web-hosting-top.com/web-h...control-panels

The problem is that servers are not really a GUI kind of thing. What they do is intended to be viewed remotely. I think most people would run them headless, and that's what I do with mine. For another, what do we really need to do that could benefit from a GUI? If you look at the Ubuntu Server Guide, you'll see what I mean. There's not really anything for a GUI to do there: https://help.ubuntu.com/8.04/serverguide/C/index.html

As a beginner, I also get a bit of a thrill every time I use wake-on-lan to start the server, and then log in using telnet or ssh. That's pretty cool. PS: you can see a picture of my latest pride and joy here: http://voxigo.wordpress.com/

[aged hippy]

Re: Apache and Tomcat on a Kubuntu machine

I find Quanta to be excellent for building web pages (and sites).

Have a look here and see what you think: http://quanta.kdewebdev.org/

With some minor adjustments it will also run on KDE 4.

[MAHillsgrove]

Re: Apache and Tomcat on a Kubuntu machine

These days there is no good reason to not run a GUI on a server or any other machine. Way back when in the dawn of computer time, a GUI could easilly suck up half the processor for something as simple as moving a mouse. These days of dual cores and mega fast busses, that just isn't so. Running without a GUI is a macho thing on Linux rather than a necessity for performance.

But the idea isn't to compete with Yahoo, it's just to serve a few pages to see how it all works, how to configure Apache and Tomcat without losing the functionality of everything else.

I'll look at Quanta, which I think is downloadable from the repository.

[aged hippy]

Re: Apache and Tomcat on a Kubuntu machine

"I'll look at Quanta, which I think is downloadable from the repository." - Yes, with Adept or Synaptic.

As well as Cervisia, KXSLDbg, Kommander Editor, and Kompare (which i've never had a use for), it will also pull in KLinkstatus.... which i find invaluable.

[Ole Juul]

Re: Apache and Tomcat on a Kubuntu machine

First, I understand your frustration regarding your interface of choice. I too have found it difficult to get the first grip on some computer project when it seemed like everyone else had a different approach. One would think that by now there was a nice and easy integrated solution to the small/home server issue.

These days there is no good reason to not run a GUI on a server or any other machine.

Actually, on production machines, and certainly server farms, the cost would be huge - and so would be the administrative and security costs. I honestly think that you and I are in the minority regarding our server interests. That would certainly explain the lack of relevant software.

Running without a GUI is a macho thing on Linux rather than a necessity for performance.

With all due respect, I find that a little strong. I think you will have to convince a lot of not very macho people on that one. I'm somewhat autistic and I find a GUI often very difficult - mostly because of the hand-eye coordination, confusing colours, and the use of unfamiliar images as aliases. It is just not an easy way for everyone to understand a computer. There are differences between people other than macho or not.

Apart from that, I agree that for many people a GUI is probably great for operating home servers. I'm sorry I don't know anything about Tomcat or java, but with plain apache (and probably most http servers), if you just want to serve a few web pages then you should be able to do like me and just put the files in /var/www. You can drag and drop them using GUI tools like Konqueror or Dolphin. After that, just type the ip of the machine in the browser and apache will serve up your page.

Here is another idea to simplify home serving. You might find this handy at work too but you have to use static addresses. To eliminate the typing of ip numbers (eg. 192.168.1.2) you can put them in your /etc/hosts file with an alias. That is much easier than using a local domain name server which really is overkill for small networks. Simply add a line with the name of the computer followed by it's preferred name after the ip. In my case it's the same name but it doesn't have to be. One line in my file looks like this:

192.168.1.109 ANA ANA

Now instead of having to type "http:// 192.168.1.109", I only need to type "http:// ana" and the computer which I have named ANA will serve a web page - assuming that it is running an http server. The same goes for "ftp ana" or "telnet ana", and even "gopher ana" if it is running those servers. I put the same /etc/hosts file on all the computers in my network.

I do hope you find some solution that works for you.