Setup / Install

 

1. Create a IIS Web Site (Either on a local server or via a commercial host provider)
Create a virtual IIS web site from folder "/dasblogce" or you can use your IIS root if you understand the requirements. You can also use the script "CreateDasBlogVdir.vbs" to create the site, if you are installing local. 

2. Copy files
Copy all files into your "dasblogce" folder or IIS site root keeping the folder structure intact.

3. Important Pemissions & configuration files: 

* On IIS 5.0 (Windows 2000), the account used to execute web applications (IWAM_xxx) needs read/write permissions to the content, siteconfig, and logs subdirectories. 

* The ASP.NET worker process identity, usually “{machinename}\ASPNET” on IIS5.0 (Windows 2000 and Windows XP) or “NETWORK SERVICE” on IIS 6.0 (Windows Server 2003) also need read/write access to the content, siteconfig, and logs subdirectories. 

* Go to the siteConfig directory in (likely in c:\inetpub\wwwroot\{sitename}) and open the site.config file. In that file, change the settings (quite obvious when you look at them). The most important change is to set the <Root> value to the proper URL for your weblog. 

* Open the siteSecurity.config in the same directory and set up your own account with a proper password.

For more detailed information on setup/install or upgrades see the release readme with the version you download! The most recent readme is  Release Notes 1.8 here on this site.

OK if your not going to read the readme right now, maybe this mini detail from Scott Hansleman's blog will be to your liking!

  • NEW INSTALL
    • If you're a new install, get the Web-Files.zip, unzip it, and assuming you've got IIS and ASP.NET on your system run CreateDasBlogVdir.vbs and you should be set. Be sure to log in admin/admin and look at ALL the configuration options, changing them from the defaults. Also edit sitesecurity.config with the user(s) and passwords you want. Read the Readme anyway.
  • UPGRADES
    • Unzip Web-Files.zip locally.
    • If you're running DasBlog locally, you have the \content folder local. If you're remote, bring your \content folder down to your local machine.
    • Upgrader
      • Referrer spam. Open DaBlogUpgrader.exe.config and add any words or domainnames that you want stripped from your dasBlog comments and referrer XML files. Your content and posts will never be touched.
      • Run DasBlogUpgrader from a command line like this: DasBlogUpgrader "c:\whatever directory\dasblog\whateverweb\content"
        • NOTE: You can run the upgrader even if you've already upgraded. It's a multiple use thing.
        • It will as you all sorts of questions. For the most part, answering yes to all is safe.
      • One of the options just strips all referrals (not trackbacks) out of your XML file. If you're running a site with any reasonable amount of traffic you'll see a nice performance boost if you do this. Omar and I recommend that you just give up on referrals. They are a hassle, they grow to quickly and provide little more than a bloated site.
    • Uploading
      • After running the upgrader, we recommend that you use a merge tool or your eyes to merge the differences between your web.config and the one that ships with Web-Files.zip. BeyondCompare is a nice diff tool. (Or read the readme as we tell you which ones in there!)
      • Upload all the ASCX, ASMX and ASPX files to your site and the entire contents of the newtelligence.DasBlog.Web\bin folder and all subfolders to your site, overwriting ALL remote files.
      • Upload the new \DatePicker folder and the \ftb folder and all subfolders
      • Upload all of \themes (if you like) and all of \smilies and \images.
      • Upload your new merged web.config over your old one
      • Upload your new merged site.config over your old one
      • If you like, add PingServices.xml, NavigatorLinks.xml, blockedips.config and blacklist.txt.
    • While you're there...
      • While you're connected to your remote system, consider cleaning out your \logs folder of .log files and .zip files. If your blog has been up a while, you've likely got schmutz up there, so why not clean up?
    • Troubleshooting
      • 93% of problems with DasBlog are web.config files being wrong or wrong directory permissions. That means, bad XML, wrong assembly namespaces, missing sections, missing HTTP Handlers, or incorrect ACLs, etc. Always compare your web.config with the one that shipped and you'll get back on track. Read the readme.
    •  
    Install/Setup | Install