Repository files navigation

Foundation offers a starting point that is intuitive, well-structured and modular allowing developers to select Episerver products as projects to include or exclude from their solution.Including as of now projects for CMS, Commerce, Personalization, Find and Social, with the rest to follow.

• Foundation
• Table of Contents
• - Troubleshooting
• System requirements
• Pre-installation set-up
  • SQL server
  • IIS settings
• Installation
• Troubleshooting
  • The installation fails

• Visual Studio 2017 or higher -Download
• SQL Server Express or Developer or SQL Azure Server -Download (If using SQL Azuredownload sqlcmd)
• Microsoft SQL Server Management Studio -Download
• Nodejs -Download
• Microsoft Internet Information Server (IIS) -Download

See also the generalEpiserver system requirements on Episerver World.

1. In Microsoft SQL Server Management Studio, connect to your SQL server:
2. Right-click on your server and select Properties.
3. UnderSecurity, make sure thatSQL Server and Windows Authentication mode is selected:

How to find the IIS settings depends on the system where you are running IIS.

1. Go to your IIS settings. If you are running IIS locally on your Windows machine, you find these underControl Panel >Programs >Programs and Features >Turn Windows features on or off.
2. Check that the following features have been enabled:

• Under Application Development:
  • ASP .NET
  • NET Extensibility
  • ASP
  • ISAPI Extensions
  • ISAPI Filters
• Common HTTP Features (Installed) node (all are required):
  • Static Content (Installed)
  • Default Document (Installed)
  • Directory Browsing (Installed
  • HTTP Errors (Installed) (Installed)
  • HTTP Redirection
• Under the Performance (Installed) node:
  • Static Content Compression (Installed)
  • Dynamic Content Compression (Installed)
• Under the Security (Installed) node:
  • URL Authorization (Installed)

The installation files on GitHub contain a batch file that will install the Foundation project with all products and set up an empty demo site. After the installation, you can fetch demo content from a remote repository to create a Mosey demo site, a fictitious fashion retail company.

1. Download the ZIP file from the Foundation project'smaster branch on GitHub and extract the files, or clone the project from GitHub to a local folder using the command prompt and the git commandgit clone https://github.com/episerver/Foundation foundation (thefoundation part specifies the folder where to put the files):

Download ZIP file

Or clone project using Git

Note: It is recommended that you store the project in a folder directly under C:, in a folder where your user has full access rights:

2. Right-click on the batch file calledsetup.cmd and selectRun as administrator:

3. The installation starts and you are asked to provide the following parameters:

4. The build process executes a number of steps and logs both to the console and to the log files. The automatic build steps are:

•Set permissions on the folder to everyone full control•Restore NuGet packages•npm install•gulp Saas task•Build solution•Install Databases•Create one application pool•Create one website•Update host file•Copy License file•create connectionstrings file•Start the site to finish setup in browser

5. When the installation is finished, a start page is opened in your browser. If not, enter the URL http://yourdomainname/ manually.

6. If the start page throws an error, open your host file, found underC:\Windows\System32\drivers\etc, and add the one domain name you entered during the installation. Reload the page in your browser.

7. Log in with user:admin@example.com and password:store to access the Episerver user interface.

Note: Aresetup.cmd file has been created in your project which you can run to re-install the database.

8. Developer licenses for evaluation purposes can be obtained from theEpiserver License Center. Place theLicense.config file in your webroot.

• Check that you have full access rights to the project folder.
• Check that you meetthe system requirements.
• Check your SQL authentication settings as described inSQL Server.
• Check your IIS settings so that they match those specified inIIS settings.
• Check the log files:

  Build\Logs\Build.logBuild\Logs\Database.logBuild\Logs\IIS.log