Posts

ollama on ubuntu 24.04

On Ubuntu 24.04, Ollama runs as a background systemd service by default, which means setting environment variables in your regular ~/.bashrc will not apply to Ollama unless you configure them inside its service override file. Step 1: Configure Ollama on Ubuntu 24.04 Run this command in your terminal to open the systemd override editor for Ollama: bash sudo systemctl edit ollama.service Wees voorzichtig met code. Add the following lines inside the [Service] section (at the top of the file, above the existing comments): ini [Service] Environment="OLLAMA_FLASH_ATTENTION=1" Environment="OLLAMA_KV_CACHE_TYPE=q8_0" Environment="OLLAMA_CONTEXT_LENGTH=16384" Wees voorzichtig met code. Save and exit the editor (Ctrl+O, Enter, Ctrl+X if using nano), then reload and restart the Ollama service: bash sudo systemctl daemon-reload sudo systemctl restart ollama Wees voorzichtig met code. Step 2: Verify It Fits 100% in Your RTX 3060 VRAM 1. Trigger a prompt from your IDE e...

how to pair this app-to-app flow with a Viva Wallet Webhook (Transaction Payment Created) sent from Viva’s servers directly to your backend server to securely finalize the order processing?

  Pairing a local browser-to-app checkout with an asynchronous backend webhook is the industry gold standard for payment security. It bridges the gap between a fragile client-side environment (the mobile browser, which can be closed mid-transaction) and a secure server-side database. The synchronization pattern relies on a unique identifier that ties the in-app terminal payment payload to your specific order record. The Secure Architecture [ Mobile Browser ] --(1. Deep Link)--> [ Viva.com Terminal App ] | | (2. Physical Tap) (4. Returns App-to-Browser) [ Viva Servers ] | | v v (3. Asynchronous HTTP POST) [ Frontend Callback ] [ Your Backend Server ] (Polling/Waiting) <--(5. Finalized)-- (Verifies & Saves Order) Step 1: Generate an Order Tracking ID Before launching the vivapayclient:// deep link,...