21–30 of 83 posts
FYI, there is a name clash with Caffeine, a Mac OS menu bar app that keeps the screen awake: https://intelliscapesolutions.com/apps/caffeine . But I guess this is expected with a name like this, and the scopes of the projects are clearly different, so this should be relatively harmless.
Feature request: supply .json file via command line to pre-load data into the in-memory database. Taking it even further; how about persisting the data in the file? Sometimes your prototype will need some pre-added data so I think this might be useful.
currently there are two implementation for the database "behind": in memory or with postgres, both with zero config (except for starting an instance of postgres, in the second case!). it can be easily extended to use files as persistence, good idea :) regarding the pre-population, you can just make a quick script with curl that will add some data after you run the service. any thought?
A few requests should randomly fail to force the developer to think about handling errors. :)
While not a security risk if done locally, why not just use a where string builder to generate the $ values and a variadic as the input? It's about the same amount of work.
Why do people overload common nouns so much when naming a project? A name should confer its essence.
My next application is going to be called Toreutics which is going to break this word for every person that actually uses it.
Kinda like breaking the word Meta. Which I suppose is actually aimed at making things difficult to search for.