Project

General

Profile

Nothing but Headaches, Brick Walls, and getting close to sheer insanity !!!

Added by BlackPine almost 4 years ago

All I want to do is set up some local pages on my laptop for several user accounts, and have Lighty serve them when someone connects to my IP from the cloud, or from WiFi. That should NOT be this difficult for someone that has been messing with this stuff since Slackware v3.7...

Just upgraded from v1.4.35 to .55, and I've noticed that the directory architecture has changed quite a bit.
The previous version even placed an 'index' script in the doc-root to show me it had installed correctly, this version did NOT, and also on 'install' moved NONE of the .conf files to the /etc tree. I am guessing that ALL of the config files in the source /doc dir should be in the /etc/lighttpd/ tree ? Why do I need to GUESS at this stuff ? What happened to "standardization" ?!

The previous version/install would deliver the html files to a 'localhost' call on the same machine, but NOT the graphics or images. I'm not sure it's not a 'permission thing' on the directories or files so I thought I would check here before my laptop grows wings. I realize that the documentation is written NOT for a novice, and I HAVE R! T! F! M! ... But I see nowhere in there any mention of permissions or outlining the chances in the install tree (I see it's now back to SRV again, last few versions ago the htdocs were under var/www/.

Ideally I would like to have lighty deliver whatever html/image content is under each particular users' ~/www/(htdocs) tree, but for now I'll settle with having a common set of content served from /srv/www/(htdocs) to ANY 'localhost' or remote connection to :80 or :8080...

Is there a comprehensive outline anywhere that diagrams the default tree for THIS version of Lighty ?
With file/dir permissions needed to have the server access the content ?

I run the latest update of Ubuntu 16.04.1LTS Xenial Xerus (Kernel v4.15.0-91-generic x86_64)
and use SeaMonkey v1.4.55 (edit) to create the simple foundation html scripts for the pages.
Not doing anything fancy with css or csmapping at the moment, but will need to process php scripts.

Perhaps I am missing something along the way, and I'm weary of wasting time with this, so if there is a Lighty-For-Dummies Doc somewhere, I'm ready to start from square One, just to be sure I don't miss anything.

Now on to trying to restore the Monkey that lost his mind...
All my email/nntp, settings, login data gone... <sigh>


Replies (1)

RE: Nothing but Headaches, Brick Walls, and getting close to sheer insanity !!! - Added by gstrauss almost 4 years ago

Your words convey that you are not as experienced as you give yourself credit.

Just upgraded from v1.4.35 to .55,

That is simply negligent. lighttpd 1.4.35 is over 6 years old and twenty (20) full releases of lighttpd out-of-date (and over 1600 code commits).

Why do I need to GUESS at this stuff ?

Probably because you appear not to understand the basic conventions of software releases, including the concept of release notes. Since I have been putting together the release notes (1.4.40+), I attempt to highlight behavior changes in the release notes, and try to give notice of scheduled behavior changes more than one release in advance.

That said, it appears that you're complaining about how things have been packaged by your choice of Linux distro. This forum is at lighttpd.net, where lighttpd is developed. There are many, many distros and each distro has its own volunteers who package lighttpd.

(I see it's now back to SRV again, last few versions ago the htdocs were under var/www/.

Please direct your complaints about packaging layout to the forums of your distro of choice. If I am incorrect in that assessment, maybe you are assuming that a make install of lighttpd source code will magically integrate with the packaging choices of your favorite distro. That is unlikely. The Ubuntu package of lighttpd defines which user and locations that will be used by default on Ubuntu. The Ubuntu startup scripts for lighttpd are part of the Ubuntu package of lighttpd.

lighttpd itself can be run by any user with any config file and serve files from any configured location, as long as that user has permissions to those files and directories.

What happened to "standardization" ?!

I am under the strong impression that you do not know what that means.
./configure --help notes that the default installation from source code is into /usr/local, a fairly common convention.

Ideally I would like to have lighty deliver whatever html/image content is under each particular users' ~/www/(htdocs) tree

mod_userdir has always been part of lighttpd 1.4.x.

I HAVE R! T! F! M!

Clearly not if you did not find mod_userdir

Perhaps I am missing something along the way, and I'm weary of wasting time with this, so if there is a Lighty-For-Dummies Doc somewhere, I'm ready to start from square One, just to be sure I don't miss anything.

You will likely be much more successful once you disabuse yourself of the flawed notion that you somehow are more special or know better than others.

The lighttpd documention on this site -- which is far from perfect and assuredly has its own flaws -- begins under the Wiki tab in the menu bar of this page, or https://redmine.lighttpd.net/projects/lighttpd/wiki/

Have you considered using your favorite search engine to search for "lighttpd" and "Ubuntu"?

    (1-1/1)