Howto: How To update the bluesky website

[bill stoddard <bi...@wstoddard.com>]

Spent some time this evening getting the bluesky website cleaned up in 
the svn repository.  If you want to make updates to the site, here is 
how you do it:

First: On your machine... checkout the bluesky website from the svn repo
$ svn co  https://svn.apache.org/repos/asf/incubator/bluesky/webpage  .

Edit the website files as needed.

Second: Check-in your changes to the website svn repo
$ svn commit -m "a brief message describing what you changed"

Your changes & updates are now checked into the svn repo, next you need 
to 'publish' the site:

Third: ssh into people.apache.org
$ ssh people.apache.org
$ cd /www/incubator.apache.org/bluesky/

Fourth: check out the website from svn
$ svn co https://svn.apache.org/repos/asf/incubator/bluesky/webpage .

The site is now published. It will probably take a few hours for the 
infrastructure to pick up the changes, so don't expect to see the 
changes show up immediately.

The next step is very important...

Finally: Change the website permissions to give all bluesky committers 
permission to update the site on people.apache.org
$ chmod -R g+w *


You should NEVER have to scp files from your local machine to 
people.apache.org. You should always be able to do your work on your 
local machine on a copy of the website checked out on your local 
machine.  Check in your changes to the svn repo, then check out your 
changes on people.apache.org.


That's it. Let me know if you have any questions...

Bill

Re: Howto: How To update the bluesky website

[Shan Jiang <da...@gmail.com>]

I'm clear about svn method now. The .sub directory is key for my
questions and it storages the svn client information that help to
execute svn command successfully without client info any more. Thank
you for Bill's careful guidance very much. :)

On 8/23/08, bill stoddard <bi...@wstoddard.com> wrote:
> bill stoddard wrote:
>> Shan Jiang wrote:
>>>
>>> 3. As we know that svn co can copy the files or dirs form svn repos to
>>> /username in local, where does svn update put the copy in
>>> people.apache, current path? I have executed the command of svn update
>>> in the /home path on people.apache. It failed.
>
> the 'co' in 'svn co' means 'checkout', not 'copy'.  When you run 'svn
> co' the .svn subdirectories are created and these subdirectories contain
> files used by the svn client to remember where the svn repository is
> located (and other information about the respositoy too).  When you do
> an 'svn update' in a directory that was checked out, the svn client
> looks into the .svn subdirectories to know how to find the svn
> repository, it an also find which files have changed in the repository
> and refresh those files in your local 'checked out' copy of the
> repository. Does that make sense?  If not, I'll try to explain it in a
> different way. Let me know.
>
> Bill
>
>

Re: Howto: How To update the bluesky website

[bill stoddard <bi...@wstoddard.com>]

bill stoddard wrote:
> Shan Jiang wrote:
>>
>> 3. As we know that svn co can copy the files or dirs form svn repos to
>> /username in local, where does svn update put the copy in
>> people.apache, current path? I have executed the command of svn update
>> in the /home path on people.apache. It failed.

the 'co' in 'svn co' means 'checkout', not 'copy'.  When you run 'svn 
co' the .svn subdirectories are created and these subdirectories contain 
files used by the svn client to remember where the svn repository is 
located (and other information about the respositoy too).  When you do 
an 'svn update' in a directory that was checked out, the svn client 
looks into the .svn subdirectories to know how to find the svn 
repository, it an also find which files have changed in the repository 
and refresh those files in your local 'checked out' copy of the 
repository. Does that make sense?  If not, I'll try to explain it in a 
different way. Let me know.

Bill

Re: Howto: How To update the bluesky website

[bill stoddard <bi...@wstoddard.com>]

Shan Jiang wrote:
> I have practiced the steps Bill told us. It works easily and effectively.
> Previously, Bill have told us to edit and update the files with
> references to "http://incubator.apache.org/guides/website.html#Edit+your+project+status+report".
> At that time, I have three questions about these steps that still
> puzzled me now.
> 1. it seem that svn update on people.apache.org update only the files
> and sub-directories under the directory of bluesky/webpage on svn
> repos, doesn't it? I have testified it in practice.
>   
> 2. Does svn update on people.apache associate only with the deirectory
> of bluesky/webpage on svn repos? Administrator of people.apache did
> it?
> 3. As we know that svn co can copy the files or dirs form svn repos to
> /username in local, where does svn update put the copy in
> people.apache, current path? I have executed the command of svn update
> in the /home path on people.apache. It failed.
> Thanks a lot for unpuzzling me!
>
>   

I'm not sure how to begin answering these questions... so I'll start 
writing and hopefully things will be clearer at the end (^_^)

Try this on your local machine:
$ svn co https://svn.apache.org/repos/asf/incubator/bluesky

What you will get is the ENTIRE bluesky svn repository, containing the 
website, trunk, tags, everything.

Now try this (in a new directory on your local machine)
$ svn co https://svn.apache.org/repos/asf/incubator/bluesky/website    foo

You have just checked out the bluesky website (and only the bluesky 
website), and placed it in directory 'foo' on your local machine.  If 
you do an:
$ ls -a
you will see a .svn subdirectory was created as part of your checkout.  
This subdirectory is used by the svn client. You should not touch 
anything in this subdirectory.

So that demonstrates how you can check out various parts of the entire 
bluesky svn repository and manage them in different places on your local 
machine.

Next exercise (this is a virtual exercise):
I want to modify something on the bluesky website.  Let's assume that I 
have already checked out the website as noted above using the 'svn co' 
command.

First... I cd into the website directory of the checked out website on 
my machine, then
$ svn update
This command pulls in any changes that others have made to the website.  
I always issue svn update before I start changing code in the repo to 
make sure I am working with the most recent code. I don't have to 
provide the https://svn.apache.org.... arguments because all that info 
is stored in the .svn subdirectory.

Next, make my changes. Then...
$ svn diff
This will display a 'unified diff' (you can google that phrase) of the 
changes I made.  Review the changes, and if you are satisfied, commit 
the changes like this:

$ svn commit -m "description of your change"

Your changes will be sent to the svn server.

So.. before I continue writing, does that answer any questions for you?

Bill

> On 8/21/08, bill stoddard <bi...@wstoddard.com> wrote:
>   
>> bill stoddard wrote:
>>     
>>> Spent some time this evening getting the bluesky website cleaned up in
>>> the svn repository.  If you want to make updates to the site, here is
>>> how you do it:
>>>
>>> First: On your machine... checkout the bluesky website from the svn repo
>>> $ svn co  https://svn.apache.org/repos/asf/incubator/bluesky/webpage  .
>>>
>>> Edit the website files as needed.
>>>
>>> Second: Check-in your changes to the website svn repo
>>> $ svn commit -m "a brief message describing what you changed"
>>>
>>> Your changes & updates are now checked into the svn repo, next you
>>> need to 'publish' the site:
>>>
>>> Third: ssh into people.apache.org
>>> $ ssh people.apache.org
>>> $ cd /www/incubator.apache.org/bluesky/
>>>
>>> Fourth: check out the website from svn
>>> $ svn co https://svn.apache.org/repos/asf/incubator/bluesky/webpage .
>>>       
>> It's late, has been a long day and I'm not thinking clearly... this
>> fourth step is wrong.  Should do an svn update rather than a checkout:
>>
>> $ svn update
>>
>> That should pull in all files that have changed in the svn repo.
>>
>> You still need to issue chmod g+w on any files that were updated to give
>> them group write permissions.
>>
>> very simple isn't it? :-)
>>
>> Bill
>>
>>     
>
>   

Re: Howto: How To update the bluesky website

[Shan Jiang <da...@gmail.com>]

I have practiced the steps Bill told us. It works easily and effectively.
Previously, Bill have told us to edit and update the files with
references to "http://incubator.apache.org/guides/website.html#Edit+your+project+status+report".
At that time, I have three questions about these steps that still
puzzled me now.
1. it seem that svn update on people.apache.org update only the files
and sub-directories under the directory of bluesky/webpage on svn
repos, doesn't it? I have testified it in practice.
2. Does svn update on people.apache associate only with the deirectory
of bluesky/webpage on svn repos? Administrator of people.apache did
it?
3. As we know that svn co can copy the files or dirs form svn repos to
/username in local, where does svn update put the copy in
people.apache, current path? I have executed the command of svn update
in the /home path on people.apache. It failed.
Thanks a lot for unpuzzling me!


On 8/21/08, bill stoddard <bi...@wstoddard.com> wrote:
> bill stoddard wrote:
>> Spent some time this evening getting the bluesky website cleaned up in
>> the svn repository.  If you want to make updates to the site, here is
>> how you do it:
>>
>> First: On your machine... checkout the bluesky website from the svn repo
>> $ svn co  https://svn.apache.org/repos/asf/incubator/bluesky/webpage  .
>>
>> Edit the website files as needed.
>>
>> Second: Check-in your changes to the website svn repo
>> $ svn commit -m "a brief message describing what you changed"
>>
>> Your changes & updates are now checked into the svn repo, next you
>> need to 'publish' the site:
>>
>> Third: ssh into people.apache.org
>> $ ssh people.apache.org
>> $ cd /www/incubator.apache.org/bluesky/
>>
>> Fourth: check out the website from svn
>> $ svn co https://svn.apache.org/repos/asf/incubator/bluesky/webpage .
> It's late, has been a long day and I'm not thinking clearly... this
> fourth step is wrong.  Should do an svn update rather than a checkout:
>
> $ svn update
>
> That should pull in all files that have changed in the svn repo.
>
> You still need to issue chmod g+w on any files that were updated to give
> them group write permissions.
>
> very simple isn't it? :-)
>
> Bill
>

Re: Howto: How To update the bluesky website

[bill stoddard <bi...@wstoddard.com>]

bill stoddard wrote:
> Spent some time this evening getting the bluesky website cleaned up in 
> the svn repository.  If you want to make updates to the site, here is 
> how you do it:
>
> First: On your machine... checkout the bluesky website from the svn repo
> $ svn co  https://svn.apache.org/repos/asf/incubator/bluesky/webpage  .
>
> Edit the website files as needed.
>
> Second: Check-in your changes to the website svn repo
> $ svn commit -m "a brief message describing what you changed"
>
> Your changes & updates are now checked into the svn repo, next you 
> need to 'publish' the site:
>
> Third: ssh into people.apache.org
> $ ssh people.apache.org
> $ cd /www/incubator.apache.org/bluesky/
>
> Fourth: check out the website from svn
> $ svn co https://svn.apache.org/repos/asf/incubator/bluesky/webpage .
It's late, has been a long day and I'm not thinking clearly... this 
fourth step is wrong.  Should do an svn update rather than a checkout:

$ svn update

That should pull in all files that have changed in the svn repo.

You still need to issue chmod g+w on any files that were updated to give 
them group write permissions.

very simple isn't it? :-)

Bill