>> This site has been online since 2004, previously entirely static (generated by a Perl script). It outgrew that some years ago and I've finally got around to rewriting it in bleeding-edge Rails. Source available on GitLab.
It's an useful resource, I had similar, albeit just a tiny fraction, collection of colors I can pull out of my sleeve when asked for advice, but... why does this page has to be served from "bleeding edge server application" instead of being served as static html files?
The most popular page is the "most popular gradients" page, and previously I had to grep the server Apache logs, insert into a DB, dump and copy the DB locally, regenerate the whole site and upload. Took an hour, I did that once a week or so. Now it's all done on the site without my intervention a few seconds after every download.
And it's bleeding edge because I wanted to get up-to date on recent Rails improvements :-)
Thanks for posting! I'm doing this: https://palettewb.com/
>> This site has been online since 2004, previously entirely static (generated by a Perl script). It outgrew that some years ago and I've finally got around to rewriting it in bleeding-edge Rails. Source available on GitLab.
It's an useful resource, I had similar, albeit just a tiny fraction, collection of colors I can pull out of my sleeve when asked for advice, but... why does this page has to be served from "bleeding edge server application" instead of being served as static html files?
The most popular page is the "most popular gradients" page, and previously I had to grep the server Apache logs, insert into a DB, dump and copy the DB locally, regenerate the whole site and upload. Took an hour, I did that once a week or so. Now it's all done on the site without my intervention a few seconds after every download.
And it's bleeding edge because I wanted to get up-to date on recent Rails improvements :-)
[author BTW]
Earlier as a ShowHN:
https://news.ycombinator.com/item?id=47455410
This can be a great help to me when I’m working on a design.