Updates and recent posts about AWX..

Posts
Description

Activity

@goutham-annem started using tool Azure Kubernetes Service (AKS) , 3 days, 23 hours ago.

Activity

@goutham-annem started using tool AWS EKS , 3 days, 23 hours ago.

Activity

@goutham-annem started using tool Amazon Web Services , 3 days, 23 hours ago.

Activity

@goutham-annem started using tool Amazon ECS , 3 days, 23 hours ago.

Activity

@eon01 gave 🐾 to The unwritten laws of software engineering , 4 days, 2 hours ago.

Link

@varbear shared a link, 4 days, 5 hours ago

FAUN.dev()

Build and Deploy a Remote MCP Server to GKE in 30 Minutes

Google walks you through shipping a remoteMCP serveronGKE AutopilotusingFastMCPandstreamable-http, swapping localstdiofor shared HTTP endpoints. The clever bit: theGateway APIhandles managed SSL plusCLIENT_IP session affinity, so one centralized server beats everyone running redundant local copies... read more

Link

@varbear shared a link, 4 days, 5 hours ago

FAUN.dev()

The unwritten laws of software engineering

- Always related - first rollback, then debug. - Backups aren’t real until restored. - You’ll hate yourself for bad logs. - ALWAYS have a rollback plan. - Every external dependency will fail. - If there's risk, use the “4 eyes” rule. - Nothing lasts like a temporary fix... read more

Link

@varbear shared a link, 4 days, 5 hours ago

FAUN.dev()

How building an HTML-first site doubled our users overnight

Building HTML-first forms using Astro instead of React dramatically increased completion rates and sustainability, highlighting the effectiveness of lightweight, accessible web components for all users, regardless of browser or connectivity... read more

Link

@varbear shared a link, 4 days, 5 hours ago

FAUN.dev()

Everything a Senior Engineer Needs to Know About What's Inside an LLM

The shift from RNNs totransformerssolved sequential bottlenecks and long-range decay issues withself-attention. Transformers use encoding, decoding, and tokenization to process sequences efficiently and accurately. This evolution led to models like GPT, which excel at tasks with minimal fine-tuning .. read more

Link

@varbear shared a link, 4 days, 5 hours ago

FAUN.dev()

Google hits 50% IPv6

The 50% IPv6 milestone is real, but adoption differs by country. Analysts who report lower figures use population-weighted sampling, while their per-country adoption rates match the higher estimate... read more

AWX is the open source, community supported upstream project for Red Hat Ansible Automation Platform, formerly known as Ansible Tower. It gives teams a web based interface, a full REST API, and a distributed task engine on top of Ansible, turning command line playbook runs into a managed, auditable automation service.

The project began at AnsibleWorks as the commercial Ansible Tower product, and after Red Hat acquired Ansible, it open sourced the codebase as AWX in September 2017, positioning it as the development ground where new features land before they are hardened into the supported Automation Platform controller. With AWX, you organize automation around projects (synced from Git or other source control), inventories (static or dynamically pulled from cloud providers), credentials (stored encrypted and injected at runtime), and job templates that tie a playbook to its inventory and credentials. On top of that, it adds role based access control, a visual dashboard, job scheduling, workflow chaining, webhooks, and real time job output, so multiple teams can run, track, and delegate automation without sharing SSH keys or sitting at a terminal.

Modern AWX runs on Kubernetes or OpenShift through the AWX Operator, which manages installation, upgrades, and scaling declaratively, reflecting its shift from a single host application to a cloud native, container based platform. Because it is the upstream of a paid product, AWX moves fast and ships frequently, which makes it ideal for labs, learning, and self managed deployments, though teams needing formal support and long term stability typically run the downstream Automation Platform instead.