Pupserv

[Evil20071]

Goal:
To create a fully functional production server version of Puppy.

Abbreviation key:

1. s - Stripped
2. m - multiple versions
3. f - fat (nothing removed)

Pupserv needs:

1. X64 *Buntu/RHEL/Debian compatible Puppy base (s)
2. PHP (mf)
3. Apache (f)
4. MySQL (mf)
5. FTP server
6. SMTP Server

I want to use a *buntu, RHEL or Debian compatible base as both of these linux distros have been used as Web/Datacenter server OS's in the mainstream, and have many packages already available for many of the server parts that Pupserv will need. Additional services may come in handy, lik3 a way to process ASP pages, though I know of absolutely none such ASP server for *nix systems. Suggestions are welcome. I do work a full-time job and now have a 2 month old baby, so this is a project that will take quite some time. I may be able to get some friends from outside the Puppy community to lend me a few extra hands.

[Evil20071]

Some have voiced concerns about running Puppy as a server as root. As Puppy doesn't really have multiuser support, this is something else we may look into after getting the alpha up and running. I know there has been talk about multiuser support and Puppy for a long long time, and the fact that it was stripped from the core intentionally should prove to be interesting. Some system for integrating the multiuser system from *buntu into Pupserv may be in order, though I'm not sire if that's possible, or even feasible at this point. Rather, I think setting up some form of remote management system that has multiuser support built in along with access rights would be more doable. Leave the root access to the physical server level only. I'm thinking a web applet written in Java/PHP may be in order. Ideas?

[Evil20071]

Reserved for status update

[Evil20071]

Ok. So, I have decided on my base being Debian compatible. Debian, after checking out their repositories, has, IMHO, the best sets of Server packages to make this an easier project. I will begin working on this build shortly.

[Atle]

Interesting... I look forward to see what comes out of this:-)

[Evil20071]

As do I. It's my first such attempt, so I'm kinda nervous. Hence me taking my time with it. I'm going to have to figure out which puplet to start off with. I currwntly run Slacko, myself. I'm going to be making good use of VirtualBox for this one, and I'm going to see just what Woof can really do, as well.

[Q5sys]

You dont have to run your server as root. When I made Cloudpup ( http://murga-linux.com/puppy/viewtopic.php?t=90788 ), I set it up so that nginx and sqlite would all run as spot.

It's not as secure as a true legit user account, but its better than full root.

[NeroVance]

Second Q5sys, spot server is what's supposed to be done. Multiuser could be good if you are crazy enough to try a terminal server, but I digress.

[Evil20071]

I may well try to figure out how to set it up with full multiuser support...

[efiabruni]

I have been using my puppy (saluki) as a webserver on my laptop since 2012. Hiawatha (the built in webserver) runs as "webuser" I think and I also installed XMPP and have it running as "nobody".

You can see it in action at: https://tine.pagekite.me

I think whether the underlying system runs as root or not should not matter as long as there is a root password.

Wouldn't it be easier to make a derivative of an existing puppy distro? DebianDog or Tahrpup comes to mind.

I'm interested in helping with the few skills I have (testing, packaging) because I will probably end up using it

[Evil20071]

I do believe you have a good idea there. Debiandog woild be a perfect fit as its already a .deb cokpatible system.

[Evil20071]

Started working on building tonight. Having a few issues with Woof, however. Once I figure that out, I'll get my alpha rollout going.

Currently going to make a fresh Woof2 build of a Debian compatible puppy with the bare minimum complete with a full web server, Filezilla FTP Server and I'm still looking at SMTP servers to try and include in it as well.

[Moose On The Loose]

Goal:
To create a fully functional production server version of Puppy.

I have used Puppy 528 as both SAMBA server and web server at home and from time to time at work. I things in this order from boot:

1) Get network going
2) Sync the time via the NTP
3) Compose status.txt and status.html
4) Start the servers

Doing the NTP first means that the time for everything won't ever step earlier. The computer in question had a clock that ran a bit fast when power was off.