Activism | Astrology | Astronomy | Blog | Credit Card Boycott | Firefox Add-Ons | GNU/Linux | How To Guides | Ideas | Languages | Music | Opinions | Pictures | Second Life | Self-Help | Software | Windows

About This Site | Contact Apollia | Disclaimer | Updates

Eryss.Com - Non24.Com

Eryss.Com Forum - Non24.Com Forum

Donations | Services (none available currently)

Request Free/Libre/Open Source Software or Documentation, or Ask Programming Questions (but only if you're very patient)

Or, Donate In Second Life

GitHub

The documentation I wrote and many of the scripts I wrote that are included in this package are under the GNU General Public License v3.0. There are also short, simple scripts by me which are in the public domain.

Other things in this package that aren't by me are under other licenses - see License Info and Icon Info.

The below copyright notice only applies to things by me, except things in the public domain.

Copyright (C) 2013 Apollia

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>.

Contact info: http://astroblahhh.com/contact-apollia.shtml

A copy of the license is included in the section titled GNU General Public License.

The documentation I wrote and many of the scripts I wrote that are included in this package are under the GNU General Public License v3.0. There are also short, simple scripts by me which are in the public domain.

Other things in this package that aren't by me are under other licenses - see License Info and Icon Info.

Why did I choose the GNU General Public License (GPL) rather than the GNU Free Documentation License (GFDL) for the documentation I wrote?

Because the terms in the GFDL about invariant sections made me uneasy. I didn't want modified versions of this page possibly acquiring unremovable new sections. If people want to use or modify relatively small parts, I want them to be free to do so without having to also reproduce the entirety of all the invariant sections too.

Web server authors, database server authors, and programming language authors do their best - but, with any kind of programming at all, it's terribly easy to make mistakes, and new security holes are discovered all the time.

Those security holes are generally plugged in updated versions of the software.

However, one problem with Astroblahhh GLMP-GTK is that it uses old versions of software. It uses PHP** 5.2.17 because, as far as I know, no more recent version of PHP works with the latest version of PHP-GTK** - 2.0.1 - and Astroblahhh GLMP-GTK uses MariaDB** 5.3.12 for the silly reason that I found struggling with learning how to compile a later version of MariaDB with CMake** to be too much trouble.

Also, Astroblahhh GLMP-GTK assumes you're going to just use the Hiawatha** web server that's installed in your Puppy Linux** - and that is most likely not the most recent version of Hiawatha.

In the configuration files I included for Hiawatha and MariaDB, I attempted to make it so by default, Hiawatha and MariaDB are hopefully local only and thus will hopefully block all outside access from random people on the internet - but, I don't even know how to properly test that (I can't even figure out how to browse my own web server from another computer on my own network), and I'm worried that I might've accidentally done it wrong, so, please be careful.

The safest thing to do (and what I recommend) would be to avoid running Hiawatha and MariaDB while you're connected to the internet.

Security holes can be extremely severe, like this PHP security hole. And I assume Astroblahhh GLMP-GTK's PHP 5.2.17 is probably vulnerable to that, even though I wasn't able to figure out how to replicate the exploits described in that page. (I'm still quite far from being an expert on Linux, security, or computers in general.) And there are quite likely many other security holes.

I definitely don't recommend taking the risk of running possibly misconfigured old versions of Hiawatha and MariaDB while connected to the internet, but if you do, please be extremely careful.

If there's ever any important security-related news related to Astroblahhh GLMP-GTK, I'll point it out on the Astroblahhh GLMP-GTK home page:

If you're only interested in the PHP-GTK desktop software part of Astroblahhh GLMP-GTK and don't need or want PHP for the web, nor a database server such as MariaDB, you should probably download the Astroblahhh PH-GTK package instead. With that, you can still do database stuff with the serverless SQLite**.

Astroblahhh GLMP-GTK is a package of software for people interested in:

• Developing, or locally running, web software in PHP** (especially), or Perl** or Python**. (Perl and Python aren't included in this package, but, there are lines about them in the web server configuration file to make it easier to get started with them, and I included some helpful tips and example scripts.)

• Developing or running desktop software with a native Linux graphical user interface (GUI) using PHP-GTK**. (Linux is also known as GNU/Linux**.)

• Database programming for either local web software or desktop software, using either MariaDB** ("a drop-in replacement for MySQL"**), or SQLite**, which is tremendously smaller and serverless.

If you need to actually run a web server or database server on your computer to serve stuff to random folks on the internet, I recommend NOT using Astroblahhh GLMP-GTK - see the above warning. Sorry, I don't know what would be best for that.

I recommend Astroblahhh GLMP-GTK for local software development only, and it's safest to be disconnected from the internet while you're running your web server or database server.

If you don't need to develop web software, nor database software for a database that runs on a server (like MariaDB or MySQL), and are only interested in PHP-GTK desktop software (and possibly using a serverless SQLite database), you'd be better off downloading Astroblahhh PH-GTK instead of Astroblahhh GLMP-GTK.

Astroblahhh GLMP-GTK doesn't contain the newest PHP available, but instead PHP 5.2.17, because that's the newest one I know of that works with the newest version of PHP-GTK, 2.0.1.

Astroblahhh GLMP-GTK also doesn't contain the latest database software. It has SQLite 2.8.17 and SQLite 3.3.7 because those are what came with PHP 5.2.17, and it has MariaDB 5.3.12 simply because that was the latest version that didn't make me learn how to use CMake** to compile it.

Astroblahhh GLMP-GTK doesn't contain any web server software, and assumes you already have the Hiawatha** web server installed, because most Puppy Linuxes** do, including all of the Puppies I've seen Astroblahhh GLMP-GTK work in.

This release of Astroblahhh GLMP-GTK was created in Lucid Puppy 5.2.8 version 004. It works in that and other Ubuntu**-based Puppy Linuxes, and somehow also works in the Slackware**-based Slacko Puppy 5.3.3. It didn't work in everything else I tried so far.

Astroblahhh GLMP-GTK can be installed either with an .sfs file, or a .pet file. (If you don't know what those are, see What is a .pet file?** and What is an .sfs file?** in the file Some Puppy Linux Basics**.)

.pet and .sfs files in general both have their advantages and disadvantages - see Why use a .pet file rather than an .sfs file, or vice versa?**

I almost named this package something long and cumbersome:

php-cli-and-cgi-5.2.17-with-php-gtk-2.0.1-and-mariadb-5.3.12-and-freetype-2.4.11--made-in-lucid-puppy-5.2.8-4--package-version-1.0-i686

Then I saw in the PHP License that I couldn't use PHP**'s name in the name of my project without permission. So, I had to change the name, which I guess was probably for the best.

So, this package became:

The GTK part of the name comes from the fact that Astroblahhh GLMP-GTK contains PHP-GTK** 2.0.1.

That makes it so you can create PHP software with native Linux graphical user interfaces (GUIs) using GTK+. ** It's similar to WinBinder in Windows**. (The WinBinder FAQ explains how PHP-GTK and WinBinder compare to each other.)

The GLMP part of the name Astroblahhh GLMP-GTK is basically inspired by GLAMP, which is a name for any AMP software bundle for Linux (also known as GNU/Linux**).

This page from GNU.org says it would be fairer to call LAMP packages GLAMP, so, I decided to name this package GLMP-GTK instead of just LMP-GTK.

One example of an AMP you might have already heard of is XAMPP**.

GLAMP typically stands for:

• GNU/Linux** - the free, open source operating system (OS) you're probably using now, which comes in tons of different varieties, also referred to as distros. It's usually called just Linux, but the Linux part of it is the kernel, while GNU** is lots of important stuff other than the kernel.

• Apache** - Popular web server software.

• MySQL** - Popular database software.

• PHP**/Perl**/Python** (any or all of the preceding) - Three well-known, popular programming languages.

Astroblahhh GLMP-GTK doesn't include any web server software such as Apache or Hiawatha**, hence it's called GLMP, rather than GLAMP or GLHMP.

Astroblahhh GLMP-GTK is intended to work with the Hiawatha web server, and it is assumed you're installing Astroblahhh GLMP-GTK in a Puppy Linux** which already has Hiawatha, but all Astroblahhh GLMP-GTK contains is a short custom Hiawatha config file.

Also, instead of the MySQL database software, Astroblahhh GLMP-GTK has MariaDB**, known as "a drop-in replacement for MySQL". (More comments on MariaDB are below.)

Astroblahhh GLMP-GTK also contains the tremendously smaller and serverless database software SQLite**, but, that's usually included in any LAMP which has PHP, since PHP generally has SQLite built in by default.

In Astroblahhh GLMP-GTK's case, the P in GLMP primarily stands for PHP**, but Perl** and Python** also deserve honorable mentions, since the Hiawatha config file included in Astroblahhh GLMP-GTK lets you easily also use Perl and Python scripts on your web server.

See: Using PHP, Perl, or Python on your Local Web Server

Astroblahhh GLMP-GTK only really assists in using PHP for GTK** stuff, since I haven't yet figured out how to use Perl and Python to make GTK software. (Haven't tried very hard yet...)

The Astroblahhh part of the name Astroblahhh GLMP-GTK is simply from the name of my personal website - Astroblahhh.Com.

Alas, Astroblahhh GLMP-GTK didn't work in most variants of Puppy Linux** I tried.

But, with effort, it could be made to work. See: Making Astroblahhh GLMP-GTK Work in Other Puppies

Happily and to my surprise, this package did work in one Puppy which wasn't Ubuntu Linux**-based: Slacko Puppy 5.3.3, which is based on Slackware Linux**.

It worked best in Ubuntu Linux-based Puppies like Lucid, Precise, Three-Headed Dog, and Puppy Studio 3.3.

However, I only tested it briefly in most everything, except Lucid Puppy 5.2.8 version 004, the Puppy I built Astroblahhh GLMP-GTK in - so, my apologies if you run into any problems.

Astroblahhh GLMP-GTK assumes your Puppy has the Hiawatha** web server already installed (it's not included in the Astroblahhh GLMP-GTK package, though it could have been), and Perl** (which is used by some of the installation scripts).

This package worked in:

This package didn't work in:

Lucid Puppy 5.2.8 version 004 - what I use nearly all the time. It's also the Puppy in which I compiled everything that needed to be compiled. However, I'm not sure if Lucid Puppy 5.2.8 version 004 is available to download anymore, since only version 005 is here: http://distro.ibiblio.org/puppylinux/puppy-5.2.8/ Lucid Puppy 5.2.8 version 005 - Briefly tested and it seemed to work fine. Three-Headed Dog 5.2.8 version 005 - Same. Precise Puppy 5.4.3 - Same. Puppy Studio 3.3 - Same. Lucid 525 Retro-2.6.30.5 - Same. Lucid Puppy 5.2 - Same. Slacko Puppy 5.3.3 - The only problem I noticed was, shell commands such as rox "/root/Path with Spaces In It/" cause an error message to appear instead of causing the Rox-Filer file manager to open the path. Escaping the spaces doesn't help (whether or not the path is put in quotes). But, other than that, the rest seems to work fine. You just won't be able to use some of the convenient folder opener scripts, and after installation, you'll have to open the "Readme and Extras" folder manually. It's located in: /root/

Wary Puppy 5.3 - After install, typing php at a shell prompt results in many repetitions of of this error: "php: /usr/lib/libxm12.so.2: no version information available (required by php)" And 1 line saying: php: /lib/libc.so.6: version `GLIBC_2.11' not found (required by php) And 1 line saying: php: /lib/libc.so.6: version `GLIBC_2.11' not found (required by /usr/local/lib/libfreetype.so.6) Racy Puppy 5.2.2 - Same. RacyPy 4** - Same. Quirky Puppy 1.4.2 - Similar. Typing php at a shell prompt results in the same last two error lines that were shown in the previous 3. Fatdog64-611 - Typing php at a shell prompt results in sh: /usr/local/bin/php: No such file or directory, even though the php file is definitely at that location after the Astroblahhh GLMP-GTK .pet installs. Also, Fatdog64-611 doesn't have the Hiawatha web server installed, which Astroblahhh GLMP-GTK assumes is installed. And, Fatdog64-611 doesn't have Perl installed, which is used by some of the installation scripts. Lighthouse64-5.11 F - Typing php at a shell prompt results in: php: error while loading shared libraries: libreadline.so.6: wrong ELF class: ELFCLASS64 Lighthouse64 also doesn't have the Hiawatha web server installed, which Astroblahhh GLMP-GTK assumes is installed. BrunoPup 2.0 - a 4.31 Puppy Linux. The Astroblahhh GLMP-GTK .pet installs but PHP complains about not having "libreadline.so.6". (As of 19:30 02/17/2013, the BrunoPup ISO doesn't seem to be available for download.) Dpup 485 - Same as what happened with BrunoPup 2.0. ArchPup 13.2.1 - I couldn't figure out how to make it open and install a .pet.

The .pet** of Astroblahhh GLMP-GTK installs about 106 MB of files, so if you install the .pet, you'll need at least that much "personal storage space" RAM (if running Puppy in RAM), or else that much space in your Pupsave file or hard disk.

If you use the .sfs** of Astroblahhh GLMP-GTK, somehow that doesn't use up "personal storage space" RAM, but, just watch out for the various nuisances .sfs files have. (See the .sfs**-related sections of the file Some Puppy Linux Basics**.)

For Astroblahhh GLMP-GTK to work in any Puppies it currently doesn't work in, probably all the compiled software in Astroblahhh GLMP-GTK will need to be recompiled using each program's source code (see Package Contents section for links) and the DevX file** for the Puppy in which you want to use Astroblahhh GLMP-GTK.

I'm unlikely to create Astroblahhh GLMP-GTK packages for other Puppies myself, unless asked, or optionally paid to do it, or unless I begin using a Puppy Linux variant that is incompatible with this Astroblahhh GLMP-GTK package.

But, you can always build your own GLMP-GTK package, with whatever customizations you like.

See: How to Compile Software from Source Code**

Doing that might be a lot less troublesome and difficult than you might think. Before making Astroblahhh GLMP-GTK, I thought it might be difficult and maybe impossible for me to figure out how to do it - but, luckily, it turned out to be surprisingly easy to make. The most difficult, time-consuming thing was writing all this documentation.

But, if you'd still rather not build your own GLMP-GTK package, you could ask me to do it, either for free, or for donations, or for upfront payment: Request Free/Libre/Open Source Software or Documentation, or Ask Programming Questions

It should be possible to make variants of Astroblahhh GLMP-GTK that would work in Linuxes other than Puppy, and I might someday make a Windows** version or perhaps even a Mac** version, since I like the idea of being able to write PHP-GTK software that will easily run on multiple platforms.

But, those will likely be more difficult to make than other Puppy versions of Astroblahhh GLMP-GTK.

The compiled software in Astroblahhh GLMP-GTK includes: PHP, PHP-GTK, MariaDB, FreeType. And SQLite, but that comes with PHP, so you won't have to compile that separately.

If your Puppy doesn't have Perl**, you could either install Perl (it's probably contained in your Puppy's DevX file**) just before running your custom GLMP-GTK installer, or replace the handful of Perl installation scripts with ones written in Bash** or some other scripting language your Puppy has.

And if your Puppy doesn't have the Hiawatha** web server, you can try downloading and compiling it. I haven't tried doing that myself, so, I don't know how easy or difficult that will be.

If you do compile your own GLMP-GTK package, it would probably be best to call it something other than "Astroblahhh" (even if it includes scripts or other things I wrote myself and included in Astroblahhh GLMP-GTK), since "Astroblahhh" in the name might imply I made your package (since my personal website is Astroblahhh.Com), and I'd prefer not to take the credit (or blame) for other people's work.

Puppy usually doesn't come with Python** built-in, and the Perl** that's built into Puppy is usually a stripped-down version rather than a full version. You can often get by just fine with the stripped-down version of Perl, but not always.

For how to install Python and a full version of Perl, see:

There are some PHP**, Perl**, and Python** example scripts in the Example Scripts/For Web Server/ folder inside this "Readme and Extras" folder.

/root/Web-Server/

(Alternatively, you can put symlinks** in that folder pointing at script files or folders in other locations.)

To go there, you can click the file icon on your Puppy desktop, which will open the /root/ folder, which should contain the Web-Server folder.

The script's name is going to be used in the script's URL on your web server, so, you should give it a name containing valid URI characters.

Also, it's best to avoid characters you need to escape, since escaped characters aren't very readable.

Depending on the kind of script it is, end its filename with either .php, .pl or .py.

You can also end the filename with .phpg (the filename extension for PHP-GTK scripts) or .phpb (the filename extension I arbitrarily chose for PHP console scripts), since I put a couple lines in the Hiawatha** web server configuration file at /etc/hiawatha/hiawatha.conf to allow that.

To be run by the Hiawatha** web server:

• PHP** scripts need World (or Other):Read permissions, or else Group:Read permissions. (It sometimes varies, and I haven't figured out why.)

• Perl** scripts need World (or Other):Read and World (or Other):Exec permissions. (Unfortunately, Rox-Filer** run actions don't work with executable files, so, you won't be able to just double-click your Perl scripts to run them on your web server.)

• Python** scripts need World (or Other):Read permissions.

If the required permissions aren't set, then, Hiawatha will give you a 403 Forbidden error when you try to run those scripts.

See: How to Set File Permissions**

The example scripts already have their permissions set properly.

Before turning on the Hiawatha** web server and (if desired) the MariaDB database server, you should disconnect from the internet. (See the above warning for why.)

Once you're disconnected, you can turn on Hiawatha and/or MariaDB using one (or more) of the scripts in the Web Server Control Scripts/ folder.

Once you've placed a script in the /root/Web-Server/ folder, disconnected from the internet and turned on your web server, you can run your script by visiting:

http://localhost/insert-name-of-your-script-file-here.php or .pl or .py or .phpg or .phpb

Once you've placed the example scripts in the /root/Web-Server/ folder, disconnected from the internet and turned on your web server, you can run the example scripts by visiting these links:

PHP

• http://localhost/random-number-from-0-to-1000.php

• http://localhost/phpinfo.php

• http://localhost/your-ip-address.php

  
  

• http://localhost/Dual PHP-GTK and Web Server Script Which Does Different Things Depending on Which php.ini File is Being Used/dual-php-gtk-and-web-server-script-which-does-different-things-depending-on-which-php-ini-file-is-being-used.phpg

• http://localhost/dual-php-console-and-web-server-script-which-does-different-things-depending-on-which-php-ini-file-is-being-used.phpb

  These last two aren't limited to only being run on your web server. To run one of them without running it on your web server, either:

  • Right-click it, go to the menu item titled File '[name of script]', and from the submenu, choose either Run in terminal window or Run without terminal window.

  Or:

  • You can just double-click on it (or single-click, depending on your Rox-Filer settings**) - assuming you have an appropriate Rox-Filer** run action set.

    If you need to, you can set a Rox-Filer run action using the run action selector script for .phpg or .phpb files in the Rox-Filer Run Actions/ folder in this "Readme and Extras" folder.

    If you choose "If Possible, Run in Browser at Localhost, or else Run with Terminal Window" or "If Possible, Run in Browser at Localhost, or else Run without Terminal Window", then, double-clicking on your script will either run it on your web server (if your web server is on and the script you clicked was somewhere inside /root/Web-Server/), or run it as a PHP-GTK or PHP console script (if your web server is off or your .phpg or .phpb script isn't somewhere inside /root/Web-Server/).

Perl

• http://localhost/random-number-from-0-to-1000.pl

Python

• http://localhost/random-number-from-0-to-1000.py

I've included some barebones template scripts for all 3 languages, both with and without comments, in Example Scripts/For Web Server/Templates with Comments/ and Example Scripts/For Web Server/Templates/.

They contain the minimum lines you need to create a working PHP**, Perl**, or Python** web server script, and you can use them as a base for your own scripts.

Astroblahhh GLMP-GTK installs PHP 5.2.17, which is not the newest version of PHP**, but instead the newest version I know of which works with the newest version of PHP-GTK**, 2.0.1.

So, you won't need to install anything extra to be able to use PHP on your Puppy's probably built-in Hiawatha** web server.

For links you can click to actually run the example scripts, see: Links to Example Scripts

The following links will let you see the source code of the PHP example scripts included in the Example Scripts/For Web Server/ folder and Example Scripts/For Both Web Server and PHP-GTK/ folder and Example Scripts/For Both Web Server and Console/ inside this "Readme and Extras" folder.

Once you follow the links, tell your web browser to show you the source. (In the Firefox web browser, you can do that by right-clicking the page and choosing View Page Source.

• phpinfo.php

• random-number-from-0-to-1000.php

• your-ip-address.php

• dual-php-gtk-and-web-server-script-which-does-different-things-depending-on-which-php-ini-file-is-being-used.phpg

• dual-php-console-and-web-server-script-which-does-different-things-depending-on-which-php-ini-file-is-being-used.phpb

See Using PHP, Perl, or Python on your Local Web Server for how to run them.

Go to Example Scripts/For Web Server/Templates with Comments/ or Example Scripts/For Web Server/Templates/ for a very short, basic, practically needless template script you can optionally use as a base for your own PHP scripts. With Comments - Without Comments

It already has the file permissions required for PHP scripts to work in the Hiawatha** web server - Group:Read and World:Read - and it conveniently contains the minimum line that a PHP web server script needs at the top:

<?php

The template script omits the ?> closing tag, since it's not required at the end of a script, and there are apparently many sensible reasons to NOT use it at the end of a script.

(The ?> closing tag is useful in the middle of a PHP script, however. It lets you write whatever text or HTML or JavaScript or whatever other non-PHP output you want in the middle of your PHP script, which can be more readable and convenient than using PHP echo statements to print code in other languages, and then having to escape quotes and so on.)

If you want to make your own PHP script from scratch rather than using the template, just put <?php at the top, and make sure your file has at least Group:Read or World (or Other):Read permissions. (Which one you need can vary, and I haven't figured out why.)

And follow the instructions at: Using PHP, Perl, or Python on your Local Web Server

A stripped-down version of Perl** is already installed by default in most Puppies I've tried, and all of the Puppies I've seen Astroblahhh GLMP-GTK work in. You can often get by just fine with the stripped-down version, but not always.

If you want or need a full version of Perl rather than a stripped-down version, it's probably in the DevX development tools .sfs file** for your particular kind of Puppy.

In many Puppies, Perl already works by default in the Hiawatha** web server without installing Astroblahhh GLMP-GTK, as you can see if you try the PPLOG personal blog software that's included with those Puppies. PPLOG might be found in the Personal menu.

For links you can click to actually run the example scripts, see: Links to Example Scripts

Click the below link to see the source code of the Perl example script included in the Example Scripts/For Web Server/ folder inside this "Readme and Extras" folder.

• random-number-from-0-to-1000.pl

See Using PHP, Perl, or Python on your Local Web Server for how to run it.

Go to Example Scripts/For Web Server/Templates with Comments/ or Example Scripts/For Web Server/Templates/ for a barebones template script you can optionally use as a base for your own Perl scripts. With Comments - Without Comments

It conveniently contains the minimum lines that a Perl web server script needs to work. Also, it already has the file permissions required for Perl scripts to work in the Hiawatha web server - World (or Other):Read and World (or Other):Exec.

You can easily just make a copy of the template.pl file and add to it, rather than making Perl scripts for your web server utterly from scratch.

Or, to make a Perl script for your web server from scratch, here are the important details:

• The first line of the script must be the following, and there can be no empty lines or other whitespace before it:

  #! /usr/bin/perl

  If that's not there, or if it has any whitespace before it, the Hiawatha web server will always give you a 500 Internal Server Error when attempting to run your script.

  
  

• The script might display only partial output unless you use the following line as the first thing the script prints. So, add this:

  print "Content-type:text/html\r\n\r\n";

  
  

• The script needs the file permissions required for Perl scripts to work in the Hiawatha web server - World (or Other):Read and World (or Other):Exec.

• You should also follow the instructions at: Using PHP, Perl, or Python on your Local Web Server

Python** can be easily installed using a .pet** file, or (probably) the DevX development tools .sfs file** for your particular kind of Puppy.

I know for sure Python is in the lupu_devx_528-4.sfs DevX for Lucid Puppy 5.2.8 version 004 (and presumably also for version 005) available from: http://distro.ibiblio.org/puppylinux/puppy-5.2.8/

I usually don't use the DevX, though - so in Lucid Puppy 5.2.8 version 004, I usually use the Python .pet from here: http://distro.ibiblio.org/puppylinux/pet-packages-lucid/Python-2.6-Lucid.pet

If you use something other than Lucid Puppy, you might have to use a different .pet for your Puppy Linux variant. You could check your Puppy Package Manager (shell command: ppm) or look around in: http://distro.ibiblio.org/puppylinux/

And, of course, in Linux, there's always the option of compiling (or attempting to compile) from source code and possibly having to fiddle and struggle for a long time with getting that to work. But, fortunately, you actually can get lucky and run into no significant problems doing that - and, it enables you to customize things much more than you can with most precompiled packages. And you might learn a lot in the process.

For links you can click to actually run the example scripts, see: Links to Example Scripts

Click the below link to see the source code of the Python example script included in the Example Scripts/For Web Server/ folder inside this "Readme and Extras" folder.

• random-number-from-0-to-1000.py

See Using PHP, Perl, or Python on your Local Web Server for how to run it.

Go to Example Scripts/For Web Server/Templates with Comments/ or Example Scripts/For Web Server/Templates/ for a barebones template script you can optionally use as a base for your own Python scripts. With Comments - Without Comments

It conveniently contains the minimum lines that a Python web server script needs to work. Also, it already has the file permissions required for Python scripts to work in the Hiawatha web server - World (or Other):Read.

You can easily just make a copy of the template.py file and add to it, rather than making Python scripts for your web server utterly from scratch.

Or, to make a Python script for your web server from scratch, here are the important details:

• The following line must be the first line of output - any output before it likely won't display properly:

  print "Content-type:text/html\r\n\r\n"

• The script needs the file permissions required for Perl scripts to work in the Hiawatha web server - World (or Other):Read.

• You should also follow the instructions at: Using PHP, Perl, or Python on your Local Web Server

PHP** is a well-known, very popular programming language.

This is deliberately not the newest version, because later versions I tried didn't work with the latest PHP-GTK** version, 2.0.1.

I compiled PHP with these options:

./configure --with-readline --enable-zip --enable-mbstring --enable-fastcgi --with-mysql=/usr/local --with-mysqli=/usr/local/bin/mysql_config --with-pdo-mysql=/usr/local --enable-ftp --with-gd --with-ttf --enable-gd-native-ttf --with-freetype-dir=/usr/local/lib/

The above options are explained in greater detail below.

PHP-CLI (the command line version of PHP) has an interactive shell, similar to the interactive shell in Python** or J**.

You can start the PHP interactive shell by using the little Bash** script in the Interactive Shells/ folder in the same folder as this Readme, or by typing php -c /etc -a in a console.

• The -a option is the one that starts the interactive shell.

• The -c option tells PHP what folder to look in (in the above case, the /etc/ folder) for the php.ini configuration file you want PHP to use.

By default, both PHP-CLI and PHP-CGI use the php.ini file at /usr/local/lib/php.ini, but PHP-CLI needs to use the php.ini at /etc/php.ini if you want to use PHP-GTK. The PHP-GTK extension is disabled in /usr/local/lib/php.ini because it causes errors with PHP-CGI.

The Rox-Filer** run action selector scripts in the Rox-Filer Run Actions/ folder in this "Readme and Extras" folder should take care of the php.ini issues automatically.

PHP-GTK** is similar to WinBinder in Windows**. (The WinBinder FAQ explains how PHP-GTK and WinBinder compare to each other.)

In the Example Scripts/PHP-GTK folder (in the same folder as this Readme), there are some PHP-GTK example scripts which hopefully can be run just by clicking on them. (They should work that way, if you said yes to the installation of the .phpg MIME type and left its default Rox-Filer** run action alone.)

SQLite** is serverless database software. I didn't include standalone versions of SQLite, just the two versions PHP 5.2.17 comes with by default:

• SQLite 3.3.7 - Used by PHP's PDO_SQLITE features. PHP's SQLite3 class isn't available in PHP 5.2.17 - it's only in PHP 5.3.0 and beyond.

• SQLite 2.8.17 - Used by PHP's SQLite functions.

SQLite can be used with both PHP-CGI (the CGI or web version of PHP) and PHP-CLI (the command line version of PHP).

Last time I used MariaDB** extensively was in 2011, but it did seem to live up to its description in the above quote. I was able to use the exact same Astroblahhh Desktop MySQL databases in both Lucid Puppy 5.2 with MariaDB and Windows XP with MySQL, and as far as I know, this created no problems at all, and worked great.

In 2011, in Lucid Puppy 5.2, I used an LHMP .pet (though I think it was a different LHMP .pet than the one in the previous link, which has a broken download link, as of March 2, 2013) containing MariaDB and the Hiawatha** web server, and in Windows XP, I used XAMPP** 1.6.3a, with MySQL and the Apache** web server.

I prefer MariaDB rather than MySQL because of alarming stories like these:

• Nov. 29, 2012: Monty on broken MySQL promises: Oracle's going to fork it up

• August 18th, 2012: Oracle Makes More Moves To Kill Open Source MySQL

I used this older version of MariaDB rather than version 5.5.29 because I was too impatient to sit there and struggle to figure out how to use CMake** to compile it.

So, I picked the next most modern-sounding version available - 5.3.12 - and was relieved to find I could compile it with the usual commands...

./configure
make
make install

...and make clean before recompiling.

The /root/.my.cnf MariaDB configuration file I included is a slightly modified version of the .my.cnf file displayed here:

https://kb.askmonty.org/en/running-mariadb-from-the-source-directory/

I put in the appropriate settings for data= and language= and added skip-networking which I hope makes it impossible for anyone other than your local computer to connect to the database server. (But see the warning above for why you should probably only run your database server and web server while disconnected from the internet.)

However, it's a very short config file, and I'm not sure it's the best configuration - I don't even know how to judge that. (But, it seems to work fine with my WordsPlatz blog software.)

MariaDB installed a bunch of example .cnf files at:

/usr/local/share/mysql/

Perhaps they would be better in some ways/for some purposes.

I think FreeType** makes it so the GD** image-making extension in PHP** can add text to images. That's the only reason I included it.

I compiled PHP with these ./configure options:

./configure --with-readline --enable-zip --enable-mbstring --enable-fastcgi --with-mysql=/usr/local --with-mysqli=/usr/local/bin/mysql_config --with-pdo-mysql=/usr/local --enable-ftp --with-gd --with-ttf --enable-gd-native-ttf --with-freetype-dir=/usr/local/lib/

Explanations of the above options:

• --with-readline

  Makes it so PHP-CLI's interactive shell works.

  http://www.php.net/manual/en/refs.utilspec.cmdline.php

  
  

• --enable-zip

  Adds the Zip extension to PHP, enabling you to work with .zip files.

  http://php.net/manual/en/book.zip.php

  
  

• --enable-mbstring

  Adds the mbstring extension to PHP. I'm not sure what it does exactly, I only added it because phpMyAdmin** 3.3.5 wanted it.

  http://php.net/manual/en/mbstring.installation.php

  
  

• --enable-fastcgi

  Makes it so PHP-CGI is FastCGI instead of not FastCGI.

  http://php.net/manual/en/configure.about.php

  This is an old version of PHP, so I don't believe it has the FastCGI Process Manager.

  http://php.net/manual/en/install.fpm.php

  
  

• --with-mysql=/usr/local

  Makes it so PHP has functions like mysql_connect(), which are now deprecated in favor of mysqli functions or PDO::mysql.

  http://www.php.net/manual/en/ref.mysql.php

  
  

• --with-mysqli=/usr/local/bin/mysql_config

  Makes it so PHP has functions like mysqli_connect(). This configure option had the odd quirk of requiring a different path than the path I was able to use with --with-mysql and --with-pdo-mysql.

  http://www.php.net/manual/en/book.mysqli.php

  
  

• --with-pdo-mysql=/usr/local

  "PDO_MYSQL is a driver that implements the PHP Data Objects (PDO) interface to enable access from PHP to MySQL 3.x, 4.x and 5.x databases."

  http://www.php.net/manual/en/ref.pdo-mysql.php

  
  

• --enable-ftp

  Included because some of the things I plan on coding might involve downloading files via FTP.

  http://php.net/manual/en/book.ftp.php

  
  

• --with-gd

  Adds the GD** image processing extension to PHP.

  http://php.net/manual/en/book.image.php

  
  

• --with-ttf

  An option related to the GD** image processing extension.

  "GD: Include FreeType 1.x support"

  Quoted from text produced by the command ./configure --help

  
  

• --enable-gd-native-ttf

  An option related to the GD** image processing extension.

  "GD: Set the path to FreeType 2 install prefix"

  Quoted from text produced by the command ./configure --help

  
  

• --with-freetype-dir=/usr/local/lib/

  I guess PHP had to be told where to find FreeType 2.4.11.

• max_execution_time = 300 [5 minutes] instead of 30

  
  

• The line which said error_reporting = E_ALL now says:

  error_reporting = E_ALL ;^ E_NOTICE

  Just delete the ; to uncomment the ^ E_NOTICE part.

  
  

• Both display_errors and display_startup_errors are On instead of Off. Also, log_errors_max_len = 0 because a comment above that says:

  "Set maximum length of log_errors. In error_log information about the source is added. The default is 1024 and 0 allows to not apply any maximum length at all."

  
  

• extension_dir = "/usr/local/lib/php/extensions/" instead of extension_dir = "./"

  
  

• In the "Dynamic Extensions" section of PHP-CGI's php.ini at /usr/local/lib/php.ini:

  ;extension=php_gtk2.so
;extension=sweph.so

  In the "Dynamic Extensions" section of PHP-CLI's php.ini at /etc/php.ini:

  extension=php_gtk2.so
;extension=sweph.so

  
  sweph.so is the Swiss Ephemeris PHP extension, PHP-SWEPH. It's not included in the Astroblahhh GLMP-GTK package, since it's mainly of interest to people who are interested in astrology, but you can download it separately at:

  http://astroblahhh.com/software/glmp-gtk-or-ph-gtk/extensions/eryss-and-swiss-ephemeris

The documentation I wrote and many of the scripts I wrote that are included in this package are under the GNU General Public License v3.0. There are also short, simple scripts by me which are in the public domain.

Other things in this package that aren't by me are under other licenses - except SQLite**, which is actually public domain.

See also: Icon Info

• PHP** is under the PHP License**.

  PHP license info: http://php.net/license/index.php

  
  

• MariaDB** is under the GNU General Public License, version 2**.

  MariaDB license info: https://kb.askmonty.org/en/mariadb-license/

  
  

• FreeType** is under either the FreeType License** or the GNU General Public License, version 2**.

  FreeType license info: http://freetype.org/license.html

  
  

• According to the PHP-GTK article at Wikipedia, PHP-GTK is under the GNU Lesser General Public License**.

  Maybe I didn't look hard enough, but, I couldn't find any mention of a license in PHP-GTK's documentation, nor in the PHP-GTK 2.0.1 tar.gz file. So, I don't know if Wikipedia is right.

See the section titled Beware of RAM** in the file Some Puppy Linux Basics** for a longer explanation of why this might be a problem.

Basically, anything in a RAM disk is at great risk of being irretrievably lost, so, anything you want to keep, you should store in a (so-called) permanent storage medium, like a hard disk.

So, you might want to move the "maria_dbs" folder and "Readme and Extras" folder to a location in a permanent storage medium.

With the "maria_dbs" folder, you'll also need to put a symlink** at /root/maria_dbs pointing to the new location of the "maria_dbs" folder, so MariaDB** will be able to access your databases at their new location.

To make that symlink:

• Go to the location on a permanent storage medium where you moved the "maria_dbs" folder to.

• Right-click on the "maria_dbs" folder, go to the Dir 'maria_dbs' menu item, and choose Link... from the submenu. (Be careful, "Link..." is just above "Delete".)

• In the little Symlink window that appeared, uncheck the Relative link checkbox.

• Then, in the text field above the checkbox, put this path:

  /root/maria_dbs

• Then, click the Symlink button.

Alternatively, you could put only certain databases in a permanent storage medium, and put symlinks inside /root/maria_dbs/ pointing at those databases' folders' locations on the permanent storage medium.

But, it's safest to move the whole "maria_dbs" folder to a permanent storage medium and symlink to that, so you won't accidentally create a database in the RAM disk and forget to save that database before shutting down.

No worries if you accidentally lose the "Readme and Extras" folder. You can always download a fresh copy from:

The Readme and Extra folder also contains a fresh copy of the "maria_dbs" folder, consisting only of default databases.

And, of course, copies of both folders exist inside the Astroblahhh GLMP-GTK .pet** or .sfs**.

Activism | Astrology | Astronomy | Blog | Credit Card Boycott | Firefox Add-Ons | GNU/Linux | How To Guides | Ideas | Languages | Music | Opinions | Pictures | Second Life | Self-Help | Software | Windows

About This Site | Contact Apollia | Disclaimer | Updates

Eryss.Com - Non24.Com

Eryss.Com Forum - Non24.Com Forum

Donations | Services (none available currently)

Request Free/Libre/Open Source Software or Documentation, or Ask Programming Questions (but only if you're very patient)

Or, Donate In Second Life

GitHub