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.
For documentation on Episerver Foundation, see the documentation repository. Note that this is till work-in-progress.
You can request a demo of the project by one of our Episerver experts on Get a demo.
- System requirements
- Pre-installation set-up
- Installation
- Troubleshooting
- Modular set-up
- Contributing
- Visual Studio 2017 or higher - Download
- SQL Server Express or Developer or SQL Azure Server - Download (If using SQL Azure download sqlcmd)
- Microsoft SQL Server Management Studio - Download
- Nodejs - Download
- Microsoft Internet Information Server (IIS) - Download
See also the general Episerver system requirements on Episerver World.
- In Microsoft SQL Server Management Studio, connect to your SQL server:
- Right-click on your server and select Properties.
- Under Security, make sure that SQL Server and Windows Authentication mode is selected:
How to find the IIS settings depends on the system where you are running IIS.
- Go to your IIS settings. If you are running IIS locally on your Windows machine, you find these under Control Panel > Programs > Programs and Features > Turn Windows features on or off.
- 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.
- Download the ZIP file from the Foundation project's master branch on GitHub and extract the files, or clone the project from GitHub to a local folder using the command prompt and the git command
git clone https://github.com/episerver/Foundation foundation(the foundation 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:
- Go to the appSettings.config and appSettings.debug.config:
- Search the config for "https://ChangeMe.com/"
- Update Perform, Insight, Profile Store urls and keys
- Go to the Web.config:
- Search the config for "changeme"
- Update Social appId and secret key
- Update the Find index to your own credentials
- Right-click on the batch file called setup.cmd and select Run as administrator:
- The installation starts and you are asked to provide the following parameters:
| Parameter | Description |
|---|---|
| Application name: | The name of the application. Note: The application name should contain only letters and numbers as it used as the prefix to create the website and database components. |
| Public domain name for foundation: | Domain name for the application, for example, foundation.com. |
| Public domain name for Commerce Manager: | Domain name for the Commerce Manager application, for example, commerce.foundation.com. |
| License path: | If you have a license file, add the path to it. Otherwise you can add that later. |
| SQL server name: | SQL server instance name. Add the same server name as the one you connected to in the Pre-installation set-up steps for the SQL server. If using Azure SQL, provide the full dns name for your Azure SQL instance |
| sqlcmd command: | SQL command to execute, by default -S . -E . This can generally be left as is. If using Azure SQL, pass username and password as -U <user> -P <password> |
- 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 two application pools
• Create two websites
• Update host file
• Copy License file
• Update commerce manager url for access from cms
• create connectionstrings files
• Start the site to finish setup in browser
-
When the installation is finished, a Mosey start page is opened in your browser. If not, enter the URL http://yourdomainname/ manually.
-
If the setup page throws an error, open your host file, found under C:\Windows\System32\drivers\etc, and add the two domain names you entered during the installation. Reload the page in your browser.
-
Log in with user: admin@example.com and password: store to access the Episerver user interface.
Note: A resetup.cmd file has been created in your project which you can run to re-install the database.
- Developer licenses for evaluation purposes can be obtained from the Episerver License Center. Place the License.config file in your webroot.
- Check that you have full access rights to the project folder.
- Check that you meet the system requirements.
- Check your SQL authentication settings as described in SQL Server.
- Check your IIS settings so that they match those specified in IIS settings.
- Check the log files:
Build\Logs\Build.log Build\Logs\Database.log Build\Logs\IIS.log
- Check that the site is actually running by navigating to http://yourdomainname/episerver/cms.
The Foundation project is set up to include all Episerver’s main products. Each product is set up as a project of its own inside the main project, so if you don’t want all products, you can simply remove their projects.
As this is an open-source project, we encourage you to contribute to the source code and the documentation. See the Contribution guidelines for this project.