Displaying 1 to 11 from 11 results

nginxconfig.io - ⚙️ NGiИX config generator on steroids 💉

  •    HTML

NGINX is so much more than just a webserver. You already knew that, probably. A lot of features with corresponding configuration directives. You can deep dive into the NGINX documentation right now OR you can use this tool to check how NGINX works, observe how your inputs are affecting the output, generate the best config for your specific use-case (and in parallel you can still use the docs).

cachex - A powerful caching library for Elixir with support for transactions, fallbacks and expirations

  •    Elixir

All of these features are optional and are off by default so you can pick and choose those you wish to enable. For anything else, please see the documentation.

caching - ⏱ Caching library with easy-to-use API and many cache backends.

  •    PHP

Cache accelerates your application by storing data - once hardly retrieved - for future use. Documentation can be found on the website.

Kizzy - A Local Storage Utility

  •    Javascript

Kizzy is a light-weight, cross-browser, JavaScript local storage utility. It leverages the HTML5 localStorage API when available, as well as Internet Explorer's persistent XML store — wrapped up in a easy to use, memcached-like interface. When neither of these features are available (unlikely), it falls back to an in-browser object store. Furthermore, a call to 'set' will return the value, making it quite easy for assignment.

doby - TODO with expiring dates

  •    Scala

Scala implementation of expiring TODO notes. Use this library if you want to write TODO notes with an expiration date.

gocache - High performance and lightweight in-memory cache library with LRU and FIFO support as well as memory-usage-based-eviction

  •    Go

gocache is an easy-to-use, high-performance, lightweight and thread-safe (goroutine-safe) in-memory key-value cache with support for LRU and FIFO eviction policies as well as expiration, bulk operations and even persistence to file. It also supports cache entry TTL, which is both active and passive. Active expiration means that if you attempt to retrieve a cache key that has already expired, it will delete it on the spot and the behavior will be as if the cache key didn't exist. As for passive expiration, there's a background task that will take care of deleting expired keys.