Search Results for "me"

...Built-in backends to store sessions in cookies or the filesystem. Flash messages: session values that last until read. A convenient way to switch session persistency (aka "remember me") and set other attributes. Mechanism to rotate authentication and encryption keys. Multiple sessions per request, even using different backends. Interfaces and infrastructure for custom session backends: sessions from different stores can be retrieved and batch-saved using a common API. First we initialize a session store calling NewCookieStore() and passing a secret key used to authenticate the session.

...It has a Jsonnet configuration file that aims to be simpler to write and maintain than using the Gmail web interface, to categorize, label, archive and manage your inbox automatically. If you use Gmail and have to maintain (like me) a lot of filters (to apply labels, get rid of spam or categorize your emails), then you probably have (like me) a very long list of messy filters. At a certain point one of your messages got mislabled and you try to understand why. You scroll through that horrible mess of filters, you wish you could find and replace stuff, test the changes on your filters before applying them, refactor some filters together... in a way treat them like you treat your code. ...

nFPM is a simple, 0-dependencies, deb, rpm, apk, and Arch Linux packager. While fpm is great, for me, it is a bummer that it depends on ruby, tar and other software. I wanted something that could be used as a binary and/or as a library and that was really simple. So I decided to create nFPM: a simpler, 0-dependency, as-little-assumptions-as-possible alternative to fpm. This is a subtle way of saying it won't have all features, nor all formats that fpm has: it is supposed to be simpler. ...

...Dependencies are immutable blobs of code and associated metadata that come from Github. They live in storage that Athens controls. You probably already know what “immutable” means, but let me just point it out again because it’s really important for this whole system. When folks change their packages, iterate, experiment, or whatever else, code on Athens won’t change.

...Extend them however you need with Oso’s declarative policy language, Polar. Filter: Go beyond yes/no authorization questions. Implement authorization over collections too - e.g., “Show me only the records that Juno can see.” Test: Write unit tests over your authorization logic now that you have a single interface for it. Use the debugger or tracing to track down unexpected behavior. Oso lets you write policies to control who can do what in your app. Select different policies below to see how they change the permissions in the sample app on the right. ...