We’ve just added an extra 54 icons to the project icon selector which allows you to select from an even bigger range of icons to use for your projects.
If you have any ideas for icons you’d like to see, just let us know on Twitter.
We’ve recently started to use HipChat as replacement to our internal IRC server for discussions between staff and it’s fantastic. It provides significantly more functionality than both IRC and Campfire allowing us to easily share information around the office and with our staff working from home.
Consequently, Codebase now supports HipChat as a notification method for repository pushes, commits, deployments as well as ticket updates. You can configure these notifications from the Notifications page which can be found from the Project Properties page. Once you have setup the notifications, you will receive messages into your desired chat room whenever an action is carried out.
The individual messages are colour coded – pushes & commits are shown in purple, deployments in red and ticket updates in green. These will not automatically notify users so they won’t constantly be bothered with notifications each time an action takes place – the message will just appear quietly in the room.
If you currently use Campfire or IRC for this, I’d strongly encourage you to take a look at it. It’s significantly more feature-rich than the alternatives.
Disclaimer: the link to HipChat above is an affiliate link – HipChat will make custom emoticons in exchange for referrals and we’ve got some ideas for icons we’d love to see in the HipChat interface.
We’ve just overhauled the Codebase project assignments & permissions interface to make things more user friendly and easier to use. The previous system had two separate interfaces – one for setting user permissions and the other for selecting which users should be assigned to projects. The new interface allows you to assign users and select what permissions they should be granted at the same time.
If you used to find the old method a bit of a headache, I encourage you to take a look and see what you think of the improvements. Just head over to a project and select Manage Project Assignments from the yellow settings box on the right.
We’ve just pushed a new feature to Codebase which will allow users to export an entire archive of all the data stored within their account. All exports are sent to you as a ZIP file containing an array of XML files and, if requested, your repository data.
In order to request an export of your data you’ll need to select Settings followed by Export Account Data from the menu at the top of the screen – to access this option you must have the appropriate permission defined as part of your access role, by default only account administrators have this level of access. Once requested, we will create the export and send you an email with a link to download the file as soon as it has been completed. To use this feature you will need a package of Small or higher.
There have been a lot of discussions recently regarding the use of SSL, along with various high profile attacks against users of services such as Facebook where account credentials, and more commonly, cookies have been stolen.
Using an insecure connection to access any web application can pose two security risks. Firstly, and most commonly understood is the risk of sending passwords over an insecure connection. Secondly, the more widely exploited issue of cookies being sent over an insecure connection, even after authentication is completed and users are simply browsing a site.
The risk posed by these issues is extremely low when browsing from a trusted, wired Internet connection, however increase in use of insecure wireless hotspots means that these risks need to be addressed.
Codebase has always offered SSL connectivity as an option to paid accounts, and has allowed users to choose whether to connect with SSL or not. From today, we have made several changes to the way we offer SSL, in order to ensure that all customers are protected from the issues.
We have recently completed the migration of all users onto our new v4 platform and have updated our DNS records to ensure all customers are routed to this new infrastructure in most efficient and fastest manner available.
This change should not affect most customers but if anyone has specific firewall rules or haspointed services directly to our old IP addresses, you should note the new details provided below.
Over the last 3-4 months we have been slowly migrating all our customers from our v3 platform in Manchester to our v4 platform hosted in Bournemouth. Due to the size of our customer base and the amount of data stored on our infrastructure, the migration has been performed on an account by account basis allowing us to move individual customers with the minimum amount of downtime possible.
On Sunday, we finished the migration of the last set of accounts and the v3 infrastructure will be shut down later this week. This marks a key milestone for us and with this migration out of the way, we can continue to focus on further developing the service and working through the hundreds of feature requests & suggestions our users have been submitting.
We are pleased to announce that after 12 months of development and testing, Codebase v4 is ready! We are sorry that this announcement comes 3 months later than planned, but we hope it will be worth the wait.
Codebase v4 adds a number of new features that we frequently get requests for, along with a lot of changes to both the interface and the infrastructure to make things faster, more stable and easier to use. Here are a few of the major updates:
We plan to migrate all users to the new service over the next couple of weeks, however if any of these features appeal to you, feel free to drop us an email and we will move you to the top of the list.
We hope you enjoy the new version of Codebase. Please let us know if there is anything you feel we could improve on.
As many of you will already know, we are now a good way through development of the next major update to Codebase. A number of people have asked about the progress of Codebase v4 so we thought it was time we posted some information about the product so far. We know that nobody likes vapourware!
After 9 months of heavy re-development, Codebase V4 is almost complete. In addition to major performance and stability improvements to the backend, we have completed work on an array of new features.
We are currently in the process of fully testing and polishing the user interface to ensure it meets the high standards we aim for with all our applications.
More screenshots can be found on Flickr
We will be deploying the updates to all users in Q1 of this year, and will begin beta testing in the coming weeks. We would like to thank all our users for their feedback which has helped us to make Codebase a better product.
In preparation for Codebase v4 we need to make a few changes to the Codebase API. Codebase v4 includes a completely new API (including OAuth2 authentication as well as a completely new versioned URL structure) and because of this we need to make a minor change to the way the current API works in order to preserve backwards compatibility. We strongly suggest that any developers using the API upgrade their implementations as outlined below to ensure applications continue to operate once v4 has been deployed.
Currently, a request can be made to the Codebase v3 API using the following format:
curl -H 'Content-type: application/xml' -H 'Accept: application/xml' \
-u '{username}:{apikey}' https://{account}.codebasehq.com/
api3.codebasehq.com.account/username, so for example if you wish to access the potatoes account as the user dave you should send potatoes/dave.curl -H 'Content-type: application/xml' -H 'Accept: application/xml' \
-u '{account}/{username}:{apikey}' https://api3.codebasehq.com/
The rest of your URL should remain the same as before (for example, if you wish to access tickets you should just send api3.codebasehq.com/project-name/tickets as before but with the new URL and username string.Once v4 has been deployed the API structure detailed above will continue to function for at least 6 months to allow developers to migrate their applications to the new much improved API.
We apologise for any inconvenience this may cause and if you have any questions, feel free to contact support