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:
Watch the video. Tim Cook is the narrator. Hopefully more companies will work on their environmental responsibility, because we really do only have one planet.
Studio 360 and Original Champions of Design try to rebrand marijuana for mainstream culture with a new icon, posters, typeface, emojis, and term for the drug.
The Verge with a nice write up about project Ara, that module smartphone concept that is in the works. The interesting thing for me is that they have been given 24 months to prove it. Once that time is up, the team is onto the next project.
The article is referencing Sketch 2, but it sure hits on the fact that Fireworks is not a thing anymore. Sketch 3 seems more like a Fireworks replacement to me than an Illustrator or Photoshop replacement. I’ve happily purchased it for $49 on Mac Appstore and will be giving it a whirl.
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.