Free host software for linux

ccHost is a Web-based infrastructure that may be used to host and allow for commenting, remixing, and distribution globally.

The more installations of ccHost and its variations, the more content there will be available for enjoyment and artistic re-use in a sane and legal setting.

ccHost is what is used for the infamous Creative Commons CC Mixter project which supports legal media sharing and remixing.

LSF::Hosts is a Perl module to retrieve information about LSF hosts.

SYNOPSIS

use LSF::Hosts;
use LSF::Hosts RaiseError => 0, PrintError => 1, PrintOutput => 0;
($hinfo) = LSF::Hosts->new( [HOST_NAME] );
@hosts = LSF::Hosts->new();

LSF::Hosts is a wrapper arround the LSF bhosts command used to obtain information about lsf hosts. The hash keys of the object are LSF bhosts header values. See the bhosts man page for more information.

CONSTRUCTOR

new( [ [HOST_NAME] ] );

With a valid hostname, creates a new LSF::Hosts object. Without a hostname returns a list of LSF::Hosts objects for all the hosts in the system. Takes no arguments (jet).

nss-myhostname is a GNU libc NSS module that statically translates the local host name to the IP address 127.0.0.2 (which is on the loopback device) and vice versa.

This is useful to make sure that the local host name is always resolvable. Some programs (such as sudo) require this functionality.

Especially on embedded systems it may not be desirable to modify /etc/hosts to match the current host name.

It is a good idea to put this module as last resort in /etc/nsswitch.conf, to make sure that other name service take precedence.

Hosting Backup provides a set of scripts for backing up your hosted Web sites.
Hosting Backup is a set if PHP command line scripts that provides an easy way to backup hosted Web sites to your local computer. It works with sites hosted on Linux servers with MySQL databases using FTP.
HostingBackup uses lftp (http://lftp.yar.ru/) to download all the files from your remote server.
HostingBackup uses rc4 encryption, so you do not need to have PHP compiled with mcrypt.
HostingBackup is tested on Linux local computer with PHP 4.3.x and lftp 3.0.x.
The remote component will manage some operations like optimization and dump of MySQL databases.
The local component will manage the execution of backups and other utilities like the generation of crypted passwords and the automatic installation of the remote component.
To allow an easy way to backup all hosted MySQL databases we store the main password for the account directly on the remote server, crypted with rc4.
When we call the dump script we pass the decrypt key.
To catch the login data an hacker should read the crypted password written on the server and intercept the key on the net.
Enhancements:
- Add: "--comments=false" to mysqldump
- Add: "set FOREIGN_KEY_CHECKS=0;" to mysqldump
- Add: "--add-drop-table" to mysqldump

Object::Meta::Plugin::Host are hosts plugins that work like Object::Meta::Plugin. Can serve as a plugin if subclassed, or contains a plugin which can help it to plug.

SYNOPSIS

# if you want working examples, read basic.t in the distribution
# i dont know what kind of a synopsis would be useful for this.

my $host = new Object::Meta::Plugin::Host;

eval { $host->method() }; # should die

$host->plug($plugin); # $plugin defines method
$host->plug($another); # $another defines method and another

# $another supplied the following, since it was plugged in later
$host->method();
$host->another($argument);

$host->unplug($another);

$host->method(); # now $plugins method is used

Object::Meta::Plugin::Host is an implementation of a plugin host, as described in Object::Meta::Plugin.

The host is not just simply a merged hash. It is designed to allow various plugins to provide similar capabilities - methods with conflicting namespace. Conflicting namespaces can coexist, and take precedence over one another. A possible scenario is to have various plugins for an image processor, which all define the method "process". They are all installed, ordered as the effect should be taken out, and finally atop them all a plugin which wraps them into a pipeline is set.

When a plugins method is entered it receives, instead of the host object, a context object, particular to itself. It allows it access to its host, its sibling plugins, and so forth explicitly, while implicitly wrapping around the host, and emulating it with reordered priority - the current plugin is first in the list.

Such a model enables a dumb plugin to work quite happily with others, even those which may take its role. The only rule it needs to keep is that it accesses its data structures using $self-self>, and not $self, because $self is the context object.
A more complex plugin, aware that it may not be peerless, could explicitly ask for the default (host defined) methods it calls, instead of its own. It can request to call a method on the plugin which succeeds it or precedes it in a certain methods stack.

Additionally, by gaining access to the host object a plugin could implement a pipeline of calls quite easily, as described above. All it must do is call $self-host->stack($method)> and iterate that omitting itself.

The interface aims to be simple enough to be flexible, trying for the minimum it needs to define to be useful, and creating workarounds for the limitations this minimum imposes.

The implementation is by no means optimized. I doubt its fast, but I dont really care. Its supposed to create a nice framework for a large application, which needs to be modular.

EtherEye is a web-based network host checking system written in PHP and standards compliant HTML.
You simply provide it with a list of IP addresses or domain names via the configuration interface and it will ping them on request and output the results as HTML.
You can also access the results via RSS feed for easier monitoring or to integrate into a website.
Installation:
To configure EtherEye, simply point your browser at the config.php file included with EtherEye. If it doesnt work or you get an error, PHP probably isnt properly configured on your server.
Language
Select your desired language here. This setting affects the language of the configuration interface as well as the results interface. Please read the README for instructions on how to translate EtherEye into your language if your language is not available.
Does the server run Windows?
If the server runs Windows, select "Yes", otherwise leave it on "No". If you set this to Yes, a few options will be filled in automatically, so you dont need to worry about them.
Which theme would you like to use?
Pretty self-explanatory really. The EtherEye interface will look different depending on which theme you select. Please see the README for instructions on how to write EtherEye themes.
Automatic refresh
If you enable automatic refreshing, the results page will be automatically re-loaded as frequently as specified by the option further down the page.
Ping command line option to specify the number of requests to send
If you selected the Windows server option you dont need to worry about this - it has been auto-filled. If not, the default should be OK for people running Linux. People running other UNIXes will need to check their ping man page.
Ping command line option to specify the ping timeout
The default value should be OK for everyone running Windows or Linux. Again, people running other UNIXes will need to check their ping man page.
Ping time-out
This value tells ping how long to wait for a response to ping requests. This value is in seconds if your server runs Linux or UNIX and milliseconds if your server runs Windows. The default value used by ping under Linux and UNIX is 3 seconds, Windows ping is 4000 milliseconds (4 seconds).
The lower this value, the less time EtherEye has to wait for ping to give up waiting for a response from a down machine, which makes the results get displayed quicker. However, bear in mind that if a machine is up but takes longer to respond than the time allowed by this value, EtherEye will report it as down! One second is probably a reasonable value for this setting.
Site name
This is simply a name used in a few places in the interface. It can be anything you want.
How often to refresh
If you enabled automatic refreshing above, you need to set this to how often you would like the results page to be automatically refreshed in seconds. The default, 300 seconds, is 5 minutes. If you didnt enable automatic refreshing above, you dont need to worry about this option.
How long to cache results for?
Each time EtherEye pings the hosts it saves the state of each host in the hosts file. This option determines how long these saved states are used for before EtherEye re-pings the hosts. If EtherEye has cached results available which have not expired, it will display them immediately without re-checking the hosts. This can be useful if you access EtherEye a lot (many times a minute) and dont need EtherEye to check the hosts that frequently. Most people will probably want to set this to 0 to disable caching completely.
Number of machines you want to watch
You need to specify here how many machines you want EtherEye to monitor. This is used to decide how many input boxes to give you on the next page.
If all is well, click on the button to save the options youve entered and move to the next page of the installation. If EtherEye is giving an error and not displaying the button, you need to check the permissions on the directory EtherEye is running from - you need to enable write access for all users (you can change it back later).
Entering the hosts
On this page, you need to enter the hosts you wish to monitor. Enter the IP address or domain name in the first box of each line, then a name for the machine in the second box (this can be anything you want) and finally select the machine type - this wont affect how EtherEye works, it is simply used to select an icon to display for the machine in the results.
Finishing the configuration
Once you have completed the installation, you may wish to change the permissions on the directory EtherEye is installed into so that every user cannot write to it (you cant be too careful).
Next, you may wish to change the permissions on the hosts-list.xml and ethereye-conf.xml files to ensure they are not writable (you dont want other people playing with your configuration). However, note that if you make hosts-list.xml non-writable, caching will not work (if you enabled it) and no error will be given to tell you this.
You may also wish to delete config.php for proper security, but then you wont be able to reconfigure EtherEye using the interface later.
Using EtherEye
Once you have EtherEye configured, you can check the machines you have configured EtherEye with by accessing the index.php file. If you use an RSS aggregator, you may wish to add rss.php to it to keep track of your network status. You could also integrate your EtherEye scan results into your website using the rss.php feed.
Enhancements:
- This release incorporates fixes for users receiving outdated results due to caching in the browser or server and for some configuration values not being remembered when reconfiguring using the configuration interface.

Easy Hosting Control Panel is designed for hosting multiple domains on a single machine. It uses LAMP (Linux/Apache/MySQL/PHP).
Easy Hosting Control Panel aims to be easy to install and use, simple, and functional.
Enhancements:
- The installer was improved.
- Known bugs were fixed.

App::installguide::hosted is a Perl module to instructions on installing the App::Context framework in a web-hosting (non-root) environment.

These are instructions on installing the App::Context framework in a web-hosting (non-root) environment.

ASSUMPTIONS

* You get command line access but not root.
* You have access to a MySQL database engine (and permissions to create at least 3 databases)

SET UP THE CPAN SHELL

Installing software from CPAN into a non-system area requires a little setup.

* Find CPAN/Config.pm and make a local copy of it to MyConfig.pm
* Modify MyConfig.pm to use local directories

The first thing to do is to find CPAN/Config.pm.

> which perl
/usr/bin/perl

Since perl is installed in /usr/bin, the perl libraries are most likely stored in /usr/lib/perl5.

> find /usr/lib/perl5 -name Config.pm -print
/usr/lib/perl5/site_perl/5.8.7/x86_64-linux/Template/Config.pm
/usr/lib/perl5/site_perl/5.8.7/Apache/Admin/Config.pm
/usr/lib/perl5/5.8.5/CPAN/Config.pm
/usr/lib/perl5/5.8.5/Net/Config.pm
/usr/lib/perl5/5.8.7/x86_64-linux/Encode/Config.pm
/usr/lib/perl5/5.8.7/x86_64-linux/Config.pm
/usr/lib/perl5/5.8.7/CPAN/Config.pm
/usr/lib/perl5/5.8.7/Net/Config.pm

Now make a copy of CPAN::Config.

mkdir ~/.cpan
mkdir ~/.cpan/CPAN
cp /usr/lib/perl5/5.8.7/CPAN/Config.pm ~/.cpan/CPAN/MyConfig.pm

Now edit it.

vi ~/.cpan/CPAN/MyConfig.pm

There might be lines like the following.

build_dir => q[/root/.cpan/build],
cpan_home => q[/root/.cpan],
histfile => q[/root/.cpan/histfile],
keep_source_where => q[/root/.cpan/sources],
makepl_arg => q[],
make_install_arg => q[UNINST=1],
mbuildpl_arg => q[],

Change them to something like the following.

build_dir => q[/home/username/.cpan/build],
cpan_home => q[/home/username/.cpan],
histfile => q[/home/username/.cpan/histfile],
keep_source_where => q[/home/username/.cpan/sources],
makepl_arg => q[PREFIX=/home/username],
make_install_arg => q[],
mbuildpl_arg => q[install_base=/home/username],

Then fire up the CPAN shell and install something. Then verify that it installed.

# perl -MCPAN -e shell
cpan> install App::Options
cpan> exit
# find ~/lib -name Options.pm -print
/home/username/lib/perl5/site_perl/5.8.7/App/Options.pm

Yay. Success. We used the CPAN shell to install modules into our private perl library directory.