From rlharris at oplink.net  Mon Aug 13 23:33:26 2018
From: rlharris at oplink.net (rlharris at oplink.net)
Date: Tue, 14 Aug 2018 06:33:26 -0000
Subject: [pm-h] blogging with blosxom
Message-ID: <8863dae15f3e2d72dec34f4f51882401.squirrel@webmail.oplink.net>

I am running Debian Jessie.  I wish to use the blogging package Blosxom,
which was written in Perl, about fifteen years ago. The last development
work on Blosxom appears to have been done about ten years ago.

The original CGI script and documentation are available on sourceforge,
http://blosxom.sourceforge.net/documentation/users/; all configuration
parameters are in the Perl script.

Debian has a Blosxom package which allows use of a separate configuration
file.  The Debian package places some files in locations other than the
locations used in the original script.

Blosxom can generate a web page dynamically in response to a web request;
alternatively, Blosxom can generate a set of static web pages which can be
uploaded to a remote web server.  Blosxom also generates an RSS feed.

I am interested in Blosxom primarily because it can publish entries
composed entirely in plain text (but HTML formatting can be added, as
desired).

I have two specific problems, which the documentation does not seem to
address:

(1) I do not know how to trigger Blosxom in static mode.

(2) Apache2 is running on this machine, but I do not know how to enable
Apache to find and serve the blog which is produced, either dynamic or
static.

I would be grateful for assistance.

RLH

From jlbprof at gmail.com  Tue Aug 14 05:00:11 2018
From: jlbprof at gmail.com (Julian Brown)
Date: Tue, 14 Aug 2018 07:00:11 -0500
Subject: [pm-h] blogging with blosxom
In-Reply-To: <8863dae15f3e2d72dec34f4f51882401.squirrel@webmail.oplink.net>
References: <8863dae15f3e2d72dec34f4f51882401.squirrel@webmail.oplink.net>
Message-ID: <CAMzD1Sp=Hz897ZRLkBbuD4qLn3b06+WgDFjZkdT7EdyF5YFk1g@mail.gmail.com>

Apache configuration is not easy, but once you get it set up it will run
forever without much interaction with you.

That being said:

- Have you ever done Apache configuration?
- The easiest thing to do is to add Bloxsum to one of your existing
websites on Apache
- We will have to do this interactively so do the following for me:

cd /etc/apache2/
hustle at HustleWebserver:/etc/apache2$ tree sites-available
sites-available
??? 000-default.conf
??? 001-learngigs.conf
??? 001-learngigs-le-ssl.conf
??? default-ssl.conf

0 directories, 4 files
hustle at HustleWebserver:/etc/apache2$ tree sites-enabled
sites-enabled
??? 000-default.conf -> ../sites-available/000-default.conf
??? 001-learngigs.conf -> ../sites-available/001-learngigs.conf
??? 001-learngigs-le-ssl.conf ->
/etc/apache2/sites-available/001-learngigs-le-ssl.conf

Once we identify which "website" to use, you will need to edit the conf
file.

Here is an example of how you will edit the file:

 11     <Directory /home/hustle/learn-cgi-bin>
 12         Options +ExecCGI
 13         AddHandler cgi-script .cgi .pl
 14         Require all granted
 15         AllowOverride all
 16         Allow from all
 17     </Directory>

 40     ScriptAlias "/cgi-bin/" "/home/hustle/learn-cgi-bin/"


You would identify the directory where the bloxsum cgi script resides, then
copy the above to the config file and change "/home/hustle/learn-cgi-bin"
to the directory where bloxsum resides.  Add the ScriptAlias line as well,
changing my directory to your bloxsum directory.

reboot your system and bloxsum should work something like this:

http://yourwebsite.com/cgi-bin/bloxsum.cgi

To be sure ps aux | grep httpd to make sure Apache is running.  If it is
not look in the logs probably in /var/log/apache2 to figure it out,
probably you typed something wrong in the conf file and got a syntax
error.   Fix it, rinse lather repeat.

As far as configuring it for static sites, you will need to read the config
file that comes with bloxsum and see if you can parse that out.

Get the site up first than we can look at your bloxsum config file and try
and fix that.

Hope that does not overwhelm.

Julian












On Tue, Aug 14, 2018 at 2:19 AM <rlharris at oplink.net> wrote:

> I am running Debian Jessie.  I wish to use the blogging package Blosxom,
> which was written in Perl, about fifteen years ago. The last development
> work on Blosxom appears to have been done about ten years ago.
>
> The original CGI script and documentation are available on sourceforge,
> http://blosxom.sourceforge.net/documentation/users/; all configuration
> parameters are in the Perl script.
>
> Debian has a Blosxom package which allows use of a separate configuration
> file.  The Debian package places some files in locations other than the
> locations used in the original script.
>
> Blosxom can generate a web page dynamically in response to a web request;
> alternatively, Blosxom can generate a set of static web pages which can be
> uploaded to a remote web server.  Blosxom also generates an RSS feed.
>
> I am interested in Blosxom primarily because it can publish entries
> composed entirely in plain text (but HTML formatting can be added, as
> desired).
>
> I have two specific problems, which the documentation does not seem to
> address:
>
> (1) I do not know how to trigger Blosxom in static mode.
>
> (2) Apache2 is running on this machine, but I do not know how to enable
> Apache to find and serve the blog which is produced, either dynamic or
> static.
>
> I would be grateful for assistance.
>
> RLH
> _______________________________________________
> Houston mailing list
> Houston at pm.org
> http://mail.pm.org/mailman/listinfo/houston
> Website: http://houston.pm.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/pipermail/houston/attachments/20180814/ba02652b/attachment-0001.html>

From rlharris at oplink.net  Tue Aug 14 06:30:38 2018
From: rlharris at oplink.net (rlharris at oplink.net)
Date: Tue, 14 Aug 2018 13:30:38 -0000
Subject: [pm-h] blogging with blosxom
In-Reply-To: <CAMzD1Sp=Hz897ZRLkBbuD4qLn3b06+WgDFjZkdT7EdyF5YFk1g@mail.gmail.com>
References: <8863dae15f3e2d72dec34f4f51882401.squirrel@webmail.oplink.net>
 <CAMzD1Sp=Hz897ZRLkBbuD4qLn3b06+WgDFjZkdT7EdyF5YFk1g@mail.gmail.com>
Message-ID: <f32a0717ee5eac7d1df1ff754a9f796c.squirrel@webmail.oplink.net>

On Tue, August 14, 2018 12:00, Julian Brown wrote:
> Apache configuration is not easy, but once you get it set up it will run
> forever without much interaction with you.
>
> That being said:
>
> - Have you ever done Apache configuration?

Thanks, Julian.  Early this afternoon, I should be free to work through
your procedure step-by-step; I am tied up this morning.

I have gone through an Apache configuration, but not recently.

However, the Debian "webserver" task is installed and running, so that
giving the URL "localhost" to a browser displays the Apache2 Debian
default page "It Works!"

Ultimately, I plan to have the blog running under its own domain name on
Siteground or Hostgator.


RLH

From jlbprof at gmail.com  Tue Aug 14 06:35:00 2018
From: jlbprof at gmail.com (Julian Brown)
Date: Tue, 14 Aug 2018 08:35:00 -0500
Subject: [pm-h] blogging with blosxom
In-Reply-To: <f32a0717ee5eac7d1df1ff754a9f796c.squirrel@webmail.oplink.net>
References: <8863dae15f3e2d72dec34f4f51882401.squirrel@webmail.oplink.net>
 <CAMzD1Sp=Hz897ZRLkBbuD4qLn3b06+WgDFjZkdT7EdyF5YFk1g@mail.gmail.com>
 <f32a0717ee5eac7d1df1ff754a9f796c.squirrel@webmail.oplink.net>
Message-ID: <CAMzD1SqoMwUncpb+oQn5iKG5hxL+2xeOoYNCCO7myg_ph=OaEw@mail.gmail.com>

If it is only configured for localhost, there will be more work you need to
do.

Do you plan to have this available to the public?  That is you want real
webtraffic driven to your site?

Julian

On Tue, Aug 14, 2018 at 8:31 AM <rlharris at oplink.net> wrote:

> On Tue, August 14, 2018 12:00, Julian Brown wrote:
> > Apache configuration is not easy, but once you get it set up it will run
> > forever without much interaction with you.
> >
> > That being said:
> >
> > - Have you ever done Apache configuration?
>
> Thanks, Julian.  Early this afternoon, I should be free to work through
> your procedure step-by-step; I am tied up this morning.
>
> I have gone through an Apache configuration, but not recently.
>
> However, the Debian "webserver" task is installed and running, so that
> giving the URL "localhost" to a browser displays the Apache2 Debian
> default page "It Works!"
>
> Ultimately, I plan to have the blog running under its own domain name on
> Siteground or Hostgator.
>
>
> RLH
> _______________________________________________
> Houston mailing list
> Houston at pm.org
> http://mail.pm.org/mailman/listinfo/houston
> Website: http://houston.pm.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/pipermail/houston/attachments/20180814/cfadb767/attachment.html>

From rlharris at oplink.net  Tue Aug 14 08:02:46 2018
From: rlharris at oplink.net (rlharris at oplink.net)
Date: Tue, 14 Aug 2018 15:02:46 -0000
Subject: [pm-h] blogging with blosxom
In-Reply-To: <CAMzD1SqoMwUncpb+oQn5iKG5hxL+2xeOoYNCCO7myg_ph=OaEw@mail.gmail.com>
References: <8863dae15f3e2d72dec34f4f51882401.squirrel@webmail.oplink.net>
 <CAMzD1Sp=Hz897ZRLkBbuD4qLn3b06+WgDFjZkdT7EdyF5YFk1g@mail.gmail.com>
 <f32a0717ee5eac7d1df1ff754a9f796c.squirrel@webmail.oplink.net>
 <CAMzD1SqoMwUncpb+oQn5iKG5hxL+2xeOoYNCCO7myg_ph=OaEw@mail.gmail.com>
Message-ID: <bc3bd315bde920ade6462171e8b9d353.squirrel@webmail.oplink.net>

On Tue, August 14, 2018 13:35, Julian Brown wrote:
> If it is only configured for localhost, there will be more work you need
> to do.
>
> Do you plan to have this available to the public?  That is you want real
> webtraffic driven to your site?

Yes; public.  That is why I am going to use a domain name www.myblog.org
or whatever, not www.mysite.org/blog.

I would like to have the blog display also on localhost, for testing of
formats and so forth.

RLH

From jlbprof at gmail.com  Tue Aug 14 08:05:10 2018
From: jlbprof at gmail.com (Julian Brown)
Date: Tue, 14 Aug 2018 10:05:10 -0500
Subject: [pm-h] blogging with blosxom
In-Reply-To: <bc3bd315bde920ade6462171e8b9d353.squirrel@webmail.oplink.net>
References: <8863dae15f3e2d72dec34f4f51882401.squirrel@webmail.oplink.net>
 <CAMzD1Sp=Hz897ZRLkBbuD4qLn3b06+WgDFjZkdT7EdyF5YFk1g@mail.gmail.com>
 <f32a0717ee5eac7d1df1ff754a9f796c.squirrel@webmail.oplink.net>
 <CAMzD1SqoMwUncpb+oQn5iKG5hxL+2xeOoYNCCO7myg_ph=OaEw@mail.gmail.com>
 <bc3bd315bde920ade6462171e8b9d353.squirrel@webmail.oplink.net>
Message-ID: <CAMzD1SqW_vZkNWYKJY3vWfyhWJckyyGC=1_+L9TkpMBtfKC9fw@mail.gmail.com>

we can do both

On Tue, Aug 14, 2018 at 10:03 AM <rlharris at oplink.net> wrote:

> On Tue, August 14, 2018 13:35, Julian Brown wrote:
> > If it is only configured for localhost, there will be more work you need
> > to do.
> >
> > Do you plan to have this available to the public?  That is you want real
> > webtraffic driven to your site?
>
> Yes; public.  That is why I am going to use a domain name www.myblog.org
> or whatever, not www.mysite.org/blog.
>
> I would like to have the blog display also on localhost, for testing of
> formats and so forth.
>
> RLH
> _______________________________________________
> Houston mailing list
> Houston at pm.org
> http://mail.pm.org/mailman/listinfo/houston
> Website: http://houston.pm.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/pipermail/houston/attachments/20180814/571bcb6b/attachment.html>

From jlbprof at gmail.com  Tue Aug 14 08:12:13 2018
From: jlbprof at gmail.com (Julian Brown)
Date: Tue, 14 Aug 2018 10:12:13 -0500
Subject: [pm-h] blogging with blosxom
In-Reply-To: <bc3bd315bde920ade6462171e8b9d353.squirrel@webmail.oplink.net>
References: <8863dae15f3e2d72dec34f4f51882401.squirrel@webmail.oplink.net>
 <CAMzD1Sp=Hz897ZRLkBbuD4qLn3b06+WgDFjZkdT7EdyF5YFk1g@mail.gmail.com>
 <f32a0717ee5eac7d1df1ff754a9f796c.squirrel@webmail.oplink.net>
 <CAMzD1SqoMwUncpb+oQn5iKG5hxL+2xeOoYNCCO7myg_ph=OaEw@mail.gmail.com>
 <bc3bd315bde920ade6462171e8b9d353.squirrel@webmail.oplink.net>
Message-ID: <CAMzD1Sp3DP=ky_yWXRsA3x2zkaNjQxVZqJ6jnsChy=6PS5o7BQ@mail.gmail.com>

Create a file in /etc/apache2/sites-available

Name it mysite.conf

# assuming your static files are in /home/mysite/public_html
# and your bloxsum is in /home/mysite/cgi-bin

<VirtualHost *:80>
    SetEnv PERL5LIB /where your PERL5 stuff is, if you need it, if you dont
remove it

    <Directory /home/mysite/public_html>
        Options FollowSymlinks
        Require all granted
        AllowOverride all
        Allow from all
    </Directory>

    <Directory /home/mysite/cgi-bin>
        Options +ExecCGI
        AddHandler cgi-script .cgi .pl
        Require all granted
        AllowOverride all
        Allow from all
    </Directory>

    # The ServerName directive sets the request scheme, hostname and port
that
    # the server uses to identify itself. This is used when creating
    # redirection URLs. In the context of virtual hosts, the ServerName
    # specifies what hostname must appear in the request's Host: header to
    # match this virtual host. For the default virtual host (this file) this
    # value is not decisive as it is used as a last resort host regardless.
    # However, you must set it for any further virtual host explicitly.
    #ServerName www.example.com

    ServerAdmin webmaster at localhost
    DocumentRoot /home/mysite/public_html

    # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
    # error, crit, alert, emerg.
    # It is also possible to configure the loglevel for particular
    # modules, e.g.
    #LogLevel info ssl:warn

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

    ScriptAlias "/cgi-bin/" "/home/mysite/cgi-bin/"

    # For most configuration files from conf-available/, which are
    # enabled or disabled at a global level, it is possible to
    # include a line for only one particular virtual host. For example the
    # following line enables the CGI configuration for this host only
    # after it has been globally disabled with "a2disconf".
    #Include conf-available/serve-cgi-bin.conf
</VirtualHost>

The virtual host <*:80> will put it on all tcp/ip addresses including
127.0.0.1, and your public ip.

Then in

/etc/apache2/sites-enabled

ln -s /etc/apache2/sites-available/mysite.conf
/etc/apache2/sites-enabled/mysite.conf

Put some test index.html in /home/mysite/public_html

then try http://localhost/index.html

and see if it responds.

if not go to the logs



On Tue, Aug 14, 2018 at 10:03 AM <rlharris at oplink.net> wrote:

> On Tue, August 14, 2018 13:35, Julian Brown wrote:
> > If it is only configured for localhost, there will be more work you need
> > to do.
> >
> > Do you plan to have this available to the public?  That is you want real
> > webtraffic driven to your site?
>
> Yes; public.  That is why I am going to use a domain name www.myblog.org
> or whatever, not www.mysite.org/blog.
>
> I would like to have the blog display also on localhost, for testing of
> formats and so forth.
>
> RLH
> _______________________________________________
> Houston mailing list
> Houston at pm.org
> http://mail.pm.org/mailman/listinfo/houston
> Website: http://houston.pm.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/pipermail/houston/attachments/20180814/f562d0dd/attachment-0001.html>