January 2nd, 2008 by rick

Bringing in the new year

7 comments on 310 words

Wow, what happened to 2007? As you may already know, Justin and I set up ActiveReload headquarters in a really cool office space in downtown Portland, along with the great folks Kongregate. We’ve been keeping our heads low finishing up client work, settling into the new city, and keeping Lighthouse afloat.

Now that the 2008 is here, let’s get down to business:

Warehouse v1.1.5 is nearly ready. It adds some slick SVN Annotate support (after we got schooled on how to implement it in ruby by Morgan Schweers, one of our forum users… thanks!), as well as removing the requirement for repository subdomains. If you’re interested in trying out the beta, let me know via direct message on twitter or company@activereload.net. Act fast, supplies are limited! Be sure to include an email address too.

Lighthouse has a visual refresh in the works, but Justin’s been bogged down by other client design work. I’m hoping to get it out really soon. Also, if emails are any indication, folks are really wanting OpenID support. It’s something I want too, but I’ve so far classified that as a ‘nice to have’ feature and pushed it below other more important features.

One last thing, I apologize for the too-frequent issues with Lighthouse. We recently added a ‘ping’ url to check the status of individual mongrel processes, but apparently our monitoring setup isn’t checking it properly.

Discussion

  1. Kevin Stewart Kevin Stewart said on January 3rd

    What about Mephisto? Mark was added to the core team awhile ago, but there’s been no visible change (i.e. new releases made available without having to grab from trunk). Posts in the Google Group are pretty infrequent as well. I understand that Mephisto doesn’t pay the bills, but I’d like to know if there is a future with it. I haven’t moved to another Ruby blog because they all seem to have the same issue with progress: Typo, SimpleLog, etc. There’s a burst of activity then everything dies down. Typo just updated to 5.0, then pulled the release due to a major data loss problem. I currently have 3 sites running thanks to Mephisto’s multi-site feature. I am now debating whether to migrate them all or stick with it. And, yes, I know that I can contribute to the project but I’d only do that if there were more visible interest in Mephisto.

    Kevin

    PS – I’m not trying to do a Zed here. :-) I actually like Mephisto as well as your other projects. Just concerned is all…

  2. Will Will said on January 3rd

    You know I had someone on xbox ask me if you two were a) alive? or b) mad at them?

  3. rick rick said on January 3rd

    Mephisto works well enough for me, so there’s not a lot of motivation to work on it. I’ve been trying to open up commit access to more folks that actively use it, but it’s really difficult to drum up actual code.

    It seems the lifecycle of these types of projects depend solely on it being a source of income for the creators. Perhaps you should seek out one of these other communities (wordpress or expression engine spring to mind).

  4. Aeon Aeon said on January 4th

    Hi Rick

    What about Beast? Is someone working on it? Is there a way to contribute? Are there plans for it? Is there a Warehouse/Lighthouse project set up for it? Is it using git now?

    I’m using the 1.0 version for a project, but I wanted to switch to edge so that I can contribute patches and so I don’t have to fix things that have already been fixed in trunk.

  5. rick rick said on January 4th

    Hey, it’s being rewritten for Rails 2.0, for various reasons. Up til now we’ve been taking patches on the main beast forum itself, but I think I’ll probably go with full Lighthouse.

    There’s a git repo now, but I haven’t posted about it yet.

  6. Aeon Aeon said on January 11th

    So what’s the git repo url? I found it by accident a few days ago, but now lost it again. The more I think about the best way to unspool my changesets from my local repo to reapply them to a checkout of trunk, the more I think that converting my local repo to git, importing stable-1.0 into a separate local repo, running a diff between the two and applying it to a local copy of trunk git repo might be the easiest way to do it. That might be doable with svn too, but keeping the my local branch of beast up to date with trunk patches might be much easier with git.

    Any suggestions? :)

  7. Dan Martell Dan Martell said on January 31st

    Rick, I would love to see some time spent on cleaning up some of the screens/flow in LH … I’m a big fan, but bang my head sometimes. Patiently waiting.

Sorry, comments are closed for this article.