Deploy On Premises

This topic shows you how to deploy a Weavy instance to an on-prem Windows server (for production use we recommend Windows Server 2016 or later, but for development and testing scenarios a Windows 10 workstation will also work fine).

This topic shows one way to deploy Weavy to an on-prem server. Depending on your requirements, environment, and security considerations you may need to do things differently.

Hardware recommendations

The highly diverse scope of potential deployments makes it hard to state "recommended" hardware requirements that would be generally applicable. But the following configuration is a good starting point. Depending on your specific use case, these values may of course have to be increased to ensure optimal performance.

  • Memory: At least 8 GB RAM, and should be increased as needed to ensure optimal performance.
  • Processor: At least dual core 64-bit processor, 3.0 GHz or faster. Increase core count and/or clock frequency as needed to ensure optimal performance
  • Storage: At least 128GB SSD, and should be increases as needed to ensure optimal performance.

Install and configure IIS

First, we need to install the IIS web server component. If you are familiar with IIS and already have things set up, feel free to jump ahead.

Search for Turn Windows features on or of in your system.

Check Internet Information Services and then make sure at least the items below are installed. Then click OK.

At this point it's recommended that you reboot your system. This way you will be sure that all the required services are started correctly.

Deploy files

Unzip your deployment package and copy the contents of the wwwroot\ folder to C:\inetpub\weavy\

If you don't have a package yet, head over to Getting Started section to download Weavy and create your first package.

For Weavy to work properly the following file and folder permissions need to be configured for the IIS_IUSRS identity. When selecting the identity, make sure you select the local server in the "From this location" field (otherwise local accounts such as IIS_IUSRS will not be selectable). If a folder does not exist, create it.

Path Type Permissons
C:\inetpub\weavy Folder Read
C:\inetpub\weavy\App_Data Folder Modify
C:\inetpub\weavy\css Folder Modify
C:\inetpub\weavy\js Folder Modify

Add Site to IIS

Open the Internet Information Services (IIS) Manager.

Right click Sites and click Add Website...

Enter values for Site name, Physical path and Host name. The physical path should point to the directory where you copied the wwwroot\ folder from the package, e.g. C:\inetpub\weavy\. Click OK.

Click Application Pools and find the application pool for the site you just created. Make sure it uses .NET CLR version 4.0.x and that the Managed pipeline mode is set to Integrated.

Create database

You can download SQL Server Developer Edition and SQL Server Management Studio from Microsoft free of charge.

Open Microsoft SQL Server Management Studio (SSMS) and connect to your database server.

Create an empty database, name it weavy.

Create a database login and map it to a database user. Make sure that the user has the database role db_owner.

Configuration settings

Open the file web.config (located in the C:\inetpub\weavy folder) with a text editor and locate the connection string Weavy.

<add name="Weavy"
connectionString="server=localhost;database=weavy;trusted_connection=true;"
providerName="System.Data.SqlClient" />

Update the connection string with your values. It should look something like this when updated:

<add name="Weavy"
connectionString="server=localhost;database=weavy;uid={your_userid};pwd={your_password};"
providerName="System.Data.SqlClient" />

If you are running Weavy without a HTTPS(SSL) binding, locate the line below in the web.config file:

<appSettings file="settings.config" />

And replace with the following:

<appSettings file="settings.config">
    <add key="weavy.https" value="false" />
</appSettings>

Save your changes to the web.config file.

Open a browser and navigate to the host name you configured for Weavy in the IIS. You should see the Weavy setup screen.