How to Migrate Java App Deployment from RPM to TAR Using Gradle and Ansible

·2 views

Switching from RPM-based distribution to .tar.gz archives removes dependency on host-level package managers like yum or dnf, simplifying build pipelines. On the Gradle side, RPM plugins and tasks are replaced with the native distribution plugin or a custom Tar task, and Artifactory publishing is updated to push the archive and a manifest file. For Ansible deployment, yum and dnf installation tasks are swapped out for the built-in unarchive module, which downloads and unpacks the tarball directly onto the target host. Unlike RPM, tar-based deployments do not automatically manage file permissions, so ownership and access modes must be explicitly set in Ansible tasks. Versioned extraction directories are also recommended to handle rollbacks cleanly, since tar does not update a package database.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

OpenAI's macOS Computer History Feature Logs Keystrokes in Unencrypted Plaintext

OpenAI has introduced a 'Computer History' feature for its ChatGPT macOS app that tracks user clicks, keystrokes, and application switches to build a searchable activity timeline. The feature uses macOS accessibility tools to give ChatGPT persistent context about a user's work, enabling the agent to act more informatively on their behalf. However, the activity logs are stored locally as unencrypted plaintext Markdown files, meaning any process running under the same user account could potentially read them. While the feature is opt-in, supports app blacklisting, and skips private browsing activity, security researchers warn the unencrypted format poses real risks given the sensitive data — such as API keys, credentials, and private messages — that may pass through a user's screen. Experts also flag an expanded prompt injection risk, as malicious content in tracked apps like Slack could theoretically influence future AI-assisted actions.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How a Daylight Saving Time Bug Caused Biweekly Production Failures

A software developer encountered a recurring production bug where a report generation job failed every other Thursday at 2 AM, but worked flawlessly in local testing. Investigation revealed the root cause was Python's naive datetime object being shifted across a daylight saving time boundary on a US/Eastern-timezone server. Because the datetime lacked timezone awareness, adding 14 days during a DST transition caused the resulting due date to be off by one hour, breaking compatibility with downstream services. Using a structured debugging framework of Observe, Hypothesize, Test, and Learn, the developer isolated the issue by forcing the job to run with a known DST transition date and logging raw datetime values. The fix involved treating all datetime objects as timezone-aware from the point they entered the system, which eliminated the intermittent failures entirely.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

GrapheneOS Rumored to Expand to High-End Motorola Phones by 2027

GrapheneOS, a privacy-focused and security-hardened Android-based operating system, is rumored to become available on high-end Motorola smartphones by 2027. Currently, the OS is primarily supported on Google Pixel devices, where it is known for features such as app sandboxing and granular permission controls. Motorola's flagship hardware is noted for its durability and strong battery life, which proponents say could complement GrapheneOS's performance-oriented design. The potential pairing has generated interest among privacy-conscious users who seek a balance between security and everyday usability. No official confirmation from either GrapheneOS developers or Motorola has been reported at this time.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Engineer Replaces kube-proxy with eBPF in Homelab Cluster, Loses Monitoring for 6 Hours

A software engineer upgraded Cilium from version 1.15 to 1.16 on a four-node bare-metal homelab cluster running Talos Linux, enabling full eBPF-based kube-proxy replacement by setting a single configuration flag. The change appeared successful at first — all pods remained running and the cluster showed healthy status — but at 2:47 AM an alert revealed that the SIEM had received zero network flow or Kubernetes audit logs since the upgrade. The root cause was that the eBPF datapath bypasses the iptables and netfilter hooks that the security monitoring stack relied on to capture packet-level data. The engineer had migrated away from kube-proxy's iptables rules, which, while less scalable, fed the observability pipeline that the SIEM depended on. The incident highlighted a critical gap in Cilium's documentation: replacing kube-proxy with eBPF silently removes the datapath layer that many security and monitoring tools assume will always be present.

0 comments Read more at DEV Community