You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I went with a fast-and-hackish way of getting ~51 event migrations finished in an afternoon; I imported the old index.html pages into welcome.md via the files I added in #290 used thusly:
for foo in $(cat events-to-migrate);do echo $foo | ./migrate-events.sh;done
I deleted the files for the ones that didn't happen: e40512c
I then viewed the start dates from the webby directory:
$ pwd
/Users/bridget/github/devopsdays-webby/site/content/events
Bridgets-MacBook-Air:events bridget$ more */_event_date_start.txt
and manually edited the start and end dates into the yaml:
for foo in $(cat events-to-migrate);do vi data/events/$foo.yml ;done
Yes, that kinda sucked. No, there was no reasonable way to get that data from the inconsistently-set-up date files.
. Known side effects:
Lots of broken images (their paths are mostly relative and need to be absolute)
without the "OLD" (or equivalent text), the imported text showed as blank. (That could be sedded out to something less visible.)
Currently a bunch of cruft shows:
I would be fine with any additional migration option that preserves as much history as possible while de-duplicating sponsor images that make the repo too big.
I regard this as temporary so we don't have to have too many old events offline for any amount of time. I think real migration/de-duplication/binary-delete of a given event's extraneous logos would still be ideal.
The text was updated successfully, but these errors were encountered:
I went with a fast-and-hackish way of getting ~51 event migrations finished in an afternoon; I imported the old index.html pages into welcome.md via the files I added in #290 used thusly:
I deleted the files for the ones that didn't happen: e40512c
I then viewed the start dates from the webby directory:
and manually edited the start and end dates into the yaml:
Yes, that kinda sucked. No, there was no reasonable way to get that data from the inconsistently-set-up date files.
. Known side effects:
sed
ded out to something less visible.)I would be fine with any additional migration option that preserves as much history as possible while de-duplicating sponsor images that make the repo too big.
I regard this as temporary so we don't have to have too many old events offline for any amount of time. I think real migration/de-duplication/binary-delete of a given event's extraneous logos would still be ideal.
The text was updated successfully, but these errors were encountered: