User:LFaraone/Work/2011-W7: Difference between revisions

From OLPC
Jump to navigation Jump to search
(→‎Tasks done: +staging fix)
 
(5 intermediate revisions by the same user not shown)
Line 2: Line 2:
* Fix git conflicts on <code>one</code>.
* Fix git conflicts on <code>one</code>.
* Fix nasty errors due to incorrect permissions of the parser syndication cache on <code>www-staging</code>
* Fix nasty errors due to incorrect permissions of the parser syndication cache on <code>www-staging</code>
* Synced the git repos on one, my personal laptop, and crank, so we're all on the same page / branch / HEAD. (before somehow the master branch was deleted, which caused all sorts of nasty merge conflicts)
* Created redirects to one from old people page, and all the people previously listed on the people page that existed in the new site


== Notes ==
== Notes ==
* What are these nodes doing in the community?
** [http://one.laptop.org/node/640/edit edupad]
** [http://one.laptop.org/node/624/edit columbia]
** [http://one.laptop.org/node/1005/edit atcac]
*:They either have no content, or are unrelated to OLPC.

=== Drupal upgrade process ===
:''now moved to [[Website/Update_Procedure]].''
Steps to upgrade Drupal: '''suggestions welcome'''
# ''Locally:'' Download and untar the new release
# ''Locally:'' Copy new release over checked out repository
# ''Locally:'' Commit changes to branch '''drupal-next'''
# ''Locally:'' Push changes to [http://dev.laptop.org/git crank] in '''drupal-next''' branch.
# ''laptop2:'' Pull from '''origin/drupal-next''' to '''master'''
# ''laptop2:'' Look at the main few pages and make sure there are no major errors
# ''laptop1:'' Make a backup of the current database, and web directory. (latter is sort of redundant, since we use git, but not all files are in VCS)
# ''laptop1:'' Pull from '''origin/drupal-next''' to '''master'''
# ''laptop1:'' Verify new site works as expected

If the site does not work as expected, we <code>git revert</code> to the old codebase, and if worst comes to worst we still have the old database backup and full <code>www</code> backup.

== Future tasks ==
== Future tasks ==



Latest revision as of 20:57, 23 February 2011

Tasks done

  • Fix git conflicts on one.
  • Fix nasty errors due to incorrect permissions of the parser syndication cache on www-staging
  • Synced the git repos on one, my personal laptop, and crank, so we're all on the same page / branch / HEAD. (before somehow the master branch was deleted, which caused all sorts of nasty merge conflicts)
  • Created redirects to one from old people page, and all the people previously listed on the people page that existed in the new site

Notes

  • What are these nodes doing in the community?
    They either have no content, or are unrelated to OLPC.

Drupal upgrade process

now moved to Website/Update_Procedure.

Steps to upgrade Drupal: suggestions welcome

  1. Locally: Download and untar the new release
  2. Locally: Copy new release over checked out repository
  3. Locally: Commit changes to branch drupal-next
  4. Locally: Push changes to crank in drupal-next branch.
  5. laptop2: Pull from origin/drupal-next to master
  6. laptop2: Look at the main few pages and make sure there are no major errors
  7. laptop1: Make a backup of the current database, and web directory. (latter is sort of redundant, since we use git, but not all files are in VCS)
  8. laptop1: Pull from origin/drupal-next to master
  9. laptop1: Verify new site works as expected

If the site does not work as expected, we git revert to the old codebase, and if worst comes to worst we still have the old database backup and full www backup.

Future tasks

  • Investigate the means by which we could import feeds a la planet.
    • We'll want to have a subset of Planet syndicated, subject to manual approval [medium, 3hr]
  • Determine a migration path for URLs on the old blog.laptop.org instance to Drupal
    • Current URL schemes are incompatible.
  • Figure out if we want to keep Wordpress for blog.l.o, and somehow integrate it with Drupal. This eliminates the above URL issue, but add new ones, namely:
    • Unify visual style. b.l.o looks decidedly un-one.l.o-like.
    • Single-user-login between Drupal and Wordpress.
  • Duplicate database for www-staging if it turns out to be needed, double check this.
  • Follow up on mailman migration with Ed et al. (talk with SJ/Adam re formulating specific rationale for upgrade)