# port Published articles for port. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## HKC reveals an ultra-wide curved monitor with split-screen modes for multitasking and gaming DevFeed: [HKC reveals an ultra-wide curved monitor with split-screen modes for multitasking and gaming]() Original publisher: [Read original article]() Author: Gaurav Sood Published: 2026-09-15T15:20:17Z Content type: news Language: en Sources: [Yanko Design]() Topics: [monitor](), [cpu](), [dell]() Tags: [4k](), [accessories](), [accessories-technology-curved-monitors](), [curved](), [display](), [kvm](), [monitor](), [monitors](), [multitasking](), [port](), [technology](), [ultra-wide](), [usb]() ### AI overview HKC has revealed the Tianqi 43H180C ultra-wide curved monitor, featuring a 24:9 aspect ratio, 5,760 x 2,160 resolution, and a 180 Hz refresh rate. It can operate as one large display, split into two zones, or divided into three zones. ### Source excerpt HKC debuts a 48.3-inch 4K curved monitor that splits into two or three sections for power users There are no limits as to how wide you can go with a desktop monitor, especially for power users and pro gamers. You can have... ## ESP32-C5 Pico board follows Raspberry Pi Pico form factor, ships with on-board or external antenna DevFeed: [ESP32-C5 Pico board follows Raspberry Pi Pico form factor, ships with on-board or external antenna]() Original publisher: [Read original article]() Author: Jean-Luc Aufranc (CNXSoft) Published: 2026-09-09T07:00:50Z Content type: news Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [ESP32-C5](), [Raspberry Pi](), [Espressif](), [cpu](), [RISC-V](), [SOC](), [Bluetooth](), [wifi 6](), [zigbee](), [Matter](), [Embedded Systems](), [ESP-IDF]() Tags: [802-15-4](), [arduino](), [battery](), [ble](), [bluetooth](), [bluetooth-le](), [boot](), [c-c-plus-plus](), [development-board](), [embedded-systems](), [esp-idf](), [esp32](), [esp32-c5](), [espressif](), [gpio](), [hardware](), [iot](), [matter](), [news](), [port](), [raspberry-pi](), [risc-v](), [thread](), [usb](), [waveshare](), [wifi-6](), [zigbee]() ### AI overview The Waveshare ESP32-C5 Pico is a development board in the Raspberry Pi Pico form factor. It uses an ESP32-C5-MINI-1 series module with a RISC-V processor, dual-band WiFi 6, Bluetooth LE, and 802.15.4 support for Zigbee, Thread, and Matter. The board includes GPIO headers, USB-C, buttons, LEDs, and Li-Ion battery support, with variants offering PCB or external antennas. ### Source excerpt Waveshare ESP32-C5 Pico board brings the ESP32-C5 dual-band WiFi 6, Bluetooth LE, and 802.15.4 (Zigbee/Thread) SoC to the Raspberry Pi Pico form factor. The board features an ESP32-C5-MINI-1 Series module with PCB or external antenna, two 20-pin GPIO headers, a USB-C port for power and programming, Reset and Boot buttons, and a few LEDs. It also supports Li-Ion battery charging and discharging. Waveshare ESP32-C5 Pico specifications: Wireless module - ESP32-C5-MINI-1 or ESP32-C5-MINI-1U Wireless MCU - Espressif Systems ESP32-C5HF4 CPU Single-core 32-bit RISC-V processor @ up to 240 MHz Low-power RISC-V core @ 48 MHz acting as the main processor for power-sensitive applications Memory - 384 KB SRAM on-chip Storage - 320 KB ROM, 4MB SPI flash Wireless Dual-band (2.4/5 GHz) 802.11ax WiFi 6, 802.11b/g/n WiFi 4 backward compatibility WiFi modes: Station mode, SoftAP mode, SoftAP + Station mode, and promiscuous mode Bluetooth 5.0 Low Energy (LE) with Mesh support, up [...] The post ESP32-C5 Pico board follows Raspberry Pi Pico form factor, ships with on-board or external antenna appeared first on CNX Software - Embedded Systems News. ## Rootless Podman: Preserving Source IPs DevFeed: [Rootless Podman: Preserving Source IPs]() Original publisher: [Read original article]() Author: Jan Rodak Published: 2026-09-04T14:25:02Z Content type: article Language: en Sources: [blog.podman.io]() Topics: [podman](), [Containers](), [Networks](), [Access Control](), [Logging]() Tags: [blog](), [bridge](), [container](), [containers](), [ipv4](), [ipv6](), [logging](), [networks](), [podman](), [port](), [rate-limiting](), [routing](), [tips-and-tricks]() ### AI overview This article explains how Pesto, a companion tool from the passt project, addresses Rootless Podman's inability to preserve incoming client source IPs on bridge networks. Pesto updates pasta's forwarding table so traffic reaches containers without source-address rewriting, while retaining existing port-mapping capabilities. The article also documents configuration steps, traffic flow, supported networking features, and limitations when switching from the current forwarder. ### Source excerpt Rootless Podman has a long-standing limitation reported since 2020: containers on bridge networks can't see the real source IP of incoming connections. The `rootlessport` userspace proxy rewrites the source to the container's own subnet address, breaking IP-based access control, logging, and rate limiting. Pesto, a new companion tool from the passt project solves this. Pesto [...] ## Shared Host Ephemeral Port Exhaustion Caused Overnight Job Failures DevFeed: [Shared Host Ephemeral Port Exhaustion Caused Overnight Job Failures]() Original publisher: [Read original article]() Author: PULKIT GARG Published: 2026-08-11T05:58:23Z Content type: article Language: en Sources: [Housing.com]() Topics: [ephemeral ports](), [incident](), [Kernel]() Tags: [incident](), [port](), [production-issue](), [rate-limiting](), [ruby-on-rails](), [tcp]() ### AI overview An engineering incident report explains how a neighboring bulk job exhausted the shared operating system's ephemeral TCP port pool, causing scheduled background jobs to fail until the temporary traffic pressure subsided. ### Source excerpt A neighbor's bulk job drained every ephemeral port on a shared box. Twice. Here's the one kernel setting that would have stopped it -- and the architecture that makes it a non-issue. At 1:38 AM, one of our background-job services started failing. Scheduled jobs -- the nudges and reminders we send users overnight -- began throwing an error most engineers rarely see: Errno::EADDRNOTAVAIL -- Cannot assign requested address Not "connection refused." Not "timeout." Cannot assign requested address. The machine wasn't saying the other end was down. It was saying it had run out of addresses to call from. Here's the strange part: we hadn't deployed anything. Our code was untouched for days. And by ~3 AM it healed itself, with nobody doing a thing. Two nights later, same window, it happened again. The bug wasn't in our service. It was in a service we don't own -- and don't even talk to. Act 1: A crime scene with no suspect ~7,800 job executions failed across the two nights. The first night slipped in under the alerting threshold entirely -- we only found it in the errors inbox after the fact. Everything about it was confusing: Our service hadn't changed. The internal APIs we call were all healthy. It happened in a tight window (~1:30-3:00 AM), then vanished. No human fixed it. It just... stopped. An outage that fixes itself is telling you something important: the thing that broke wasn't yours, and the pressure that caused it was temporary. Act 2: The noisy neighbor That service doesn't run on its own machine. It shares one box with about ten other apps -- a normal, cost-efficient setup. What's easy to forget is what they silently share: not just CPU and memory, but the operating system's ephemeral port pool. Quick refresher. Every time a program opens an outbound TCP connection, the OS assigns it a temporary "ephemeral" source port. That pool is finite -- by default, roughly 28,000 ports. And on a shared box, every app draws from the same pool. Ephemeral ports are an unmonitored, multi ## tcpdump: analiza tráfico de red en terminal DevFeed: [tcpdump: analiza tráfico de red en terminal]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-08-01T12:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Command-line interface](), [Linux](), [Firewall]() Tags: [firewall](), [linux](), [port](), [resolver](), [tcp](), [terminal]() ### AI overview A practical guide to using tcpdump from the terminal to capture and inspect network traffic, apply filters, interpret TCP packets, and save or reread pcap files while troubleshooting network problems. ### Source excerpt Guía práctica de tcpdump: sintaxis de filtros, lectura de paquetes y captura en archivos pcap para depurar problemas de red desde terminal. ## netcat (nc) Command in Linux, with Examples DevFeed: [netcat (nc) Command in Linux, with Examples]() Original publisher: [Read original article]() Author: Hayden James Published: 2026-08-01T10:42:27Z Content type: tutorial Language: en Sources: [Hayden James]() Topics: [networking](), [Linux](), [Tool]() Tags: [blog](), [commands](), [connectivity](), [debugging](), [examples](), [guide](), [linux](), [networking](), [port](), [security](), [server](), [sysadmins](), [tcp](), [tool](), [troubleshooting](), [udp]() ### AI overview A practical guide to the Linux nc (netcat) command, covering port testing, file transfers, banner grabbing, reverse shells, proxies, and network-service debugging over TCP and UDP. It also explains implementation differences across OpenBSD netcat, Ncat, BusyBox, and traditional netcat. ### Source excerpt The nc command (netcat) is a lightweight but surprisingly powerful networking tool for port testing, file transfers, banner grabbing, and connectivity debugging. This practical guide covers the flags and real-world usage patterns that Linux users and sysadmins actually reach for. Continue reading... ## Pure Codename One Text Editing Without Native Overlays DevFeed: [Pure Codename One Text Editing Without Native Overlays]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-07-27T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [ui](), [Code]() Tags: [component](), [formatting](), [gif](), [image](), [jpeg](), [native](), [port]() ### AI overview A new semantic port contract lets Codename One handle text painting, selection, rich editing, clipboard formats, and bidirectional layout while platform ports provide keyboard and input-method events. The opt-in path supports text composition, undo and redo, selection geometry, and multi-format clipboard content without a visible native field. ### Source excerpt A semantic port contract lets Codename One own text painting, selection, rich editing, clipboard formats, and bidirectional layout while the platform supplies keyboard and IME operations. ## Java To Native Linux App: One 5MB Binary, x64 And Arm DevFeed: [Java To Native Linux App: One 5MB Binary, x64 And Arm]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-20T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [Linux](), [Java](), [App](), [Arm](), [OpenGL]() Tags: [arm](), [glibc](), [java](), [linux](), [native](), [port]() ### AI overview This article explains Codename One's native Linux desktop port. ParparVM translates Java and Kotlin bytecode to C, which is compiled into a self-contained ELF binary without requiring a JVM on the target machine. It describes the GTK-based rendering stack, native integrations, packaging approach, dependencies, and support for x64, arm64, and musl-based Alpine Linux. ### Source excerpt The new native Linux port compiles your Java to a single self-contained ELF through ParparVM and GTK3, with no JVM on the target machine. It runs on an ancient universal glibc, supports musl for Alpine, and ships for both x64 and arm64. ## MetaStealer traffic, new DGAs and analyzing the "tracker" backdoor DGA with AI DevFeed: [MetaStealer traffic, new DGAs and analyzing the "tracker" backdoor DGA with AI]() Original publisher: [Read original article]() Author: Jason Reaves Published: 2026-06-17T21:54:01Z Content type: article Language: en Sources: [Walmart Global Tech]() Topics: [Malware](), [backdoor](), [payload](), [Python](), [Claude](), [Artificial Intelligence]() Tags: [ai](), [backdoor](), [capture](), [claude](), [claude-ai](), [infosec](), [ip](), [malware](), [payload](), [port](), [python](), [reverse-engineering]() ### AI overview The article examines new MetaStealer domain-generation algorithms and explains that its gate servers rely more on IP addresses, ports, URIs, and HTTP headers than on domains. It also analyzes RuntimeSync, a developing malware sample with RAT and backdoor capabilities, and describes using Claude.ai Sonnet 4.6 to reverse engineer its DGA and produce Python simulation code. ### Source excerpt By: Jason Reaves and Joshua Platt In this blog we simply want to highlight a few new additions to what appears to be related to MetaStealer, one is a new wordlist based DGA used by MetaStealer. We also want to highlight that MetaStealer's proxies or 'gates' don't actually care what domain gets used as it's just a config item; they simply pass on the traffic to another server. We also want to highlight a task that was seen delivered to a few bots which is related to MetaStealer but appears to still be in development. This turned out to be a piece of malware that contains RAT/backdoor functionality. Leveraging Claude.ai Sonnet 4.6 we were able to systematically guide the AI to automatically reverse engineer the DGA used in the backdoor malware and provide working python code to simulate it. MetaStealer DGA: As previously mentioned MetaStealers new DGA is based on a wordlist. Below are some recent examples: sea-vast-send.com 46bbaceb6073f196bf7737c67f5394a6465e396bbcbbac1afe5f2f866c995fd0hxxp://pestrear-lamp.xyz:443 d57e132866286f9b4227c7fb1cd77f16a461e76a3f3e71362734741aab6b9a96hxxp://anus-staylard.xyz:443 d1b88ded80f0e616362b8984334c69da1ea2f32d0828480e32978d1a710f40c5 This does not mean, however, that the older DGA is no longer in use; it remains active. The threat actor (TA) has designed their gate servers in such a way that they are largely agnostic to the domain being used. Instead, the IP address, port, URI, and HTTP headers are the more important factors. 155.117.20.75 qocyeicmusmegouw.xyz 213.139.77.254 uumcceymkuymmqou.xyz We didn't focus on this DGA though because during our investigation we stumbled on a piece of malware being actively developed by the same TA that also had a DGA. Backdoor "tracker" During the investigation, we observed a peculiar payload being delivered to several machines: an installer named RuntimeSync, example hash: 82c218357266ce314f523946bdd661cc335a120981c471e95d70af7fbd4d9141 RuntimeSyncExe: PE32+ executable (GUI) x86-64, for MS Win ## SSH Port 22: Custom Ports, Port Forwarding Security, and Production SSH Hardening DevFeed: [SSH Port 22: Custom Ports, Port Forwarding Security, and Production SSH Hardening]() Original publisher: [Read original article]() Author: info@goteleport.com (Matt Keib) Published: 2026-05-01T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Security](), [OpenSSH](), [ssh](), [Authentication](), [rate-limiting](), [Authorization](), [configuration]() Tags: [configuration](), [hardening](), [port](), [rate-limiting](), [security](), [server](), [ssh](), [tcp](), [tcp-handshake]() ### AI overview This article explains that SSH port 22 is a historical TCP entry point with no inherent cryptographic or authentication significance. It covers port forwarding risks, cryptographic and authentication configuration, rate limiting, and production SSH hardening. ### Source excerpt Learn about SSH port 22, its limitations, port forwarding security, and how to harden production SSH. ## Avoiding Port Conflicts with Multiple Storybook Instances DevFeed: [Avoiding Port Conflicts with Multiple Storybook Instances]() Original publisher: [Read original article]() Author: Nicolas Beaussart Published: 2024-12-18T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Storybook](), [Tooling](), [Development]() Tags: [inference](), [monorepo](), [nx](), [port](), [storybook](), [tooling]() ### AI overview This tutorial explains how to use Nx task inference and the createNodes feature to generate Storybook targets with unique ports for projects in a monorepo. The approach is intended to prevent port conflicts when multiple Storybook instances run in parallel, including in CI environments. ### Source excerpt Use Nx's task inference to automatically assign unique ports to Storybook instances, preventing conflicts in your monorepo. ## ERR\_PROXY\_CONNECTION\_FAILED errors with HTTP proxies DevFeed: [ERR\_PROXY\_CONNECTION\_FAILED errors with HTTP proxies]() Original publisher: [Read original article]() Author: HTTP Toolkit; Tim Perry Published: 2024-12-11T17:00:00Z Content type: tutorial Language: en Sources: [HTTP Toolkit]() Topics: [HTTP](), [browser](), [Security](), [debug](), [TLS (Transport Layer Security)](), [cURL](), [Postman]() Tags: [authentication](), [browser](), [chrome](), [curl](), [debugging](), [errors](), [http](), [issue](), [port](), [postman](), [protection](), [proxy](), [server](), [tcp](), [tls](), [tools]() ### AI overview This tutorial explains how to diagnose ERR_PROXY_CONNECTION_FAILED when using a local debugging proxy with Chrome or similar applications. It covers incorrect connection details, unreachable proxies, and antivirus software that intercepts local proxy traffic and rejects the proxy's TLS certificate. ### Source excerpt If you're using a local debugging proxy tool like HTTP Toolkit, you might run into the dreaded ERR_PROXY_CONNECTION_FAILED error in Chrome and other similar apps. This can be a very frustrating and unhelpful error! There's only a few possible causes though, and it's usually easy to fix. The Simple Case The simplest explanation is exactly what it says: the browser can't connect to your proxy. In the simple case this may be caused by a basic connection issue: you have the address, port or some authentication details wrong, or the details are correct but the proxy is just not reachable on your connection, and so the browser can't talk to it. The easiest way to confirm this is to try connecting to the details directly using an HTTP client tool like curl, Postman, or the HTTP Toolkit Send page, to manually check if the server is listening on the port you expect. If you see a TCP error then the details are wrong, but if you see any kind of HTTP error or similar then you know that the server does exist and it's reachable with the given details. If the failure comes from a browser intercepted by a tool like HTTP Toolkit though, where intercepted clients are preconfigured & launched for you, this is not what's happening - the server is definitely reachable (it's running locally) and the config is correct (it's been done automatically). Instead, this might be caused by something more complicated... Beyond the Simple Case If you know the settings are correct, and you know the proxy is reachable, what could cause this ERR_PROXY_CONNECTION_FAILED error? Once you're ruled out basic connection issues, the most likely cause is antivirus software on your computer that is intercepting your connections. This is becoming a common feature of some antivirus & security software, most notably ESET. It's not directly related to viruses at all, but is a separate security feature that's often enabled automatically for additional protection. What happens in this case is that your browser is tryi ## Zero-day RCE vulnerability found in CUPS - Common UNIX Printing System DevFeed: [Zero-day RCE vulnerability found in CUPS - Common UNIX Printing System]() Original publisher: [Read original article]() Author: Jim Armstrong Published: 2024-09-27T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Unix](), [Vulnerabilities](), [Security](), [Exploit](), [Linux](), [Containers](), [C](), [C++]() Tags: [attacks](), [awareness](), [blog](), [c](), [c-plus-plus](), [container-security](), [containers](), [cve](), [cves](), [dns](), [docker](), [engineering](), [executive](), [interest](), [linux](), [network](), [open-source-security](), [pmm](), [port](), [rce](), [remote-code-execution](), [scm](), [security](), [snyk](), [snyk-apprisk](), [snyk-container](), [snyk-open-source](), [vulnerabilities](), [vulnerability]() ### AI overview The article reports several vulnerabilities in CUPS, the Common UNIX Printing System, including unauthenticated remote code execution. It discusses four associated CVEs, a potentially high CVSS score, affected UNIX and Linux packages, exploitability conditions involving UDP port 631 or DNS-SD, and remediation assessment using Snyk Open Source and Snyk Container. ### Source excerpt Security researcher evilsocket.net (Simone Margaritelli) published information about several vulnerabilities in CUPS that allow for remote code execution (RCE) ## Attacking UNIX Systems via CUPS, Part I DevFeed: [Attacking UNIX Systems via CUPS, Part I]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2024-09-26T14:51:30Z Content type: article Language: en Sources: [evilsocket]() Topics: [vulnerability](), [Security](), [Unix](), [Exploit](), [gnu linux](), [systems]() Tags: [bugs](), [cups](), [cups-browsed](), [cve](), [cve-2024-47076](), [cve-2024-47175](), [cve-2024-47176](), [cve-2024-47177](), [cybersecurity](), [disclosure](), [exploit](), [gnu-linux](), [hacking](), [ipp](), [lan](), [linux-security](), [mdns](), [no-authentication](), [port](), [print-services](), [printer](), [printers](), [printing](), [rce](), [responsible-disclosure](), [security](), [udp](), [unauthenticated-access](), [unix](), [vulnerability-research](), [zeroconf]() ### AI overview A security writeup describes multiple vulnerabilities in CUPS components affecting GNU/Linux and other UNIX systems. It reports that remote unauthenticated attackers may replace printer IPP URLs and trigger arbitrary command execution when a print job starts, with attacks possible over the public internet or via spoofed LAN advertisements. ### Source excerpt Hello friends, this is the first of two, possibly three (if and when I have time to finish the Windows research) writeups. We will start ## Building Applications on NuttX: Understanding the Build System DevFeed: [Building Applications on NuttX: Understanding the Build System]() Original publisher: [Read original article]() Author: John Lee Published: 2024-09-16T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [NuttX](), [Operating system](), [Embedded Software Dev](), [systems]() Tags: [apache](), [applications](), [blog](), [build](), [esp32](), [how-to](), [linux](), [nuttx](), [port](), [posix](), [tutorial]() ### AI overview This article explains how to integrate and build applications in NuttX, including applications ported from other POSIX-compliant systems. It describes the separation between applications and the NuttX kernel, the role of POSIX-compatible APIs, and the NuttX build system and application repository. ### Source excerpt This article shows how to port and build an application form other Posix-compliant systems to NuttX. ## Use Github with SSH on port 443 DevFeed: [Use Github with SSH on port 443]() Original publisher: [Read original article]() Author: Tom Published: 2023-12-26T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [GitHub](), [OpenSSH](), [Firewall]() Tags: [blocking](), [bypass-firewall-github](), [firewall](), [github](), [github-repository-access](), [github-ssh-port-443](), [how-to](), [https](), [linux](), [port](), [repository](), [ssh](), [ssh-configuration-github](), [ssh-github-access](), [timeout](), [wifi]() ### AI overview This tutorial explains how to use GitHub over SSH on port 443 when standard SSH access is blocked or times out, such as on hotel or public Wi-Fi networks. It describes configuring the connection to simulate HTTPS traffic so repositories can still be cloned, pulled, and pushed over SSH. ### Source excerpt Learn how to use GitHub with SSH on port 443 to bypass firewall restrictions and ensure seamless repository access. ## Android emulator access to local server DevFeed: [Android emulator access to local server]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2023-01-25T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [Android](), [Emulator](), [Server](), [adb](), [Network](), [Development]() Tags: [adb](), [android](), [blogs](), [command-line](), [devices](), [emulator](), [ip](), [localhost](), [network](), [port](), [react-native](), [server]() ### AI overview This tutorial explains how to connect an Android app running in an emulator to a development server on a computer's localhost. It presents using the computer's IP address, the emulator loopback alias, editing the emulator's hosts file, and ADB reverse as possible approaches. ### Source excerpt How can you connect your app on an Android emulator to a development server running on the localhost of your computer? The problem # Since Android emulators create their own virtual network, they cannot access devices on your local network. ## Serving static files with Ktor DevFeed: [Serving static files with Ktor]() Original publisher: [Read original article]() Author: Marc Plano-Lesay Published: 2022-09-03T09:00:00Z Content type: tutorial Language: en Sources: [Marc Plano-Lesay]() Topics: [servers](), [Routing (disambiguation)](), [web applications](), [Web Development]() Tags: [files](), [handler](), [html](), [http](), [kotlin](), [ktor](), [plugin](), [port](), [route](), [routing](), [web]() ### AI overview This tutorial explains how to serve static files and nested index.html files with Ktor. It replaces the default static-file handling with a custom route that resolves files and directory fallbacks, then uses a Ktor plugin to handle trailing slashes. ### Source excerpt Serving static files with Ktor for a static website seems easy enough: fun main() { embeddedServer(Netty, port = 8080) { routing { static { files("static-data") } } }.start(wait = true) } Done? Not quite. Opening http://localhost:8080 will only get you a 404, even if you have an index.html file in the static-data folder. You have to let Ktor know you want to opt-in serving a default file. Let's try again (omitting anything outside the static block): static { files("static-data") default("static-data/index.html") } Surely now this works? Well, kind of. The root folder will have a default index.html, but sadly if you have any sub-folders with index.html files inside, they won't be served by default - that default() function only works for the top-level folder. Let's work around that. Let's store our static-data directory into a File variable, replace the files function call by our own extension. Note that this extension will handle the fallback to index.html in all cases, so we can also remove the call to default(): val staticData = File("/path/to/static-data") static { filesWithDefaultIndex(staticData) } fun Route.filesWithDefaultIndex(dir: File) { } In there, we'll need a get handler: fun Route.filesWithDefaultIndex(dir: File) { get("{static_path...}") {} } This will catch anything inside the static path, and let us access the requested path through call.parameters.getAll("static_path"). This gets us a list of URL segments that we need to join with File.separator: val relativePath = call.parameters .getAll("static_path") ?.joinToString(File.separator) ?: return@get Now, we have three options: The requested path points to an existing file. Great! We can just return it. The requested path points to a folder. If there's an index.html file in there, let's serve it. In any other case (the requested path doesn't exist, or points to a folder without an index.html file), we let Ktor handle that (most likely returning a 404). We can easily access the corresponding local file ## Running Multiple Rails Apps Concurrently with Foreman and Procfile.dev DevFeed: [Running Multiple Rails Apps Concurrently with Foreman and Procfile.dev]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2022-07-18T13:15:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Rails](), [Environment Variables](), [Development](), [Yarn](), [Processes](), [Unix]() Tags: [dev](), [environment-variables](), [foreman](), [node](), [port](), [process](), [procfile](), [rails](), [run](), [unix]() ### AI overview A tutorial on running multiple Rails applications concurrently with Foreman and Procfile.dev. It explains how port conflicts can come from Node running behind Yarn and recommends assigning Yarn a port so Node inherits it through the environment. ### Source excerpt Pizza courtesy of Pizza for Ukraine! Donate Now to Pizza for Ukraine As I've said, I build a lot of side projects and I really, really like the model of having: ALL MY APPS RUNNING CONCURRENTLY I may be a scattered, distracted developer trying to do too damn much but that's my damn right. And I have 64 gigs of RAM so why shouldn't I be this way. What I want is to be able to switch from app to app and make changes. This is important because some apps provide APIs which other apps rely on and having to figure out what thing is on what port, etc, is just plain distracting. Foreman and Procfile.dev is a way around this but there's a major hitch in your getalong (as my Texas wife might say). Here's a sample Procfile.dev for an app I'm building called Cartazzi which makes a developer's life easier: web: bin/rails server -p 5000 css: yarn build:css --watch js: yarn build --reload # docker: docker-compose up And here's a Profile.dev for another application called Poolwizard which helps you maintain your swimming pool: #web: bin/rails server -p $PORT web: bin/rails server -p 5700 css: yarn build:css --watch js: yarn build --reload # docker: docker-compose up worker: bundle exec sidekiq If you run Cartazzi and Poolwizard together then you're going to get crashes and here's the error: ❯ foreman start -f Procfile.dev 09:11:53 web.1 | started with pid 72877 09:11:53 css.1 | started with pid 72878 09:11:53 js.1 | started with pid 72879 09:11:53 worker.1 | started with pid 72881 09:11:53 js.1 | yarn run v1.22.5 09:11:53 css.1 | yarn run v1.22.5 09:11:53 css.1 | $ tailwindcss --postcss -i ./app/assets/stylesheets/application.tailwind.css -o ./app/assets/builds/application.css --watch 09:11:53 js.1 | $ node esbuild.config.js --reload 09:11:54 js.1 | node:events:371 09:11:54 js.1 | throw er; // Unhandled 'error' event 09:11:54 js.1 | ^ 09:11:54 js.1 | 09:11:54 js.1 | Error: listen EADDRINUSE: address already in use :::5200 09:11:54 js.1 | at Server.setupListenHandle [as _listen2] (no ## Card Soccer DevFeed: [Card Soccer]() Original publisher: [Read original article]() Published: 2022-07-10T00:00:00Z Content type: tutorial Language: en Sources: [Vasya Drobushkov]() Topics: [Kotlin Multiplatform](), [multiplatform](), [Compose](), [ui](), [compose-for-desktop](), [Web]() Tags: [ai](), [compose](), [compose-ui](), [desktop](), [game](), [how-to](), [kotlin](), [kotlin-multiplatform](), [multiplatform](), [port](), [strategies](), [web]() ### AI overview Card Soccer is a turn-based card game against an AI opponent. Players move a card-based ball through rows by matching its value or suit, using passes or shots to score goals. The author describes developing desktop and web versions with Kotlin Multiplatform and Jetpack Compose UI. ### Source excerpt How to play The goal of the game is to win AI opponent by scoring more goals. The game is turn based. On your turn you should move the "ball" (card opened from your deck) to opponents goal. You start from the row that is close to your goal: you should select a card in a row and if it matches by value or suite - proceed to the next row up until the opponent's goal. If there is no match - your turn is over. You can select opened and closed cards. If the whole row is opened - you can skip it and procced to the next one. You score when your "ball" matches opponent goal. ## SSH Client Config File Example DevFeed: [SSH Client Config File Example]() Original publisher: [Read original article]() Author: info@goteleport.com (Ben O'donnell) Published: 2022-01-06T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [OpenSSH](), [configuration](), [Authentication](), [Command-line interface]() Tags: [authentication](), [configuration](), [how-to](), [port](), [requirements](), [ssh]() ### AI overview This tutorial explains how SSH client configuration files simplify connections to remote servers by storing reusable host settings and connection parameters. It also introduces Teleport's tsh client for identity-based server access and visibility. ### Source excerpt This blog post will show you how to use SSH client config files to simplify server management. ## Using TLS Extensions to Route Traffic and Reduce Port Requirements in Teleport DevFeed: [Using TLS Extensions to Route Traffic and Reduce Port Requirements in Teleport]() Original publisher: [Read original article]() Author: ben@goteleport.com (Ben Arent) Published: 2021-12-21T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [TLS (Transport Layer Security)](), [TLS handshake](), [Routing (disambiguation)](), [SSL](), [Server]() Tags: [https](), [port](), [route](), [security](), [ssl](), [tls](), [tls-handshake]() ### AI overview This tutorial explains how Teleport uses TLS extensions, including ALPN and SNI, to route traffic more efficiently and reduce the number of required open ports. It also distinguishes the TLS protocol from the X.509 certificates used with it. ### Source excerpt How to leverage TLS extensions to more efficiently route traffic and reduce port requirements in Teleport. ## Meet keepalived - High Availability and Load Balancing in One DevFeed: [Meet keepalived - High Availability and Load Balancing in One]() Original publisher: [Read original article]() Author: Techno Tim Published: 2021-12-11T13:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Availability](), [Protocol (disambiguation)](), [configuration](), [nginx](), [Docker](), [Pi-hole]() Tags: [config](), [configuration](), [docker](), [gateway](), [high-availability](), [homelab](), [install](), [load-balancing](), [nginx](), [port](), [protocol](), [route](), [services](), [tutorial](), [video]() ### AI overview A video tutorial explains how keepalived uses VRRP and a virtual IP to provide high availability and failover across hosts. It demonstrates configuration, testing, service management, and an advanced load-balancing setup, including a Pi-hole use case. ### Source excerpt In my quest to make my services highly available I decided to use keepalived.keepalived is a framework for both load balancing and high availability that implements VRRP.This is a protocol that you see on some routers and has been implemented in keepalived. It creates a Virtual IP (or VIP, or floating IP) that acts as a gateway to route traffic to all participating hosts.This VIP that can provi... ## How to run JMX monitoring in Docker image? DevFeed: [How to run JMX monitoring in Docker image?]() Original publisher: [Read original article]() Author: Tom Published: 2021-02-19T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Docker](), [Monitoring](), [Java](), [configuration](), [container]() Tags: [configuration](), [container](), [docker](), [docker-java-monitoring](), [docker-jmx-configuration](), [how-to](), [java](), [java-jmx-docker](), [jconsole-docker](), [jmx-monitoring-docker](), [mapping](), [monitoring](), [port](), [server](), [variable](), [visualvm-docker]() ### AI overview A tutorial on configuring JMX monitoring for an application running in a Docker container. It explains setting the RMI and JMX ports, configuring the hostname used for connections, mapping the ports, and connecting with VisualVM or Jconsole. ### Source excerpt Learn how to run JMX monitoring in a Docker image, including the necessary Java parameters and configuration for connecting to JMX consoles like VisualVM or Jconsole. [Next page]()