This page describes how to set up Communifire on your own server(s). Communifire is a web application that operates using IIS and SQL Server. This guide includes the following sections:
We recommend backing up your Windows Server, Communifire folder, and SQL database daily. We do not have any recommendations for disaster recovery.
Communifire is a modern web application that uses HTML5 and CSS3 for enhanced usability on desktop computers as well as a vast array of mobile devices. The following browsers are supported:
EXEC [Dyve_System_InstantiateCommunity] @ApplicationName = 'Your_app_name_goes_here',
@ApplicationURL = 'http://www.your-application-url.com',
@VirtualDirectory = '', @DefaultEmailAddress = 'email@example.com',
@SMTPServer = '', @SMTPUsername = '', @SMTPPassword = '', @SMTPPort = 25,
@AdminUserName = 'admin', @AdminPassword = 'admin'
NOTE: If you are installing CF as a virtual directory, add a forward slash ("/") before the virtual directory name. For example, for "http://your-site.com/community", set @ApplicationURL='http://your-site.com' and the virtual directory name as follows: @VirtualDirectory = "/community".
Create site folder: Create E:\Websites\Yourwebsite.com\ and copy files in the \software\ folder of the .zip file to your new directory.
Database connection string: Update /CFConnectionStrings.config so that it reflects the credentials of your Communifire database.SQL user authentication:
<add name="CommunifireConnectionString" connectionString="Initial Catalog=[DATABASENAME];Server=[IPADDRESS];User ID=[USERID];Password=[PASSWORD]"/>
Windows AD user authentication:
connectionString="Data Source=[IPADDRESS];Initial Catalog=[DATABASENAME];Integrated Security=SSPI;" providerName="System.Data.SqlClient" />
Optional: SQL Connection String in Registry
Create Site in IIS: Create a new site in IIS and add proper bindings to your new site. http and https bindings are required.
App Pool Settings: Click IIS > Application Pools > Right-click application pool > Advanced Settings. Make sure the settings are as follows:
<system.net> <defaultProxy enabled="true"> <proxy bypassonlocal="true" proxyaddress="http://your proxy address here:8080/" /> </defaultProxy> </system.net>
<system.web> <httpRuntime maxRequestLength="2000000" executionTimeout="100000" /> </system.web>
<security> <requestFiltering> <requestLimits maxAllowedContentLength="2000000000" /> </requestFiltering></security>
With the above maxAllowedContentLength, users can upload files that are 2,000,000,000 bytes in size (approx. 2 GB). This setting will work right away without restarting IIS services.
Alternatively, if the above methods do not work, you can fix the issue by running the "appcmd" command:
C:\Windows\System32\inetsrv\appcmd set config -section:requestFiltering -requestLimits.maxAllowedContentLength:100000000
%windir%\system32\inetsrv\appcmd set config "Default Web Site/<your app>" -section:requestFiltering -requestLimits.maxAllowedContentLength:10000000
You can find detailed information regarding specific installation instructions on the following pages:
Axero typically publishes one major version a year. Service versions, which contain bug fixes, are published monthly and sometimes weekly. Learn how to upgrade to the latest major version or service version of Communifire.
is requesting access to a wiki that you have locked: http://my.axerosolutions.com/spaces/5/communifire-documentation/wiki/view/329/on-premise-installation