Search Results for "can="

...You can use Guardian tokens to authenticate web endpoints (Plug/Phoenix/X), channels/Sockets (Phoenix - optional), and any other system you can imagine. If you can attach an authentication token you can authenticate it.

...The easiest way to use Pow with Phoenix is to use a :otp_app in function calls and set the app environment configuration. It will keep a persistent fallback configuration that you configure in one place. Pow ships with a session plug module. You can easily switch it out with a different one. Pow is extremely modular and fully customizable. As your platform scales, each moving part can be modified or replaced ad-hoc. Several extensions are included in Pow so you with no effort can add secure features to your app.

The operating system and all related software that runs on FarmBot's Raspberry Pi. The FarmBot OS release page has moved to my.farm.bot/os. Old versions of FarmBot OS can still be found. Get configured over WiFi, mitigating the need to plug in a mouse, keyboard, or screen. Communicate with the web application over WiFi or ethernet so that it can synchronize (download) sequences, regimens, farm designs, events, and more; upload logs and sensor data; and accept real-time commands. Communicate with the Farmduino to send G and F commands and receive sensor and encoder data. ...

...The library’s helpers make it straightforward to add registration and login flows that resist brute-force and side-channel attacks. Migration paths and checks are included so you can upgrade algorithms or work factors over time without breaking existing credentials. Its focus on practical ergonomics—clear APIs, sensible defaults, and good docs—has made it the de facto choice for password handling in Elixir. By centralizing hashing concerns, Comeonin helps teams avoid subtle security mistakes while keeping authentication code terse and testable.

...It does not authenticate each request, that's up to your application. You could issue a token or put the result into a session for the needs of your application. Libraries like Guardian can help you with that aspect of authentication. Strategies implement the two phases and then may allow the request to flow through to your downstream plugs. Implementing the request and callback phases is optional depending on the strategies requirements. If a strategy does not redirect, the request will be decorated with Ueberauth information.

libcluster provides automatic cluster formation and node discovery for Erlang/Elixir applications, removing the manual steps typically required to connect distributed nodes. It ships with multiple pluggable strategies—such as DNS polling, Kubernetes integration, EC2 metadata/tag discovery, UDP gossip, and EPMD helpers—so you can adapt clustering to your runtime environment. The library supervises a topology process that continually discovers peers and joins or prunes nodes as they become available or disappear. Its design embraces OTP principles: strategies implement a behavior, can be composed, and run under supervision for resilience. libcluster also emits events on nodeup/nodedown, allowing applications to react (for example, rebalance work or update registries) when membership changes. ...

Swarm is a distributed process registry for Elixir/Erlang that lets you register and discover processes across a cluster as if they were on a single node. It focuses on automatic distribution and rebalancing, so when nodes join or leave, Swarm can move work and hand off state to keep the system stable. The library offers a global name registry, conflict resolution for name ownership, and hooks for reacting to membership changes. Its design embraces OTP principles, using supervised processes and fault-tolerant messaging to keep the registry resilient under failures. Developers can co-locate Swarm with their existing supervision trees to scale workers horizontally without writing custom clustering code. ...

...Just 3 lines of code to add pages/metrics for your library when users have :wobserver installed. Wobserver does not support being included directly from GitHub. The required assets are not included in the repo in build form and can therefore not be used. It is possible to build locally and use the generated package. (See Build manually for more information.) To view the web interface just enter http://<host>[:<port>]/ in the browser and it should show the :wobserver interface. The default port is 4001, but the port can be changed in the configuration.