User:LFaraone/Work/2011-W6: Difference between revisions
< User:LFaraone | Work
Jump to navigation
Jump to search
(init.d) |
(→Notes: drupal replication) |
||
(6 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
== Tasks done == |
== Tasks done == |
||
* Combine [http://planet.laptop.org Planet Laptop] and [http://planet.sugarlabs.org Planet Sugar] into one feed using [http://pipes.yahoo.com/ Yahoo Pipes]. ([http://pipes.yahoo.com/lfaraone/planet_sl_olpc pipe published here]) |
* Combine [http://planet.laptop.org Planet Laptop] and [http://planet.sugarlabs.org Planet Sugar] into one feed using [http://pipes.yahoo.com/ Yahoo Pipes]. ([http://pipes.yahoo.com/lfaraone/planet_sl_olpc pipe published here]) |
||
* Footer link to Dashboard in Drupal |
|||
* Copy over database + files to <code>www-staging.l.o</code> from <code>one.l.o</code> |
|||
== Notes == |
== Notes == |
||
* Drupal is currently a point release behind ('''6.19''' vs '''6.20'''), are we handling upgrades or is GT? |
|||
**Some other plugins, notably Google Analytics, are currently marked "not supported", and several others have updates available |
|||
*Attempts to migrate <code>one</code> database to <code>www-staging</code> resulted in a variety of odd failures: |
|||
**Not all tables were migrated when restoring from webif via backup created from webif on <code>one</code>, but restoring <code>www-staging</code> was without problems. |
|||
**Attempts to use <code>mysqlimport</code> resulted in Access Denied errors (for the specific tables, not in general) |
|||
*:Eventually solved via command <code>mysql -u drupal -p drupal < drupal-one.sql</code>. |
|||
*Attempts to replicate the database on my local system resulted in a system that was similar to, but not identical, to the main Drupal site. Namely, I couldn't get the admin webif working. |
|||
== Currently working on == |
== Currently working on == |
||
Line 20: | Line 29: | ||
* Duplicate database for www-staging if it turns out to be needed, double check this. |
* Duplicate database for www-staging if it turns out to be needed, double check this. |
||
* Follow up on mailman migration with Ed et al. |
* Follow up on mailman migration with Ed et al. (talk with SJ/Adam re formulating specific rationale for upgrade) |
Latest revision as of 18:45, 9 February 2011
Tasks done
- Combine Planet Laptop and Planet Sugar into one feed using Yahoo Pipes. (pipe published here)
- Footer link to Dashboard in Drupal
- Copy over database + files to
www-staging.l.o
fromone.l.o
Notes
- Drupal is currently a point release behind (6.19 vs 6.20), are we handling upgrades or is GT?
- Some other plugins, notably Google Analytics, are currently marked "not supported", and several others have updates available
- Attempts to migrate
one
database towww-staging
resulted in a variety of odd failures:- Not all tables were migrated when restoring from webif via backup created from webif on
one
, but restoringwww-staging
was without problems. - Attempts to use
mysqlimport
resulted in Access Denied errors (for the specific tables, not in general)
- Eventually solved via command
mysql -u drupal -p drupal < drupal-one.sql
.
- Not all tables were migrated when restoring from webif via backup created from webif on
- Attempts to replicate the database on my local system resulted in a system that was similar to, but not identical, to the main Drupal site. Namely, I couldn't get the admin webif working.
Currently working on
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)