didactic_cudgel: (Default)
didactic_cudgel ([personal profile] didactic_cudgel) wrote in [site community profile] dw_dev2011-05-17 02:08 pm
  • Add Memory
  • Share This Entry
Entry tags:

Keeping production current.

I run a production DW-powered site and I want to keep it up to date with the latest code fixes and features.

In asking #dreamwidth-dev about following this procedure: http://wiki.dwscoalition.org/notes/Dev_Maintenance firefoxfey recommended that I find out what the latest post-release final tag is an update only to that tag to avoid getting untested dev features, but didn't know the procedure. I was advised to ask here and so I am :)

If I want to keep my code current, but reduce the chance of pulling down untested code, how do I find and limit code to the post-release final tag?

Also, Fey suggested making sure that I'm aware of any database changes. Are those announced separate from code pushes?
Flat | Top-Level Comments Only
didactic_cudgel: (Default)

Full Update/Upgrade/Procedure

[personal profile] didactic_cudgel 2011-05-19 01:28 pm (UTC)(link)
OK ... soo ... just to make sure I understand. The procedure should be:

  1. See Code Push in [site community profile] dw_maintenance.

  2. Run cvsreport -update

  3. Run cvs/dw-free/hg tags - note Tag info

  4. Wait one week or so.

  5. Run cvs/dw-free/hg tags -
    • a. If highest (non-tip?) tag is different, wait one week more and repeat step.

    • b. If highest tag matches, proceed.

  6. Copy all config files to cvs/< my journal local >/etc/
    • a. Do this for any file I've modified in the code, like schemes, etc? - copied into their own cvs/< my journal local >/< original path >?

    • b. Do schemes follow the same "override with -local" effect as the config files? If I've modified vertical-gradation heavily, will it be overwritten with a code-push? Will gradation-vertical-local override gradation-vertical?

  7. Run "hg update -r [tagname]"

  8. Run diff on the files in cvs/< my journal local >/etc/config* to make sure none of my changes will be overwritten - any overwritten changes should be moved to a -local.pl file.

  9. sudo /etc/init.d/apache2 stop

  10. cd $LJHOME

  11. run cvsreport.pl without arguments to get a preview of changes being implemented

  12. bin/cvsreport.pl -sync -cvsonly

  13. bin/cvsreport.pl -sync -cvsonly

  14. LJHOME/bin/upgrading/update-db.pl -r -p --innodb

  15. $LJHOME/bin/upgrading/update-db.pl -r --cluster=all --innodb

  16. $LJHOME/bin/upgrading/texttool.pl load

  17. start apache


Does that look right? I could also, I assume, create the update scripts in the Dev_Maintenance wiki (where a lot of this info came from) and replace the relevant parts in my list here.
Edited 2011-05-19 13:32 (UTC)
exor674: Computer Science is my girlfriend (Default)

Re: Full Update/Upgrade/Procedure

[personal profile] exor674 2011-05-19 02:35 pm (UTC)(link)
You really should be fine waiting a week, just monitor the dw-maint post to see if there are any lingering issues and just make sure no new tags show up with the minor ( that is 1.0.x -- the x changing ) different.

6. You should not be overriding any files, really -- because you will miss out on any changes, and they could cause incompatibilities -- besides the config files.

What are you overriding? -- anything that DW has needed to should have a local component or a hook.

6b. See:

http://hg.dwscoalition.org/dw-nonfree/file/6883b468b6b7/schemes/_dreamwidth.tt
http://hg.dwscoalition.org/dw-nonfree/file/6883b468b6b7/schemes/gradation-vertical-local.tt
http://hg.dwscoalition.org/dw-nonfree/file/6883b468b6b7/cgi-bin/DW/Hooks/SiteScheme.pm

And then use grad-vertical-local in all your config places.

But any file you create yourself should be in your cvs/<blah> directory.

7. You should also do that to the closest tag before [tagname] ( or past, if there's a different minor ) in:

dw-free
bml
js
perlbal
s2

8. No, compare the config files with 'hg diff -r <last tag> etc/config.pl' ( and the same with the two templates in doc ) and merge in any relevant looking changes ( new options, etc... )

11. Yep, and you can 'cvsreport.pl --diff filename' if you want to see what changed.
didactic_cudgel: (Default)

Re: Full Update/Upgrade/Procedure

[personal profile] didactic_cudgel 2011-05-19 04:01 pm (UTC)(link)
6a. I'm not positive that I did, very much, except for the vertical-gradation scheme because I'm a bit bumbly and didn't know any better - despite the warnings in the scratch installation code, that is. I didn't understand the relationship between x.file and x-local.file before. Yay! Bring out the sub, I'm goin' code-divin'!

6b. Thank you :)

7. Are you saying to run hg update from each folder?

8. Thank you

11. Neat! :)

Thank you all. I have a history of jumping feet first into things I don't understand even a little. Same thing happened with phpBB3. I knew this would be complex, but, as always, I underestimated the complexity and overestimated my ability. You've helped make this so much more painless. Not only I appreciate it, but my users do too. :)
Flat | Top-Level Comments Only