If you looked today, and clicked on one of the “uploaded” images, you would have seen some of this kind of stuff:
Because I had the path set wrong. And the link. And on some of them the link and path.
The path variable for URL’s to uploaded images (this is our meme archive) is now being set correctly on both the front and backend, and we are moving to more truly ‘serverless’ space. Note: We have a bit more work to do in order to be able to turn on submissions for everyone else (if you have the points, natch), but these are essential steps to containerizing and commodifying each part of the application.
Right now the front and back end are hot-swappable. The storage solution is hot-swappable and the DB as well. By keeping each element defined within itself, we have the ability to fix/upgrade/change each element individually and maintain End-to-End cohesion.
[this is about haikuthenews.io]
It turns out my image error thing had to do exactly with the feature I introduced yesterday (a common result, and why regression testing exists…for people who have staff to do that).
While I was futzing with the generated paths (basically what we store in the doc DB is a bunch of paths to things), I added, then removed, then I think added again an extra “/”. This breaks everything.
But we got it fixed, and now we have a nice backstory for the site itself (and you can see one of the my favorite “logo” images I generated while testing…in “compressed” form…).
Make sure and test the blue text on the link to listen to the voice! I didn’t make this thing into an mp3 player for nothing!
Update: So I continued to have some issues with the uploaded images disappearing after a bit on the page. This has to do with some clunky re-sizing code that I’ll probably pull out later. It was still including a local path in the alternate img src text, but would only show up after a screen resize/refresh (not sure exactly, it was odd on mobile). New build deployed: 0.1.2.2
Robot Pirate Ninja 