introducing something new to chew on
Chaw is an application designed to help better manage version-controlled projects. You can read about some of the features in Chaw on the wiki http://thechaw.com
As some of you may have noticed, the source for http://book.cakephp.org was released on http://thechaw.com/cakebook. Making the source available is a great step in improving the documentation efforts of CakePHP. In addition, the release allows other developers to use the application for the documentation of their own projects.
So, you may be wondering about http://thechaw.com. This application was built because I wanted to have more control over the management of our projects. The ability to add features as we need and ensure that the code is in a safe place is very important to me. I see the development of this application as a big step forward in the development of the CakePHP. With this application, we will begin rolling out ways to make it easier for developers to collaborate and share. Stay tuned for more developments. Did someone say plugin server? Oh, you will have to be at CakeFest #2 - http://cakefest.org to hear about that...
The goal behind http://thechaw.com is quite simple. Provide a simple interface to consolidate all the CakePHP development in one place. This goal may raise the question of what will happen to cakeforge - http://cakeforge.org. The answer is that we hope to transition the projects on cakeforge to the chaw. This will give us an opportunity to clean out some of the abandoned projects and moving forward we will be able to provide a better service.
I truly you hope you all enjoy http://thechaw.com. If you have any questions or comments stop by #chaw on irc.freenode.net or send a message to http://groups.google.com/group/chaw
So, you may be wondering about http://thechaw.com. This application was built because I wanted to have more control over the management of our projects. The ability to add features as we need and ensure that the code is in a safe place is very important to me. I see the development of this application as a big step forward in the development of the CakePHP. With this application, we will begin rolling out ways to make it easier for developers to collaborate and share. Stay tuned for more developments. Did someone say plugin server? Oh, you will have to be at CakeFest #2 - http://cakefest.org to hear about that...
The goal behind http://thechaw.com is quite simple. Provide a simple interface to consolidate all the CakePHP development in one place. This goal may raise the question of what will happen to cakeforge - http://cakeforge.org. The answer is that we hope to transition the projects on cakeforge to the chaw. This will give us an opportunity to clean out some of the abandoned projects and moving forward we will be able to provide a better service.
I truly you hope you all enjoy http://thechaw.com. If you have any questions or comments stop by #chaw on irc.freenode.net or send a message to http://groups.google.com/group/chaw
Comments
Comment
1 Nice but...
I'll have to install bakery's db first then
Comment
2 SVN credentials problem
Some people have already mentioned this in the comments to Andy's thread http://www.ad7six.com/MiBlog/CookbookSourceReleased#comments, but I figured this article here is the right place to address the matter, as Andy is probably not to be blamed for anything else besides actually developing the Cookbook :)
Could anyone give some hints (either here or on thechaw.com website) as to what would the proper way to checkout the code be?
Thanks in advance and congratulations on the good work on both the Cookbook and Thechaw.com!
Comment
3 Nice but... there is no but.
You make it sound like thats a bad thing and a surprise.
Please see http://thechaw.com/cakebook/browser/docs/install_instructions.txt if you have any install difficulties.
Comment
4 [Updated] SVN credentials problem
Okay, I got it figured... For those who're still stuck here's what i did:
1. I was wrong to assume that because there were separate input fields for SVN and GIT public keys in my profile form on thechaw.com, the project could be accessed as both - SVN and GIT repository. It seems that SVN is being used when accessing a project stored in an SVN repo - which is not the case with Cakebook...
2. I created my private/public keys and copy/pasted the public string in my thechaw.com profile edit form as a GIT key
3. I created ~/.ssh/config file with the following text:
Host thechaw.com
User git
Port 22
Hostname thechaw.com
IdentityFile ~/path/to/your-private-key-filename-here
TCPKeepAlive yes
IdentitiesOnly yes
I first tried using my thechaw.com username instead of 'git' on both places - in the git clone command url, and in .ssh/config, but to no success. Then I reverted to the default 'git'
4. I chmoded my private key file to 600 as otherwise it's ignored
chmod 600 ~/path/to/your-private-key-filename-here
5. I then cloned the code using what's suggested on the website:
git clone git@thechaw.com:cakebook.git
I guess everyone used to working with GitHub is probably quite familiar with this stuff, but for SVN guys like me it was a stopper :)
Comment
5 re: Nice but... there is no but
I didn't say it was bad, although it was a surprise. That the install wasn't to the level of automagic the Cake crew has made us used to.
Also, the schema files had some problems with the rght index in the node table.
Question
6 Adding first admin user
I originally thought I would add a users through and ACL console (which I'm still understanding) but that wasn't the case.
Did anyone manually generate an admin user? What group and level did you use?
Thanks!
Wilson
Comment
7 RE: Adding first admin user
What I did was that I created a user with the bakery, and changed level_id to 1.
Also, I tried the bakery trunk first and then the 2.x branch, I ended using the 1.x branch.
You also have to create the tmp directory structure, use:
mkdir -p tmp/cache/models tmp/cache/views tmp/cache/persistent tmp/logs tmp/sessions tmp/tests
Comment
8 Permission denied (publickey)
I tried your instructions step by step, but I just encountered this message:
Permission denied (pubkey)
fatal: The remote end hung up unexpectedly.
fetch-pack from 'git@thechaw.com:cakebook.git' failed.
Comment
9 Re: Permission denied (publickey)
Are you in MAC OS X?
I thing these steps is desired to MAC OS X users.
To other OS's, please check it: http://github.com/guides/providing-your-ssh-key
Comment
10 RE: Permission denied
I got it! my problem was because I didn't submitted my RSA keys to thechaw.com by going to my user profile named as 'edit' link.
Comment
11 Super cool!
I will definitely use this at some point - good stuff! Might make a good combo with my server control panel I'm writing in Cake.