<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/atom10full.xsl" type="text/xsl" media="screen"?><?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/itemcontent.css" type="text/css" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" xml:lang="en-US">
  <title>entp hoth blog - Home</title>
  <id>tag:hoth.entp.com,2008:mephisto/</id>
  <generator version="0.8.0" uri="http://mephistoblog.com">Mephisto Drax</generator>
  
  <link href="http://hoth.entp.com/" rel="alternate" type="text/html" />
  <updated>2008-07-07T16:20:56Z</updated>
  <feedburner:browserFriendly /><link rel="self" href="http://feeds.feedburner.com/activereload-articles" type="application/atom+xml" /><entry xml:base="http://hoth.entp.com/">
    <author>
      <name>courtenay</name>
    </author>
    <id>tag:hoth.entp.com,2008-07-07:2942</id>
    <published>2008-07-07T16:15:00Z</published>
    <updated>2008-07-07T16:20:56Z</updated>
    <link href="http://hoth.entp.com/2008/7/7/entp-brings-on-rabble-ass-kicking-ensues" rel="alternate" type="text/html" />
    <title>ENTP brings on Rabble, ass-kicking ensues</title>
<content type="html">
            &lt;p&gt;The excellent &lt;a href="http://anarchogeek.com"&gt;Evan Henshaw-Plath&lt;/a&gt;, a longtime friend and cabooser, has &lt;a href="anarchogeek.com/2008/7/6/good-bye-to-the-purple-mothership-leaving-yahoo"&gt;joined &lt;span class="caps"&gt;ENTP&lt;/span&gt;&lt;/a&gt; as our latest Ruby and Rails coder.  Evan worked at famed early rails adopters Odeo, and most recently was instrumental in the Yahoo BrickHouse’s &lt;a href="http://fireeagle.yahoo.net/"&gt;Fire Eagle&lt;/a&gt; geo platform.&lt;/p&gt; 

&lt;p&gt;I know can speak for the team when I say we’re all wetting our pants to work with yet another smart implementer.  He’s already been hacking &lt;span class="caps"&gt;XMPP&lt;/span&gt; into some of our internal apps.&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://hoth.entp.com/">
    <author>
      <name>will</name>
    </author>
    <id>tag:hoth.entp.com,2008-06-25:2925</id>
    <published>2008-06-25T23:42:00Z</published>
    <updated>2008-06-26T03:21:27Z</updated>
    <category term="lighthouse" />
    <link href="http://hoth.entp.com/2008/6/25/where-did-those-custom-selectors-in-lighthouse-go" rel="alternate" type="text/html" />
    <title>Where did those custom selectors in Lighthouse go?</title>
<content type="html">
            &lt;p&gt;As some of you may have noticed, the fancy user selector in &lt;a href="http://www.lighthouseapp.com" title="Lighthouse"&gt;Lighthouse&lt;/a&gt; has recently gone missing! You know the one. It looked a little something like this:&lt;/p&gt;

&lt;p&gt;&lt;img src="http://hoth.entp.com/assets/2008/6/26/selector01.png" alt="Screenshot" /&gt;&lt;/p&gt;

&lt;p&gt;No, the &lt;a href="http://en.wikipedia.org/wiki/Hamburglar" title="Hamburglar"&gt;Hamburglar&lt;/a&gt; did not hop out of your televisions and run off with it.  We've just decided to make take a different direction for the time being. So for now, you'll see something a little more on the simple side of life.&lt;/p&gt;

&lt;p&gt;&lt;img src="http://hoth.entp.com/assets/2008/6/26/selector02.png" alt="Screenshot" /&gt;&lt;/p&gt;

&lt;p&gt;You can quit rubbing your eyes and pinching yourself. It's not a dream. In truth, we've run into a few brick walls with the usability of the assigned user selector.  While we work on developing a user selector widget that can rock some socks off, we feel that the usability of the system controls are more important than some fancy UI fluff.&lt;/p&gt;

&lt;p&gt;So what was so wrong with the previous selector? For starters, the script wasn't going to allow us to order the list in a way which made sense for accounts and projects with a large number of users.  It was forcing us to settle for horizontal ordering, which isn't cool at all.&lt;/p&gt;

&lt;p&gt;Most importantly though, it crippled the use of hotkeys. By taking out that beloved visual selector, you can now use your keyboard the way it was intended.  As accounts and projects grow, those lists are getting long, and now you can use that keyboard to sort through the list or jump straight to a user.&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://hoth.entp.com/">
    <author>
      <name>will</name>
    </author>
    <id>tag:hoth.entp.com,2008-06-24:2909</id>
    <published>2008-06-24T18:57:00Z</published>
    <updated>2008-06-24T19:38:39Z</updated>
    <category term="lighthouse" />
    <link href="http://hoth.entp.com/2008/6/24/lighthouse-member-invites-system-gets-some-love" rel="alternate" type="text/html" />
    <title>Lighthouse member/invites system gets some love</title>
<content type="html">
            &lt;p&gt;Last Wednesday, we took Lighthouse offline to deploy some bug fixes and give it some serious feature love. Our original intention was to blog about the new features the next morning so that users would wake up to something pretty cool, but we got a little sidetracked tweaking some last minute details.  Now we owe our users a blog post, so without further ado...&lt;/p&gt;

&lt;h3&gt;What's new?&lt;/h3&gt;

&lt;h4&gt;Member management ++&lt;/h4&gt;

&lt;p&gt;When you log into your Lighthouse account, you'll notice something different at the top.  Rather than the old &lt;strong&gt;People&lt;/strong&gt; tab, you now have an &lt;strong&gt;Access &amp;amp; Permissions&lt;/strong&gt; tab:&lt;/p&gt;

&lt;p&gt;&lt;img src="http://hoth.entp.com/assets/2008/6/23/screenshot_01.png" alt="Screenshot" /&gt;&lt;/p&gt;

&lt;p&gt;We're especially excited about this.  The member management and invite areas within your Lighthouse account has been revamped from the ground up.&lt;/p&gt;

&lt;p&gt;&lt;img src="http://hoth.entp.com/assets/2008/6/23/screenshot_02.png" alt="Screenshot" /&gt;&lt;/p&gt;

&lt;p&gt;Lighthouse has received a great deal of feedback from our users over the last year. Thanks to your voice, we came up with an entirely new way to handle Access &amp;amp; Permissions for member management and invites. This update will make managing the people who surround your projects a lot easier. &lt;/p&gt;

&lt;p&gt;When you click &lt;strong&gt;Set Permissions&lt;/strong&gt;, the available settings for that member will drop down.&lt;/p&gt;

&lt;p&gt;&lt;img src="http://hoth.entp.com/assets/2008/6/23/screenshot_03.png" alt="Screenshot" /&gt;&lt;/p&gt;

&lt;p&gt;As you can see, I'm currently set to the account administrator. This actually disables the project selectors at the bottom half of the selector options.  If the administrator check is removed, then those fields are opened up and you can easily select which projects that person is a member of.&lt;/p&gt;

&lt;p&gt;We've had a few users ask how deleting or removing members from their accounts works. This is a side of the user interface that isn't quite finished just yet. We decided to release the improvements we'd already built (ship early!).&lt;/p&gt;

&lt;p&gt;The access and permissions list organizes your users in order of their permissions. Members who have account access are at the top, while those who have individual project access will be below the account level members.  &lt;/p&gt;

&lt;p&gt;So what about deleting a user from your account/project? For technical reasons, rather than deleting the user from the account, you remove all their permissions. This will remove the user from your member count, and they will be pushed down to the very bottom of your members list.&lt;/p&gt;

&lt;h4&gt;Meet the totally revamped invite system&lt;/h4&gt;

&lt;p&gt;Lighthouse invites have always been pretty straight forward.  Actually, they've been so straight forward that they sometimes were fumbled in the process.  We took that into account when restructuring the invite system so there wasn't any confusion between the inviter, the invitee, and the Lighthouse account or project(s) in question. &lt;/p&gt;

&lt;p&gt;Now when you click the &lt;strong&gt;Invite someone by email&lt;/strong&gt; tab, you'll see a lot more than just the email address field that the old system had.&lt;/p&gt;

&lt;p&gt;&lt;img src="http://hoth.entp.com/assets/2008/6/23/screenshot_04.png" alt="Screenshot" /&gt;&lt;/p&gt;

&lt;p&gt;The new invite system allows for you to not only invite the user, but set their permissions to your account and/or projects right there. But wait...there's more.&lt;/p&gt;

&lt;p&gt;So you've just sent the invite email out and you're soon to be project member gets the email a few moments later.  When they click that link in their email, they will see a little something like this:&lt;/p&gt;

&lt;p&gt;&lt;img src="http://hoth.entp.com/assets/2008/6/23/screenshot_05.png" alt="Screenshot" /&gt;&lt;/p&gt;

&lt;p&gt;Notice the two options on the left side?  Lighthouse invites now allow you to create a new profile right there on the spot or log into a current profile for which you wish to accept the invitation offer. Also, if you're already logged into Lighthouse when you receive an invite, you'll see a third option.&lt;/p&gt;

&lt;p&gt;&lt;img src="http://hoth.entp.com/assets/2008/6/23/screenshot_06.png" alt="Screenshot" /&gt;&lt;/p&gt;

&lt;p&gt;The third option is to use the invitation for the profile in which you are currently logged into. Pretty cool, huh?&lt;/p&gt;

&lt;p&gt;Overall, we really think the new member management and invite system is going to improve the users experience of Lighthouse right from the start.&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://hoth.entp.com/">
    <author>
      <name>justin</name>
    </author>
    <id>tag:hoth.entp.com,2008-06-20:2859</id>
    <published>2008-06-20T23:43:00Z</published>
    <updated>2008-06-21T08:40:17Z</updated>
    <category term="lighthouse" />
    <link href="http://hoth.entp.com/2008/6/20/lighthouse-downtime-scheduled-saturday-8-pm-pdt" rel="alternate" type="text/html" />
    <title>Lighthouse downtime scheduled for Saturday, 8 p.m. PDT</title>
<content type="html">
            &lt;p&gt;We’ll have a small window of downtime for about one hour on Saturday night in order to push some bug fixes and perform server maintenance to Lighthouse.   Downtime will start on Saturday at 8 p.m. PST (2000 -7 GMT) while our host, &lt;a href="http://www.engineyard.com" title="Engine Yard"&gt;Engine Yard&lt;/a&gt;, performs a Cluster Switch Upgrade.  During that time we’ll be updating Lighthouse.&lt;/p&gt;

&lt;p&gt;We’re hoping that Saturday night/Sunday morning is good time when most sane people will be out doing things that don’t involve ticket tracking, but we would like to apologize in advance for any inconvenience this may cause. The details for the updates are as follows:&lt;/p&gt;

&lt;h3&gt;Cluster Switch Upgrade&lt;/h3&gt;

&lt;p&gt;Engine Yard is upgrading the switches that provide connectivity for our slices starting at 8 p.m. PDT (2000 -7 GMT)&lt;/p&gt;

&lt;h3&gt;Database Maintenance&lt;/h3&gt;

&lt;p&gt;Deployments usually only take a few minutes, but we’ll be taking this opportunity to tweak some of the core database indexes. The site will already be offline while the new switches are being setup.&lt;/p&gt;

&lt;h3&gt;DNS Changes&lt;/h3&gt;

&lt;p&gt;Much our surprise, our DNS nameservers were still at our old Engine Yard cluster.  EY00 happened to be taken down for some server maintenance while we were pushing out the new Access &amp;amp; Permissions updates this week.  This is the last bit of our service that relies on the old slices.  We’re all set up on the new nameservers, but we’ll be making the change live tomorrow night.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;edit&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;June 20, 2008 at 9:28 p.m. – this post was just updated to reflect that the downtime will begin at 8 p.m., not at the originally stated 9 p.m.&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://hoth.entp.com/">
    <author>
      <name>nicole</name>
    </author>
    <id>tag:hoth.entp.com,2008-06-20:2915</id>
    <published>2008-06-20T20:20:00Z</published>
    <updated>2008-06-20T20:58:17Z</updated>
    <link href="http://hoth.entp.com/2008/6/20/git-put" rel="alternate" type="text/html" />
    <title>Git Put</title>
<content type="html">
            &lt;p&gt;I had zero experience using version control before I began working for ENTP, so starting fresh with Git was a breeze. The only problem I found was when I when it came time to git push, I always seemed to push branches I didn't mean to push. Luckily, my pal Trevor showed me how to create an alias for a new command - &lt;b&gt;git put&lt;/b&gt;. This neat trick (using newer versions of git) ensures only the 'current' branch is pushed. &lt;/p&gt;


&lt;p&gt;Paste this into your $HOME/.gitconfig file and never worry about accidentally pushing that p0rn branch again.&lt;/p&gt;

&lt;pre&gt;
&lt;code&gt;
[alias] 
  put = push origin HEAD

&lt;/code&gt;
&lt;/pre&gt;
          </content>  </entry>
  <entry xml:base="http://hoth.entp.com/">
    <author>
      <name>will</name>
    </author>
    <id>tag:hoth.entp.com,2008-06-19:2913</id>
    <published>2008-06-19T03:52:00Z</published>
    <updated>2008-06-19T23:48:49Z</updated>
    <category term="lighthouse" />
    <link href="http://hoth.entp.com/2008/6/19/rough-seas-around-the-lighthouse-this-morning" rel="alternate" type="text/html" />
    <title>Rough seas around the lighthouse this morning</title>
<content type="html">
            &lt;h3&gt;4:47 p.m. PDT&lt;/h3&gt;

&lt;p&gt;Account invite emails are now being processed.  We're still under the hood at the moment, but those which we're cued up should have reached their destination inbox by now.&lt;/p&gt;

&lt;h3&gt;3:52 a.m. PDT&lt;/h3&gt;

&lt;p&gt;We hit a bit of a snag after we brought Lighthouse back online last night.  At the moment, invitations for Lighthouse accounts and projects are not making it out of the system.&lt;/p&gt;

&lt;p&gt;On a positive note, the entire email system is not effected.  Emails sent to Lighthouse are being processed, and email notifications of ticket replies are going through the system as normal.&lt;/p&gt;

&lt;p&gt;We'll keep you updated as we know more.&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://hoth.entp.com/">
    <author>
      <name>will</name>
    </author>
    <id>tag:hoth.entp.com,2008-06-18:2908</id>
    <published>2008-06-18T18:30:00Z</published>
    <updated>2008-06-19T22:31:47Z</updated>
    <category term="lighthouse" />
    <link href="http://hoth.entp.com/2008/6/18/scheduled-lighthouse-downtime-tonight-at-10-p-m" rel="alternate" type="text/html" />
    <title>Scheduled Lighthouse downtime tonight at 10 p.m.</title>
<content type="html">
            &lt;p&gt;We're taking Lighthouse offline for approximately 15-30 minutes at 10 p.m. PST (that would be 2200 -7GMT) today in order to perform some updates to the system.&lt;/p&gt;

&lt;p&gt;There are several updates in store which we will blog about as we bring Lighthouse back online, but there seems to be an odd sense of excitement in the office about one of the minor improvements. It has to do with some wording changes to the inline Lighthouse ticket notifications.&lt;/p&gt;

&lt;p&gt;Currently, when you set a milestone of a ticket to be empty, it reads:&lt;/p&gt;

&lt;pre&gt;&lt;code class="ruby"&gt;→ Milestone set to “&amp;quot; &amp;quot;”&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;That's now going to have a more clear statement, which will read something like:&lt;/p&gt;

&lt;pre&gt;&lt;code class="ruby"&gt;→ Milestone cleared&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Now call me crazy, but I've never seen Rick so excited about a single change in Lighthouse.  Maybe he needs his privileges from the &lt;a href="http://www.drinkviso.com/" title="Viso"&gt;Viso&lt;/a&gt; stocked office fridge taken away? I've heard him use the term "&lt;a href="http://www.urbandictionary.com/define.php?term=snarky" title="snarky"&gt;snarky&lt;/a&gt;" 22 times today, so that has to be grounds for some kind of punishment.&lt;/p&gt;

&lt;p&gt;Minor refinements to Lighthouse such as this improve the users experience and mixed with additional notification improvements to tickets that we have in store for the near future, it just makes Lighthouse better. Of course, there is a little more in store than just some wording changes that we are REALLY excited about! &lt;strong&gt;*CoughNewMembersAndInvitesSystemCough*&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;We'll keep you posted on tonight's update after this short break.  Stay tuned!&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://hoth.entp.com/">
    <author>
      <name>justin</name>
    </author>
    <id>tag:hoth.entp.com,2008-06-17:2903</id>
    <published>2008-06-17T20:33:00Z</published>
    <updated>2008-06-17T22:13:25Z</updated>
    <link href="http://hoth.entp.com/2008/6/17/open-source-loves-lighthouse" rel="alternate" type="text/html" />
    <title>Open Source Loves Lighthouse</title>
<content type="html">
            &lt;p&gt;Since we've rolled out our &lt;a href="http://hoth.entp.com/2008/4/29/free-open-source-projects-now-in-lighthouse"&gt;free Open Source projects&lt;/a&gt; we've had a number of amazing projects come on board.  Check out the projects for yourself:&lt;/p&gt;

&lt;p&gt;&lt;a href="http://sproutcore.com"&gt;&lt;img src="/assets/2008/6/17/sproutcore.png" alt="SproutCore" /&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;SproutCore:&lt;/strong&gt;
Fresh off the press! Created by &lt;a href="http://sproutit.com"&gt;Sproutit&lt;/a&gt; with major contributions from &lt;a href="http://apple.com"&gt;Apple&lt;/a&gt;, SproutCore is a Cocoa-inspired, MVC-based JavaScript framework. &lt;/p&gt;

&lt;p&gt;&lt;a href="http://mootools.net"&gt;&lt;img src="/assets/2008/6/17/mootools.png" alt="MooTools" /&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;mootools:&lt;/strong&gt;
A compact, modular, object-oriented JavaScript framework.  We used mootools' FX package on &lt;a href="http://warehouseapp.com"&gt;Warehouse&lt;/a&gt;, it's a fantastic framework and we're glad to have them on board.&lt;/p&gt;

&lt;p&gt;&lt;a href="http://prototypejs.org"&gt;&lt;img src="/assets/2008/6/17/prototype.png" alt="Prototype" /&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prototype:&lt;/strong&gt;
Our JavaScript framework of choice. We use Prototype almost universally on our projects, including &lt;a href="http://lighthouseapp.com"&gt;Lighthouse&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="http://rubyonrails.org"&gt;&lt;img src="/assets/2008/6/17/rails.png" alt="Rails" /&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;RubyOnRails:&lt;/strong&gt; 
The immensely popular web framework that Lighthouse is built on along with a host of other very popular 
applications including &lt;a href="http://twitter.com"&gt;Twitter&lt;/a&gt;, &lt;a href="http://penny-arcade.com"&gt;Penny Arcade&lt;/a&gt; and &lt;a href="http://basecamphq.com"&gt;BaseCamp&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="http://merbivore.com"&gt;&lt;img src="/assets/2008/6/17/merb.png" alt="Merb" /&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Merb:&lt;/strong&gt;
An up and coming web framework built on Ruby, created and supported by our awesome hosting provider &lt;a href="http://engineyard.com"&gt;EngineYard&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="http://chyrp.net"&gt;&lt;img src="/assets/2008/6/17/chyrp.png" alt="Chyrp" /&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Chyrp:&lt;/strong&gt;
A clean and simple PHP blogging engine with a pimpin' theme and module engine.&lt;/p&gt;

&lt;p&gt;&lt;a href="http://rubini.us"&gt;&lt;img src="/assets/2008/6/17/rubinius.png" alt="Rubinius" /&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Rubinius:&lt;/strong&gt;
A virtual machine for running Ruby programs and a Ruby core library.  Rubinius is also supported by Engineyard.&lt;/p&gt;

&lt;p&gt;&lt;a href="http://rspec.info"&gt;&lt;img src="/assets/2008/6/17/rspec.png" alt="RSpec" /&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;RSpec:&lt;/strong&gt;
A Behaviour Driven Development framework for Ruby&lt;/p&gt;

&lt;p&gt;Thanks to all those projects who've joined us here at &lt;a href="http://lighthouseapp.com"&gt;Lighthouse&lt;/a&gt;, especially the Rubinius, Merb and Rspec guys.  They were on Lighthouse long before our official open source support, and have given us a lot of good feedback and criticism.  We're looking forward to expanding on our Open Source functionality and doing what we can to support free and open projects!&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://hoth.entp.com/">
    <author>
      <name>justin</name>
    </author>
    <id>tag:hoth.entp.com,2008-06-04:2895</id>
    <published>2008-06-04T21:50:00Z</published>
    <updated>2008-06-05T16:07:42Z</updated>
    <link href="http://hoth.entp.com/2008/6/4/lighthouse-spam-issues" rel="alternate" type="text/html" />
    <title>Lighthouse Spam Issues</title>
<content type="html">
            &lt;h3&gt;9:01 AM PST (the next day)&lt;/h3&gt;

&lt;p&gt;I deployed some code late last night that should make the spam handling more tolerant (hello, http timeouts!).  I also changed the default behavior for failed API calls to leave the ticket in the current state, rather than marking it spam.  Please let us know if there's something we can do to resolve any spam fires, or if you're still seeing issues.&lt;/p&gt;

&lt;p&gt;We've gotten some requests over the last month to allow projects to disable spam tracking.  We'll cautiously provide this, but I'm thinking some of you don't remember the dark spam-filled early days of Lighthouse.  We have a &lt;a href="http://skitch.com/technoweenie/pykc/activereload-court3nay-s-profile"&gt;ridiculous tar pit system&lt;/a&gt; that I hope is keeping a lot of the riff raff out.&lt;/p&gt;

&lt;h3&gt;6:57 PM PST&lt;/h3&gt;

&lt;p&gt;I recently heard from Defensio.  They are in the process of restoring their service, in the mean time we'll be working on a fix on our end to ensure we'll be able to handle this scenario in the future.&lt;/p&gt;

&lt;h3&gt;2:58 PST&lt;/h3&gt;

&lt;p&gt;It looks as if an Amazon EC2 is the cause of the problem.  Defensio is twittering their status that you can &lt;a href="http://twitter.com/defensio_status"&gt;follow here&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;2:52 PM PST&lt;/h3&gt;

&lt;p&gt;Just a quick post to let everyone know we started experiencing high levels of false positives for spam.  It appears our filter Defensio is down at the moment.  We're getting in touch with them and I'll update this post as soon as I know something further.&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://hoth.entp.com/">
    <author>
      <name>courtenay</name>
    </author>
    <id>tag:hoth.entp.com,2008-05-21:2888</id>
    <published>2008-05-21T02:51:00Z</published>
    <updated>2008-05-21T02:53:25Z</updated>
    <link href="http://hoth.entp.com/2008/5/21/exciting-developments-in-lighthouse" rel="alternate" type="text/html" />
    <title>Exciting developments in Lighthouse</title>
<content type="html">
            &lt;p&gt;&lt;img src="http://img.skitch.com/20080521-f5g179qtei2fnyd1sy426mw2tj.png" /&gt;&lt;/p&gt;


	&lt;p&gt;From our Campfire room.  Read into this what you will. :)&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://hoth.entp.com/">
    <author>
      <name>rick</name>
    </author>
    <id>tag:hoth.entp.com,2008-05-05:2005</id>
    <published>2008-05-05T23:09:00Z</published>
    <updated>2008-05-14T05:11:42Z</updated>
    <link href="http://hoth.entp.com/2008/5/5/more-on-our-partnership-with-engineyard" rel="alternate" type="text/html" />
    <title>More on our partnership with Engineyard</title>
<content type="html">
            &lt;p&gt;I completely missed the actual publishing of &lt;a href="http://engineyard.com"&gt;Engine Yard’s&lt;/a&gt; latest press release announcing &lt;a href="http://www.engineyard.com/2008/4/29/github-and-lighthouse-tap-private-cluster-from-engine-yard"&gt;Lighthouse and Github on a new private cluster&lt;/a&gt;.  I just wanted to take this chance to thank Engine Yard for all the support they have given us over the past year.  With just the two man team in ActiveReload bootstrapping the application from their own pockets, there’s no way we would have had the time to do our client work, write Lighthouse, and set up a scalable clustered infrastructure too.  Their knowledgeable staff has helped keep the database tuned and speedy, migrated us to the faster &lt;a href="http://code.macournoyer.com/thin/"&gt;Thin&lt;/a&gt; web server, and gave us a much larger caching server to keep everything snappy.&lt;/p&gt;


	&lt;p&gt;I also noticed that &lt;a href="http://newrelic.com/press-release-20080501.html"&gt;New Relic finally emerged from stealth mode&lt;/a&gt;.  We’ve been using their monitoring system for several months now and have been very pleased.  I’ll be posting more on that later.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Disclaimer:&lt;/strong&gt;  &lt;em&gt;Naturally, our opinions may be tainted a bit by the donated hosting provided by Engineyard.&lt;/em&gt;&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://hoth.entp.com/">
    <author>
      <name>justin</name>
    </author>
    <id>tag:hoth.entp.com,2008-04-29:1457</id>
    <published>2008-04-29T23:44:00Z</published>
    <updated>2008-04-29T23:47:34Z</updated>
    <link href="http://hoth.entp.com/2008/4/29/free-open-source-projects-now-in-lighthouse" rel="alternate" type="text/html" />
    <title>Free Open Source Projects Now In Lighthouse!</title>
<content type="html">
            &lt;p&gt;We've just rolled out the beginning of exciting things to come in Lighthouse: Open Source Project support.
To create an OSS Project, just select "Open Source Project" from the &lt;strong&gt;Project Type&lt;/strong&gt; area and choose a license when creating or editing a project.&lt;/p&gt;

&lt;p&gt;&lt;img src="http://hoth.entp.com/assets/2008/4/29/oss.png" alt="Open Source Support in Lighthouse" /&gt;&lt;/p&gt;

&lt;p&gt;This is just the tip of the iceberg on our support for OSS projects.  Our next goal in this area is to roll out an area where anyone can browse and search OSS projects across Lighthouse.  Enjoy!&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://hoth.entp.com/">
    <author>
      <name>justin</name>
    </author>
    <id>tag:hoth.entp.com,2008-04-24:508</id>
    <published>2008-04-24T21:37:00Z</published>
    <updated>2008-04-28T18:31:06Z</updated>
    <link href="http://hoth.entp.com/2008/4/24/migrate-from-jira-or-trac-to-lighthouse" rel="alternate" type="text/html" />
    <title>Migrate from JIRA or Trac to Lighthouse</title>
<content type="html">
            &lt;p&gt;Looking to move from old tickets from JIRA or Trac to Lighthouse?  You're not alone.  Some of our members have gotten creative with the Lighthouse API and implemented some unofficial importers.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href="http://work.onemanswalk.com/2008/4/23/cruise-control-rb-is-moving-to-lighthouse"&gt;JIRA Importer&lt;/a&gt;&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href="http://github.com/shayarnett/trachouse/tree/master"&gt;Trac Importer&lt;/a&gt;&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href="http://github.com/WALoeIII/lighthouse-bugzilla-importer/tree/master"&gt;Bugzilla Importer&lt;/a&gt;&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
          </content>  </entry>
  <entry xml:base="http://hoth.entp.com/">
    <author>
      <name>rick</name>
    </author>
    <id>tag:hoth.entp.com,2008-04-22:70</id>
    <published>2008-04-22T04:41:00Z</published>
    <updated>2008-04-22T05:07:13Z</updated>
    <link href="http://hoth.entp.com/2008/4/22/lighthouse-timeout-troubles" rel="alternate" type="text/html" />
    <title>Lighthouse Timeout troubles</title>
<content type="html">
            &lt;p&gt;If you’re following &lt;a href="http://twitter.com/activereload"&gt;our twitter stream&lt;/a&gt; or been trying to use Lighthouse this afternoon, you will have noticed the slowness.  It’s been tracked down to a firewall issue on the slices and elevated to an EY support issue.  Basically, the slices can’t access the outside world.  This is fine for most functions, but breaks down on a few of them.  The major one is OpenID.  I was astonished to find that it has no concept of timeouts, so requests to openid servers were timing out after several &lt;em&gt;minutes&lt;/em&gt;.  Yikes.  I’ve fixed the code and &lt;a href="http://trac.openidenabled.com/trac/ticket/156"&gt;posted a patch&lt;/a&gt; for the ruby-openid folks.&lt;/p&gt;

&lt;p&gt;Keep an eye on this post or Twitter for when the firewall issue is solved.  And until then, please refrain from using OpenID to log in.  Thanks.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Update&lt;/em&gt;:  And we’re back.  The firewalls are syncing up properly now.&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://hoth.entp.com/">
    <author>
      <name>courtenay</name>
    </author>
    <id>tag:hoth.entp.com,2008-04-17:55</id>
    <published>2008-04-17T03:40:00Z</published>
    <updated>2008-04-17T03:41:21Z</updated>
    <link href="http://hoth.entp.com/2008/4/17/entp-gets-enterprise-working-with-oracle" rel="alternate" type="text/html" />
    <title>ENTP gets ENTerPrise: working with Oracle</title>
<content type="html">
            &lt;p&gt;The fine folks at Oracle have been building a Rails-based &lt;a href="http://mix.oracle.com"&gt;social platform&lt;/a&gt; called Mix for their customers and employees to network and collaborate.  For customers of Oracle, this is an invaluable site to see into the internals of Oracle and ask questions of the relevant teams in a public forum (“Where’s the 10G adapters for &lt;span class="caps"&gt;OSX&lt;/span&gt; Intel?”).&lt;/p&gt;


	&lt;p&gt;It was initially built on a JRuby + Oracle App server + Oracle DB stack, and has been growing since its launch around OpenWorld last year.  Oracle has their excellent internal Apps Lab team hacking on the site, but due to timing constraints needed a fresh team to come in and kick some ass.&lt;/p&gt;


	&lt;p&gt;&lt;a href="http://oracleappslab.com/2008/04/16/mix-messaging/"&gt;We’ve been busy&lt;/a&gt; adding some cool features like direct messaging, while learning the ins and outs of Oracle 10G and building WARs.  Meanwhile, Justin and Kyle been super-busy on some of the coolest javascript I’ve ever seen, for some secret new features yet to be unveiled.  There’s more to be released over the coming months in the lead-up to OpenWorld.  (Honestly, I don’t know where Justin gets the time to work on &lt;a href="http://github.com/Caged/gitnub/tree/master"&gt;Gitnub&lt;/a&gt; , &lt;a href="http://lighthouseapp.com"&gt;Lighthouse&lt;/a&gt; &lt;em&gt;and&lt;/em&gt; client work)!&lt;/p&gt;
          </content>  </entry>
</feed>
