26 replies
-
@zachleat awesome, thanks! 🙏
@nhoizey The code is in _pretty_ good shape, it’s maybe a quick review away from publishing! README should have some very terse steps to get going
@zachleat great idea! 👍
Do you want to open an issue for this, or should I do it and mention your toot?
@zachleat I'm currently running it on my backup. More than 30 minutes already, is the first build supposed to take longer than next builds?
@nhoizey if it’s taking forever I’d try replacing the eleventyImg local media caching with just a straight passthrough to the image sources (just for testing)
@zachleat the build just finished!
@zachleat I think it took a long time because it had to get almost 6000 images from Twitter API
@nhoizey awesome!
@nhoizey repeats should be much faster with the local cache folder
@zachleat but I know I have more than 100.000 tweets, so should I be worried with "only" 55477 files written?
@zachleat are images binaries also in the `.cache` folder?
@nhoizey yeah so if you clear your _site folder it should still be fast. I think it might be better to have those images in source control though, not sure why I chose to write them to _site
@zachleat it takes only 90 seconds after removing the `_site` folder, really great! 👍
It's almost 2em here, I'll continue tomorrow… 😅
@nhoizey ack! Go to bed!!
-
@nhoizey when you wake up—just fyi I made a few more changes and merged to main
https://github.com/tweetback/tweetback
Namely that images are now written to `/img/` so that CI builds don’t have to fetch them the first time 🏆
-