OpenSource Showcase CLI Auto-Generates GitHub Contribution Portfolios

·2 views

A developer has built OpenSource Showcase, a command-line tool that helps developers curate and display their merged GitHub pull requests as a professional portfolio. The tool is launched with a single command, 'npx opensource-showcase', which authenticates with GitHub, retrieves merged pull requests, and lets users select contributions to highlight. It automatically creates a dedicated '.opensource' repository containing a portfolio website, a formatted README, and a machine-readable contributions.json file. The project addresses a common pain point where open-source work is scattered across multiple repositories, making it hard to present impact quickly to recruiters or maintainers. The generated site is also prepared for deployment via GitHub Pages, removing the need for manual portfolio upkeep.

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)

Load Balancing Explained: Algorithms, Layers, and the Single Point of Failure Risk

Load balancers sit between clients and backend servers, distributing incoming traffic so no single server is overwhelmed — but the choice of algorithm matters significantly. Common strategies include round robin, least connections, and IP hash, each suited to different traffic patterns and statefulness requirements. Load balancers also operate at either Layer 4, routing by IP and port for speed, or Layer 7, inspecting request content for smarter but costlier decisions. Built-in health checks allow load balancers to detect and stop routing traffic to failed servers, effectively doubling as a monitoring layer. However, a single load balancer itself becomes a critical point of failure, which is why production systems typically run multiple load balancer instances behind DNS round robin for redundancy.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to properly enable hibernation on Ubuntu 24.04 using a swap file

Ubuntu 24.04 LTS introduced silent changes to its polkit permissions system, breaking most existing hibernation tutorials that rely on the outdated .pkla file format. The correct setup requires passing resume and resume_offset parameters directly through GRUB, pointing to the swap file's UUID and physical offset on disk. A common initramfs warning is triggered when a separate resume config file is created unnecessarily, as the kernel already reads the required parameters from GRUB. Additionally, legacy init scripts that attempt to manually write to kernel power management interfaces will cause a 'write error: invalid argument' failure and should be removed. The guide also notes that polkit rules must now be written in JavaScript .rules format, as the old .pkla format is silently ignored on Ubuntu 24.04.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How a Next.js Rebuild Modernised a 75-Year-Old Lahore Law Firm's Website

Ansari Law Associates, a Lahore-based legal consultancy with 75 years of history, had its website rebuilt using Next.js to better serve overseas clients and reflect the firm's established reputation. The new site uses static generation to pre-render pages at build time, delivering fast load speeds while eliminating security vulnerabilities common in WordPress-based legal sites. Structured intake forms were developed to capture key details such as practice area, client jurisdiction, and preferred contact method, helping partners receive pre-screened inquiries rather than vague messages. The site also incorporates bilingual support with English and Urdu locale routing, allowing language variants to coexist without duplicating the codebase. Design choices including serif typography, generous whitespace, and a restrained colour palette were made to digitally mirror the authoritative atmosphere of a long-established law office.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Set Up a Vite-Powered WordPress Theme with Sass and Hot Reloading

Developers can modernize WordPress theme development by integrating Vite, a fast front-end build tool, to handle Sass compilation, JavaScript modules, and hashed production assets. The setup involves configuring a vite.config.js file with manifest generation enabled, so WordPress can dynamically resolve hashed filenames from the dist folder at runtime. A custom PHP helper function checks whether the Vite dev server is running locally, allowing WordPress to load assets directly from it during development for a faster workflow. For production, Vite compiles and outputs optimized files into a dist directory, which WordPress enqueues using filenames read from Vite's generated manifest.json. The approach is compatible with most classic WordPress themes and requires only Node.js, npm, and the vite and sass packages as dev dependencies.

0 comments Read more at DEV Community