SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
ive had the fortunate experience of succesfully serving my webpage thru apache2*53.
hey two quick questions
1. is it possible to serve a public page as well as a private page simultaneously ? Ive built a page
for my wife and only want her login or hostname able to see it here in our LAN.
2. IYHO what is the best tool, ported to Linux that is, for building graphics for a webpage like photoshop, freehand, etc... im using inkscape right now and ISO a possible alternate
If her computer uses a static IP, it should be pretty easy. If not, it's possible, just a bit trickier.
You can create an alias to her page as follows:
Code:
Alias /wife "/home/wife"
<Directory "/home/wife">
AllowOverride Options FileInfo
Order allow,deny
Allow from 192.168.1.1 (or whatever her computer's IP address is)
</Directory>
This requires no login.
If you want to require login to see that page, you'll have to add a userid to the groups.conf file and a md5-hashed password (which you might be able to copy from /etc/shadow) in .htpasswd. Then it can be used as follows:
Code:
Alias /wife "/home/wife"
<Directory /home/wife>
AuthType Basic
AuthName "Wife's Eyes Only"
AuthUserFile /etc/apache/.htpasswd
AuthGroupFile /etc/apache/groups.conf
Require group wife
Satisfy All
AllowOverride None
</Directory>
You can also serve up an intranet site using name virtualhosts in Apache. If the request doesn't come to the right FQDN, the user doesn't get the webpage they were expecting.
On my system, the intranet site doesn't have a real name. (The TLD I'm using for my internal network isn't real). It exists on my DNS server, but that's the only place it exists. That way, if a user wants the internal server (used as a testbed for php applications, mostly), they just have to type in http://intranet.mylocaldomain, and for mail, it's imap.mylocaldomain and smtp.mylocaldomain
ok I think were moving in the right direction I tried both ideas you sugg
but now im getting prompted for a usrnm/pwd and cannot get past
she is connecting from a M$/IE client and my server is listening on both
http 80 and https 443
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.