Skip to content

Installing Sriracha

mmooney edited this page Sep 29, 2014 · 5 revisions

Building From Source

Database Considerations

Sriracha can use either a SQL Server or Raven DB database.

If you are going to use Raven DB, you must be running the setup scripts as a user who has permission to create the Raven DB.

If you are going to use SQL Server, you will need to provide a connection string in the settings file below that has DBO access to the target database in order to create the database objects. If the database does not yet exist, the user account in the connection string needs to have access to create the database. In either case, this is the same connection string that will be used by the application.

  • Download the code from GitHub: https://github.com/mmooney/Sriracha.Deploy
  • From a command line, run build.bat
  • Edit .\SampleSettings\LOCAL.js to match your settings. The fields in this file are:
    • Always Change/Verify

      • TargetWebsitePath - Target location for website code
      • WebUserName: The NT user name that the web application pool should run under
      • VirtualDirectorySite: The name of the IIS website that the web application should run under
      • VirtualDirectoryName: The name of the virtual directory (subdirectory) that the web application should run under
      • WebsiteAuthenticationMode: The authentication mode that the web application should use. Possible values are Forms and Windows.
      • ApplicationPoolName: The name of the application for the web application to run under. If it does not exist, it will be created.
      • SiteUrl: The common URL of the web application, to be included in email notifications.
      • EmailConnectionString: Connection information for email communication. Possible fields:
        • Host - SMTP server name
        • Port - SMTP port to use, optional, defaults to 25
        • UserName - SMTP user name, if necessary
        • Password - SMTP password, if necessary
      • EncryptionKey: Unique private key used to encrypt and sensitive values like deployment credentials. We recommend a random GUID for this
      • ServiceStartMode: Indicates what service startup mode the Sriracha service should use. Possible values are: Automatic, Manual, Boot, System, Disabled
      • ServiceUserName: NT user name for the Sriracha service to run under. For built in system accounts, use "NT AUTHORITY\SYSTEM", "NT AUTHORITY\LOCAL SERVICE", "NT AUTHORITY\NETWORK SERVICE"
      • ServiceUserPassword: Password of the NT user account for the Sriracha service to run under. For built in system accounts, leave this blank.
      • ServiceName: Name of the Sriracha service
      • ServiceTargetPath: Target location for Sriracha service code
      • AutoStartService: Indicates whether to automatically start the Sriracha service after the installation
      • TargetCommandLinePath: Target location for the Sriracha command line utility
    • For SQL Server Only

      • ConnectionString: SQL Connection String
      • RepositoryAssemblyName: Set to Sriracha.Deploy.SqlServer.dll
    • For Raven DB Only

      • RavenDBConnectionString: The URL of the Raven DB database to use
      • RepositoryAssemblyName: Set to Sriracha.Deploy.RavenDB
    • Do Not Change

      • SourceWebsitePath: Where the website code will be pulled from (generated by build.bat)
      • ServiceSourcePath: Where the service code will be pulled from (generated by build.bat)
      • ServiceExeName: Just what it sounds like
      • SourceCommandLinePath: Where the command line utility code will be pulled from (generated by built.bat)
      • CommandLineExeName: Just what it sounds like
  • Edit .\SampleSettings\LOCAL.servermaps to match your target server IP addresses.
  • From a command line, run deploy.bat

Other Options

Coming soon

Clone this wiki locally