Applies to Windows Server 1709 and later At //Build2017, Microsoft announced that Windows Subsystem for Linux will be. These instructions walk through running the Windows Subsystem for Linux on Windows Server 1709 and later.

Enable the Windows Subsystem for Linux Enable the 'Windows Subsystem for Linux' optional feature and reboot. • Open PowerShell as Administrator and run: PowerShell Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux • Restart your computer when prompted. Install a Linux distribution • Download the appx for your favorite Linux distribution. Here are links directly to the apps available through the store: • • • You can download the distributions to Windows Server with cmdlet. Here's a sample instruction to download Ubuntu.

Assuming you are deploying Codestriker under the 'Default Web site', right-click this entry on the left hand frame of the window, and select 'New' ->'Virtual Directory' ->'Next'. Check that there is an entry for.pl files, and that the 'Executable Path' entry looks like (substitute the path to your local Perl installation).

Invoke-WebRequest -Uri -OutFile ~/Ubuntu.zip -UseBasicParsing Tip: If the download is taking a long time, turn off the progress bar by setting $ProgressPreference = 'SilentlyContinue' • Unzip the file Expand-Archive ~/Ubuntu.zip ~/Ubuntu Make sure your target directory ( ~/Ubuntu in this example) is on your system drive. Usually this is your C: drive. Example: C: Distros Ubuntu The contents should look like this: • Run the installer, named.exe For example: ubuntu.exe, fedora.exe, etc. Troubleshooting: Installation failed with error 0x8007007e This error occurs when your system doesn't support WSL. Make sure that: • You're running Windows build 16215 or later.. • The Windows Subsystem for Linux optional component is enabled and the computer has restarted.. Sigma As 227 Programmable Thermostat. • Create a UNIX user The first time you install the Windows Subsystem for Linux, you will be prompted to create a UNIX username and password.

This UNIX username and password can be different from, and has no relationship to, your Windows username and password.. • Run distro's preferred update/upgrade. Sudo apt-get update sudo apt-get upgrade You're done! Go use your new Linux environment!

This section deals with deploying Codestriker using Apache, on either a UN*X machine or Win32. Codestriker can run as an ordinary CGI script, which allows it to run under any CGI-complaint webserver. The following configuration details are specific for the Apache webserver (), which is available for download for both UNIX and Window platforms. Apache should be already available for most UNIX distributions. Apache 1.X or 2.X can be used for Win32 systems deploying Codestriker as a CGI script. For Win32 mod_perl installations, Apache 1.X is recommended. Note any Codestriker or Apache configuration changes require the Apache server to be restarted.

For UNIX, a command like the following is required: /etc/init. Chevy Head Porting Templates. d/httpd restart or /etc/init.d/apache restart For Windows, the Apache shell window can be terminated by pressing ^C, and started from the Windows menu. There are also shortcuts from the menu for editing the Apache configuration file.

If you installed Codestriker into /var/www/codestriker/codestriker-X.Y.Z, the configuration you need in your apache.conf file (normally located in either /etc/httpd.conf, /etc/apache.conf or /etc/httpd/conf/httpd.conf) is the following: ScriptAlias /codestriker/ /var/www/codestriker/codestriker-X.Y.Z/cgi-bin/ Alias /codestrikerhtml/ /var/www/codestriker/codestriker-X.Y.Z/html/ AllowOverride None Options ExecCGI Order allow,deny Allow from all SetHandler cgi-script AllowOverride None Allow from all For Windows, the configuration is the same, but filename paths should use '/' rather than ' '. An example configuration could be the following, if Codestriker was installed in c: codestriker codestriker-X.Y.Z. ScriptAlias /codestriker/ 'C:/codestriker/codestriker-X.Y.Z/cgi-bin/' Alias /codestrikerhtml/ 'C:/codestriker/codestriker-X.Y.Z/html/' AllowOverride None Options ExecCGI Order allow,deny Allow from all SetHandler cgi-script AllowOverride None Allow from all. Using mod_perl provides performance benefits for Perl-based web applications. For CGI deployments, as described in the previous section, each HTTP request will create a new Perl interpreter, which needs to initialise, and then parse the Codestriker source code. This may add significant latency for each HTTP request. Using mod_perl, a pool of Perl interpreters which have already parsed the Codestriker source code is maintained, so that whenever an HTTP request is issued, the time spent creating a new Perl interpreter and the parsing of the Codestriker code is removed.

Mod_perl is available for download from. For most UNIX distributions, it is available by default with Apache. For installing mod_perl under Windows, contains installation information. You should be able to install it by typing: C: >ppm PPM>rep add theory PPM>install mod_perl Note mod_perl has known to be a little flaky under Windows.

Make sure you get Codestriker working deployed as a CGI script before trying to use mod_perl. The following shows the configuration settings for an Apache 1.X server with mod_perl enabled, for a Codestriker distribution installed in /var/www/codestriker/codestriker-X.Y.Z. Alias /codestriker/ /var/www/codestriker/codestriker-X.Y.Z/cgi-bin/ Alias /codestrikerhtml/ /var/www/codestriker/codestriker-X.Y.Z/html/ SetHandler perl-script PerlHandler Apache::Registry Options +ExecCGI AllowOverride None Allow from all The settings for Windows are the same, only the pathnames will be different, as per the CGI configuration in the previous section.

For extra security, Codestriker supports Perl taint-mode, so it is advisable to also have the following option in your Apache config: PerlTaintCheck On Note if you are using LXR on the same webserver, this option cannot be used. You'll also need to remove the -T argument from bin/codestriker.pl.base, and re-run install.pl again (see ) if you want to use Codestriker and LXR. Also note there is a strange issue with Perl 5.8 on Win32, the open3() call and taint mode. For Win32 users, don't enable tainted mode. For Apache 2.X, make sure the mod_perl module is loaded when Apache starts.

Near the top of the Apache config file, you should see commands like the following: LoadModule perl_module modules/mod_perl.so PerlModule Apache2 If these commands aren't present, and a Perl startup file is not being used, make sure these are added in. The Codestriker configuration for Apache 2.X is very similar, the only change is the name of the PerlHandler. Alias /codestriker/ /var/www/codestriker/codestriker-X.Y.Z/cgi-bin/ Alias /codestrikerhtml/ /var/www/codestriker/codestriker-X.Y.Z/html/ SetHandler perl-script PerlHandler ModPerl::Registry Options +ExecCGI AllowOverride None Allow from all To enable Perl taint mode checking, using the following option: PerlSwitches -T As mentioned in the previous section, Win32 users should not enable this mode.