Foswiki system requirements

Perl

• Perl 5.30.3 or higher
• A minimum of perl 5.26.3 is recommended
• Best would be 5.32.0 or higher.
• Please make sure that you are using an up-to-date perl version for security reasons.

perlbrew

See: https://foswiki.org/Support/HowToUseFoswikiWithLocalPerlInstallation

5.16.3 - OK

[<user>@<location> ~]$ perlbrew install perl-5.16.3

5.26.3, 5.28.2/3, 5.32.1, 5.33.7 - NOT OK, 1 test failed

Installing /home/<user>/perl5/perlbrew/build/perl-5.33.7/perl-5.33.7 into ~/perl5/perlbrew/perls/perl-5.33.7

This could take a while. You can run the following command on another shell to track the status:

tail -f ~/perl5/perlbrew/build.perl-5.33.7.log

Installation process failed. To spot any issues, check

/home/<user>/perl5/perlbrew/build.perl-5.33.7.log

If some perl tests failed and you still want to install this distribution anyway,
do:

(cd /home/<user>/perl5/perlbrew/build/perl-5.33.7/perl-5.33.7; make install)

You might also want to try upgrading patchperl before trying again:

perlbrew install-patchperl

Generally, if you need to install a perl distribution known to have minor test
failures, do one of these commands to avoid seeing this message:

perlbrew --notest install perl-5.33.7
perlbrew --force install perl-5.33.7

build.perl-5.33.7.log

# Failed test 'setlogsock() should return true: '''
# at t/syslog.t line 225.
# Looks like you failed 1 test of 181.
../cpan/Sys-Syslog/t/syslog.t ….....................................
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/181 subtests
(less 110 skipped subtests: 70 okay)

installation with --notest

[<user>@<location> ~]$ perlbrew --notest install perl-5.33.7
Installing /home/<user>/perl5/perlbrew/build/perl-5.33.7/perl-5.33.7 into ~/perl5/perlbrew/perls/perl-5.33.7

This could take a while. You can run the following command on another shell to track the status:

tail -f ~/perl5/perlbrew/build.perl-5.33.7.log

perl-5.33.7 is successfully installed.

Perlbrew - other parameters

Once you have multiple perl versions installed, you can list and switch between them:

[web00929@amsterdam ~]$ perlbrew list
perl-5.33.7
* perl-5.16.3
[web00929@amsterdam ~]$ perlbrew switch perl-5.33.7

You can clean the build and dists directory's and so save a lot of precious disk space by issuing the following command:

perlbrew clean

PerlDependencyReport => cpanm

All required modules can now be installed by issuing cpanm [module]:

cpanm Crypt::PasswdMD5
cpanm File::Copy::Recursive
cpanm JSON
cpanm Locale::Language
cpanm Text::Unidecode
cpanm Date::Manip
cpanm Locale::Maketext::Lexicon
cpanm Email::MIME
cpanm Locale::Msgfmt
cpanm LWP
cpanm LWP::Protocol::https
cpanm Algorithm::Diff
cpanm Email::Address
cpanm LWP
cpanm LWP::UserAgent
cpanm CHI
cpanm Archive::Zip
cpanm DBI
cpanm DBD::SQLite

After the installation of a cpan module using cpanm, you can empty the .cpanm directory - this can quickly grow! Or you wait 7 days and it cleans itself: https://serverfault.com/questions/426081/can-i-safely-delete-the-cpanm-work-directory...

.cpanm	size	date	expected date of auto deletion
sources	23.56 MB	2021-03-07	2021-03-14
work	395.18 MB	2021-03-08	2021-03-15

No, no, you have to issue the --auto-cleanup option:

cpanm --auto-cleanup 5 *

.cpanm	size	date
sources	23.55 MB	2021-03-07
work	1.09 MB	2021-03-17

@INC

Can't locate ….pm in @INC (you may need to install the DBI module) (@INC contains: ~)

• /home/<user>/domains/<domain.ext>/public_html/wiki/lib
• ../bin
• /home/<user>/perl5/perlbrew/perls/perl-5.33.7/lib/site_perl/5.33.7/x86_64-linux
• /home/<user>/perl5/perlbrew/perls/perl-5.33.7/lib/site_perl/5.33.7
• /home/<user>/perl5/perlbrew/perls/perl-5.33.7/lib/5.33.7/x86_64-linux
• /home/<user>/perl5/perlbrew/perls/perl-5.33.7/lib/5.33.7
• /home/<user>/domains/<domain.ext>/public_html/wiki/lib/CPAN/lib

FastCGI

• cpanm FCGI

External programs

• GNU diff 2.7 or higher,
• fgrep
• egrep (not required on Windows)

Web server

• Apache - Apache sample configs are provided
  or
• Nginx
  or
• Lighttpd
• For information on other servers, see Foswiki:Support.InstallingOnSpecificPlatforms.

… and much more
Still going strong after all those … deletes.