Re: [Openscrobbler-devel] Development Environment / Tools

[Mr. D. <mr...@gm...>]

Ok, I'm all set on the svn stuff, let the devlopment begin!
Almighty Obenscrobbler dev lead, assign a task and i shall complete it.

- deep


On Mar 12, 2005, at 1:04 AM, Jonathan Dance wrote:

> Hi All,
>
> I have the following development news. Note that we aren't really 
> ready to start "real" development but I figured I'd get the ball 
> rolling.
>
> Our subversion repository has been up for some time. It is accessible 
> at http://wuputah.com:81/svn/openscrobbler. The repository is now 
> world-readable, but you will need an account to commit changes. When 
> you need an account, please contact me.
>
> To learn how to use Subversion, I have attached a document I wrote up 
> a while ago at Agora. The URLs are wrong but the idea is the same. 
> Also, don't use the links to the software; go to the web sites and get 
> the latest version.
>
> PHP5 is running on our Apache2 server on Port 81 (the same port as 
> access to subversion). An automatically updating checked out copy of 
> the code (a so-called "sandbox") is available for testing at 
> http://openscrobbler.wuputah.com:81. What this means is when you 
> commit a change to the SVN repository, the web site above 
> automatically updates itself with the latest code.
>
> Which brings me to this point. I would prefer if all code that gets 
> committed is "parsable." (Basically, it shouldn't contain parse 
> errors.) In compiled languages, this would mean you would compile it 
> and make sure it doesn't "break the build." There is no way to do this 
> in PHP but to test it some other way. Now, getting PHP5/MySQL/Apache 
> running on your local computer is a minor feat; it's possible, yes, 
> but not easy. I would not recommend it because, in addition, you will 
> have issues keeping your copy of the MySQL database in sync with the 
> development one.
>
> An alternative is to do the development on the server. You check out a 
> copy on the server, set it up as necessary, make it web accessible, 
> and start working. You could then use Transmit + SubEthaEdit (or your 
> favorite FTP client/text editor) to edit the files. Alternately, you 
> could download the whole project and use Transmit to synchronize the 
> folders (this way you can browse the project locally, without being 
> slowed up by Transmit) as necessary. Either way, once you have tested 
> your changes, you can commit them on the server. Be aware:
> - If you choose to synchronize, be careful when doing "svn update" - 
> you should synchronize your local copy UP before updating, and 
> synchronize DOWN after updating, else your local copy will suck and 
> everyone will call you a persnickety flibbertigibbet.
> - Also, I highly recommend getting Transmit 3 if you're doing any work 
> like this; the column view is fantastic.
>
> That's all for now.
>
> So say we all,
>
> --JD
>
> <svn-help.html>