Collecting the Internet So You Don't Have To

We work on the Internet. As such, we are constantly consuming information. Believe me, there is a lot of it out there. Sometimes we even forget things unless we write them down. Our blog covers everything from web standards to the muppets, php to comic books, music and everything else that we find interesting. Leave us a note when you drop by.

Setting up a Springloops Git Repository in Coda 2

Technology
Lauren Zacharias
Lauren Zacharias Programmer
Visual Lizard
work
1 (204) 957-5520 ext:156
toll-free
1 (888) 237-9559
url
http://www.visuallizard.com
Lauren Zacharias Database Detective

We've been poking around using Git as source control for a few projects and recently ran into a bit of head-scratching while trying to configure a Coda project with a Springloops Git repository. 

We regularly set up Coda 2 with our Springloops SVN repositories, and have even set up GitHub and BitBucket repos in Coda in the past as well. 

The Problem

The problem we ran into was that Springloops usernames are email addresses, and Coda only asks for your Git URL and password. This means your username needs to be included in the URL.

With a GitHub account, this isn't an issue - the URL will look something like https://github.com/yourusername/reponame.git

The Solution

After some trial and error we determined that the trick with a username which is an email address is to URL encode it before inserting it into the repo URL.

Take note that with the Springloops URL the order is hostname, colon, URL encoded email address, rest of repo URL. For example:

Username: youremail@youremail.com
Springloops Git URL: https://slsapp.com/git/yourspingloopsaccount/reponame.git

Coda URL: https://slsapp.com:youremail%40youremail.com/git/yourspingloopsaccount/reponame.git

Happy Coding!

OpenSSL Heartbleed Bug

Business
Julian Moffatt
Julian Moffatt CEO / Partner
Visual Lizard
work
1 (204) 957-5520 ext:1
toll-free
1 (888) 237-9559
url
http://www.visuallizard.com
Julian Moffatt Purveyor of Good Times

Hello everyone,

If you are online at all you have heard about the bug in OpenSSL called Heartbleed. For the technical details you can visit OpenSSL's news release. If you are interested in an easier to understand write up, you can visit Heartbleed.com. In a nutshell, this bug in OpenSSL allows your encrypted data to be read.

Rest assured, that our security team had our servers patched within hours of this bug being made public. If we are hosting your domain, you are not at risk.

If we are not hosting your domain, you should ask your hosting provider if you are at risk. There are a bunch of versions of OpenSSL that do not have this bug, so it is possible that older infrastructure is running a version of OpenSSL that is immune.

Again, our hosting services are not at risk and have been updated via backporting. To find out more about backporting, you can check out https://access.redhat.com/site/security/updates/backporting/.