# command Published articles for command. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Why your Redis is slow: it is single threaded and you sent it KEYS DevFeed: [Why your Redis is slow: it is single threaded and you sent it KEYS]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-09-15T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [Redis](), [Latency](), [Concurrency]() Tags: [blocking](), [caching](), [command](), [latency](), [observability](), [performance](), [redis](), [single-threaded]() ### AI overview The article explains that Redis executes commands one at a time on a single thread, so expensive commands can block every client and cause latency spikes across all operations. It identifies KEYS as a key offender and also discusses large DEL operations, unbounded LRANGE, SMEMBERS on large sets, and FLUSHALL. Redis 6 threaded I/O helps with socket handling but does not change single-threaded command execution. ### Source excerpt Redis executes commands one at a time on a single thread, so any command that takes 200ms makes every other client wait 200ms regardless of how trivial their request was. KEYS scans the entire keyspace and is the obvious offender, but DEL on a large collection, unbounded LRANGE, SMEMBERS on a big set and FLUSHALL are all linear in the size of the data and block identically. The tell is a latency spike across all operations at once while CPU and network look normal. ## \[webapps\] Linksys E1200\_2.0.04 - Unauthenticated OS Command Injection DevFeed: [\[webapps\] Linksys E1200\_2.0.04 - Unauthenticated OS Command Injection]() Original publisher: [Read original article]() Author: jarrett Published: 2026-08-31T00:00:00Z Content type: article Language: en Sources: [Exploit-DB.com RSS Feed]() Topics: [Exploit](), [Hardware](), [webapps]() Tags: [command](), [cve](), [cve-2025-60689](), [exploit](), [hardware](), [os](), [platform](), [webapps]() ### AI overview This exploit listing identifies an unauthenticated OS command injection affecting Linksys E1200 version 2.0.04 and references CVE-2025-60689. ### Source excerpt Linksys E1200_2.0.04 - Unauthenticated OS Command Injection ## Security Caveat: Locked out of my server while traveling DevFeed: [Security Caveat: Locked out of my server while traveling]() Original publisher: [Read original article]() Author: Josh Sherman Published: 2026-08-30T00:00:00Z Content type: opinion Language: en Sources: [Josh Sherman]() Topics: [Self-hosted](), [Security](), [Linode](), [Firewall](), [hosting](), [DDoS]() Tags: [command](), [ddos](), [firewall](), [hosting](), [linode](), [security](), [self-hosting]() ### AI overview A personal account of being unable to access a self-hosted server while traveling because firewall rules restricted services and ports to specific IP addresses. The author describes using Linode's web-hosted shell to add a temporary nomadic IP address to the allow list, then plans to remove it afterward. ### Source excerpt I'm still on my self-hosting kick as of late, while also questioning my life choices around hosting my own git forge. The last week or so has included what appears to be a DDoS attack rather than some coordinated scraping effort by a sketchy LLM company. Open source will prevail, even if I'm being stubborn about giving in and setting up Anubis. WordPress has been its own other adventure, but this isn't meant to be a post about those security caveats. I'll save those for another week. The current dilemma is that I'm far from home, ~30 hours away up in Rhode Island. I'm sitting at Audrey's Coffee House & Lounge, where it was a bit too early to order a BLT. As I sat down to knock out a quick blog post, I realized very quickly that I didn't think things through as well as I had thought. I keep my servers pretty well hardened, including but not limited to limiting access to certain services / ports to specific IP addresses. This tends to not be much of a problem. I do a lot of work from the house, which in itself is a problem I want to remedy in the near future. I also boss agents around remotely, but they are all homebodies as well. Since I like to stay as close to the server as possible, I try to not introduce managed services except where I feel it's absolutely necessary. In this scenario, I use iptables via the ufw command. I don't run a large enough fleet that I'd feel like leveraging Linode's firewall would be beneficial. Path of least resistance today would be to simply compose a blog post and get it live when I'm back home. Could probably just ask one of my friendly robots to take the markdown file and get it out there for me too. But alas, I would prefer to figure out how to pull this off, then blog about it. All while thinking through alternatives so future Josh can look back at this post and ask, "so why didn't you actually do anything you talked about in this post?" This dance probably looks about the same with most modern VPS hosting providers, but my story ## Super-comma-nix: A Rust helper for Nix shell and run commands with sandboxing DevFeed: [Super-comma-nix: A Rust helper for Nix shell and run commands with sandboxing]() Original publisher: [Read original article]() Author: ksvivek Published: 2026-08-14T08:01:27Z Content type: article Language: en Sources: [Announcements - NixOS Discourse]() Topics: [Nix](), [Rust](), [Command-line interface](), [Shell](), [ci]() Tags: [announcements](), [ci](), [code](), [command](), [commands](), [config](), [dependencies](), [developer-experience](), [environments](), [integrations](), [runner](), [rust](), [shell]() ### AI overview Super-comma-nix is a Rust command-runner helper for Nix that shortens common nix shell, nix run, and version-checking commands. It integrates with nix-output-monitor and landrun, supports configurable environment variables, and can produce commands without running them. ### Source excerpt Hi All super-comma is an ultra-fast, zero-dependency Nix command runner helper written in Rust and powered directly by nixpkgs-multiverse. It is inspired by the project comma nix. But my project is loaded with batteries and much more DX(Developer eXperience). You'll love it. This project makes the consumption easier for nix shell, nix run commands and versions list all with simple handy commands like ,(nix run) ,s(nix shell) ,v(versions checking) . The project have some cool flags and also integrations like nix-output-monitor and landrun for sandboxing all with just few flags. Dont want to type these nom and sandboxing flags verbose? U can add it to env variable for session or globally as like config. Go read the README, you'll love it. Though plenty of features, I sticked to this principle: Simple by default and powerful when needed So learn as u go. Want more integrations? Please feel free to raise an issue Sandboxing is pretty cool, u want to try a software but dont want it to connect to inernet? This project enables some real adhoc shell environments and with the sandboxing etc figure out the possibilities for everyday usage, CI etc The project has zero dependencies for rust. Coz this project just makes u type short commands and the program just does some splitting and joining of strings. So please feel free to unslop some logic written by the LLM there if u think it can be simplified. Skeptic coz LLM(though it'll change in future)? just use the program with -o flag and u can just use the program to give you the final command without running. The Github README is carefully crafted to explain all the features, so take your time there. I'm a nix and nixos user since 2024, so I know some nix and the project design and integration of nom and landrun etc purely my design and idea and instructed the llm with my knowledge. But i'm not having good rust knowledge, so that part is covered by LLM. I wanted to write it with PF languages like haskell etc, but I wanted to qui ## How to Stop or Skip Cypress Test Commands DevFeed: [How to Stop or Skip Cypress Test Commands]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2026-08-07T04:00:00Z Content type: tutorial Language: en Sources: [Gleb Bahmutov]() Topics: [Cypress](), [Mocha](), [test](), [Code]() Tags: [callback](), [command](), [commands](), [condition](), [cypress](), [object](), [products](), [skip](), [syntax](), [test](), [testing](), [tests]() ### AI overview This tutorial explains three ways to stop or skip Cypress test execution: using Cypress.stop, skipping the current Mocha test, and skipping the remaining commands in the Cypress command queue. It describes the trade-offs of each approach, including whether later tests run and whether completed commands remain visible. ### Source excerpt Let's say you have a long-ish Cypress test and you know a place where it might fail. You want to stop / skip the test commands. ## iPhone Screenshots on Linux, on a Stream Deck Button DevFeed: [iPhone Screenshots on Linux, on a Stream Deck Button]() Original publisher: [Read original article]() Author: Ivan Morgillo Published: 2026-06-22T09:30:00Z Content type: tutorial Language: en Sources: [Ivan Morgillo]() Topics: [iphone](), [iOS](), [Linux](), [systemd]() Tags: [capture](), [command](), [ios](), [iphone](), [linux](), [root](), [screenshots](), [stream](), [systemd]() ### AI overview A tutorial on capturing iPhone screenshots directly to the Linux clipboard with a Stream Deck button. On iOS 17 and later, it uses pymobiledevice3, Developer Mode, a mounted Developer Disk Image, and a root-run systemd tunnel service instead of the classic idevicescreenshot workflow. ### Source excerpt How I screenshot my iPhone straight to the Linux clipboard with one Stream Deck button -- iOS 17+ needs pymobiledevice3 and a root tunnel, not the classic idevicescreenshot. No Mac required. ## PM Skills 2.0: Red-Team Your Roadmap, Then Check the Code Before You Ship DevFeed: [PM Skills 2.0: Red-Team Your Roadmap, Then Check the Code Before You Ship]() Original publisher: [Read original article]() Author: Paweł Huryn Published: 2026-06-05T17:55:04Z Content type: release Language: en Sources: [The Product Compass]() Topics: [Claude](), [Artificial Intelligence](), [GitHub](), [test](), [execution]() Tags: [ai](), [claude](), [command](), [env-file-security](), [github](), [plugins](), [release](), [review]() ### AI overview PM Skills 2.0 is a free, MIT-licensed Claude marketplace release with 68 skills, 42 commands, and 9 plugins. It adds the /red-team-prd command and an AI Shipping Kit for documenting, auditing, and shipping AI-built applications with human sign-off. ### Source excerpt 68 free Claude skills, 42 commands, 9 plugins. This release adds a new /red-team-prd command and the AI Shipping Kit: a way to document, audit, and ship AI-built apps with human sign-off. ## Comparing Cypress cy.prompt, Cypress Studio, and Hand-Coded Tests DevFeed: [Comparing Cypress cy.prompt, Cypress Studio, and Hand-Coded Tests]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2026-04-28T04:00:00Z Content type: comparison Language: en Sources: [Gleb Bahmutov]() Topics: [Cypress](), [Testing](), [coding](), [Visual Studio Code]() Tags: [ai](), [coding](), [command](), [copilot](), [cypress](), [editor](), [next](), [process](), [prompt](), [selectors](), [test](), [testing](), [vs]() ### AI overview The article compares three ways to create a Cypress login test: hand-coding in VSCode, using cy.prompt, and recording actions with Cypress Studio. In the author's test, hand-coding worked reliably, while cy.prompt produced failures and code that needed manual cleanup, and Cypress Studio inserted unwanted assertions and missed recommended selectors and negative assertions. ### Source excerpt Cypress-the-company is putting a lot of effort behind its cy.prompt command (which I recreated ## Waiting for PostgreSQL 19 - json format for COPY TO DevFeed: [Waiting for PostgreSQL 19 - json format for COPY TO]() Original publisher: [Read original article]() Author: depesz Published: 2026-03-29T12:34:22Z Content type: article Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [JSON](), [export](), [data](), [Query (disambiguation)](), [interoperability]() Tags: [command](), [copy](), [data](), [developers](), [export](), [json](), [pg19](), [postgresql](), [query](), [stream](), [uncategorized](), [waiting]() ### AI overview The article discusses a PostgreSQL 19 patch adding a JSON format option to COPY TO. It allows table data or query results to be exported as a stream of JSON objects, one object per line, with an option to wrap the output in an array. ### Source excerpt On 20th of March 2026, Andrew Dunstan committed patch: json format for COPY TO This introduces the JSON format option for the COPY TO command, allowing users to export query results or table data directly as a stream of JSON objects (one per line, NDJSON style). The JSON format is currently supported only ... Continue reading "Waiting for PostgreSQL 19 - json format for COPY TO" ## How to bypass SSL for PROJ reprojection DevFeed: [How to bypass SSL for PROJ reprojection]() Original publisher: [Read original article]() Author: Robin Wilson Published: 2026-03-23T16:23:36Z Content type: tutorial Language: en Sources: [Robin Wilson]() Topics: [Geographic Information System](), [Security](), [SSL](), [import](), [Linux](), [osx](), [Windows]() Tags: [academic](), [command](), [computing](), [gis](), [how-to](), [import](), [linux](), [osx](), [remote-sensing](), [security](), [ssl](), [windows]() ### AI overview This tutorial explains how to temporarily disable SSL verification for PROJ during coordinate reprojection when self-signed or misconfigured certificates cause downloads of conversion data to fail. It notes the security trade-off and points to setting a PROJ environment variable. ### Source excerpt A friend was using GDAL's ogr2ogr command to import some data to PostGIS recently, and as part of the import they were doing a reprojection of the data. They got the following error: PROJ: Cannot open https://cdn.proj.org/uk_os_OSTN15_NTv2_OSGBtoETRS.tif: schannel: the certificate or certificate chain is based on an untrusted root They've had various SSL errors on [...] ## Waiting for PostgreSQL 19 - Introduce the REPACK command DevFeed: [Waiting for PostgreSQL 19 - Introduce the REPACK command]() Original publisher: [Read original article]() Author: depesz Published: 2026-03-19T18:07:59Z Content type: article Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [postgresql clusters]() Tags: [analyze](), [bloat](), [command](), [indexes](), [locking](), [maintenance](), [pg-repack](), [pg19](), [planner](), [postgresql](), [repack](), [uncategorized](), [vacuum](), [waiting]() ### AI overview The article examines PostgreSQL 19's proposed built-in REPACK command, which combines functionality associated with VACUUM FULL and CLUSTER. It demonstrates reclaiming space and reordering a table, discusses locking because concurrent operation is not yet supported, and introduces the pg_stat_progress_repack progress view and available command forms. ### Source excerpt On 10th of March 2026, Álvaro Herrera committed patch: Introduce the REPACK command REPACK absorbs the functionality of VACUUM FULL and CLUSTER in a single command. Because this functionality is completely different from regular VACUUM, having it separate from VACUUM makes it easier for users to understand; as for CLUSTER, the term is heavily ... Continue reading "Waiting for PostgreSQL 19 - Introduce the REPACK command" ## In Praise of -dry-run DevFeed: [In Praise of -dry-run]() Original publisher: [Read original article]() Author: Henrik Warne Published: 2026-01-31T17:50:03Z Content type: opinion Language: en Sources: [Henrik Warne]() Topics: [Development](), [Testing](), [Database]() Tags: [command](), [configuration](), [development](), [dry-run](), [programming](), [reporting](), [run](), [testing]() ### AI overview The author describes adding a --dry-run option to a reporting application that generates, archives, uploads, and validates reports. The option prints the planned steps without making changes, providing a quick sanity check and helping test report-generation logic safely. ### Source excerpt For the last few months, I have been developing a new reporting application. Early on, I decided to add a -dry-run option to the run command. This turned out to be quite useful - I have used it many times ... Continue reading -> ## Waiting for PostgreSQL 19 - Implement ALTER TABLE ... MERGE/SPLIT PARTITIONS ... command DevFeed: [Waiting for PostgreSQL 19 - Implement ALTER TABLE ... MERGE/SPLIT PARTITIONS ... command]() Original publisher: [Read original article]() Author: depesz Published: 2026-01-04T17:30:47Z Content type: opinion Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [function]() Tags: [command](), [locking](), [merge](), [partition](), [partitioning](), [partitions](), [pg19](), [postgresql](), [split](), [uncategorized](), [waiting]() ### AI overview A PostgreSQL 19 development update describes the ALTER TABLE command for merging and splitting partitions. The patch was rolled back after earlier discussion, then recommitted; testing showed it worked as expected, with slightly less locking observed. Further changes may be needed before the feature reaches the final release. ### Source excerpt Important update This has been rolled back after some discussion. On 14th of December 2025, Alexander Korotkov committed patch: Implement ALTER TABLE ... MERGE PARTITIONS ... command This new DDL command merges several partitions into a single partition of the target table. The target partition is created using the new createPartitionTable() function with the ... Continue reading "Waiting for PostgreSQL 19 - Implement ALTER TABLE ... MERGE/SPLIT PARTITIONS ... command" ## Waiting for PostgreSQL 19 - Support COPY TO for partitioned tables. DevFeed: [Waiting for PostgreSQL 19 - Support COPY TO for partitioned tables.]() Original publisher: [Read original article]() Author: depesz Published: 2025-10-22T10:05:08Z Content type: article Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [data]() Tags: [command](), [copy](), [partition](), [partitioning](), [partitions](), [performance](), [pg19](), [postgresql](), [uncategorized](), [waiting]() ### AI overview The article discusses a PostgreSQL patch committed by Masahiko Sawada that adds direct COPY TO support for partitioned tables. Previously, users had to use COPY (SELECT ...) TO as a workaround. The author's test found similar performance, with COPY from a table slightly slower in the reported case. ### Source excerpt On 20th of October 2025, Masahiko Sawada committed patch: Support COPY TO for partitioned tables. Previously, COPY TO command didn't support directly specifying partitioned tables so users had to use COPY (SELECT ...) TO variant. This commit adds direct COPY TO support for partitioned tables, improving both usability and performance. Performance tests show ... Continue reading "Waiting for PostgreSQL 19 - Support COPY TO for partitioned tables." ## WebAssembly Jobs and CronJobs in Kubernetes with SpinKube & the Spin Command Trigger DevFeed: [WebAssembly Jobs and CronJobs in Kubernetes with SpinKube & the Spin Command Trigger]() Original publisher: [Read original article]() Author: Thorsten Hans Published: 2024-11-05T12:00:00Z Content type: tutorial Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [WebAssembly](), [Kubernetes]() Tags: [command](), [how-to](), [kubernetes](), [webassembly]() ### AI overview A tutorial on running WebAssembly applications as Kubernetes Jobs and CronJobs using Spin Command Trigger and SpinKube. ### Source excerpt Learn how to run WebAssembly apps as Kubernetes Jobs and CronJobs using Spin Command Trigger and SpinKube ## Installing NetBSD on Linode DevFeed: [Installing NetBSD on Linode]() Original publisher: [Read original article]() Published: 2024-09-14T19:29:01Z Content type: tutorial Language: en Sources: [Signs of Triviality]() Topics: [Linode](), [Command-line interface]() Tags: [command](), [command-line](), [console](), [how-to](), [install](), [linode]() ### AI overview A tutorial explaining how to install NetBSD on a Linode instance using the command line and serial console. ### Source excerpt Instructions on how to install NetBSD on a Linode instance. All steps are performed via the command-line and serial console. ## Demystifying MongoDB write operations DevFeed: [Demystifying MongoDB write operations]() Original publisher: [Read original article]() Published: 2024-02-18T00:00:00Z Content type: tutorial Language: en Sources: [Gaurav Sarma's Blog]() Topics: [MongoDB](), [Replication](), [Cache]() Tags: [cache](), [checkpoint](), [command](), [memory](), [mongodb](), [replication](), [storage-engine]() ### AI overview This post explains MongoDB write operations by connecting WiredTiger caching, journaling, checkpointing, and replication. It describes how writes move through memory, the write-ahead log, and disk, including stated default flushing intervals and recovery behavior. ### Source excerpt In this post, we will try to understand the different factors which control the write operations in MongoDB. We will try to tie in the common concepts like checkpointing, journaling, replication that we hear so often in the context of write operations... ## A Contextual and Dynamic Approach to Designing Command-Line Interfaces DevFeed: [A Contextual and Dynamic Approach to Designing Command-Line Interfaces]() Original publisher: [Read original article]() Published: 2023-11-17T00:00:00Z Content type: opinion Language: en Sources: [Garnix Blog]() Topics: [Command-line interface](), [interfaces]() Tags: [approach](), [command](), [command-line](), [interfaces]() ### AI overview The article discusses a contextual and dynamic approach to designing command-line interfaces. ### Source excerpt A more contextual and dynamic approach to designing command-line interfaces. ## Spin Application Structure DevFeed: [Spin Application Structure]() Original publisher: [Read original article]() Author: Tim McCallum Published: 2023-08-01T12:00:00Z Content type: tutorial Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [structure](), [App]() Tags: [application](), [command](), [guide](), [how-to](), [structure]() ### AI overview A how-to guide covering the "spin new" command, Spin application structure, and tips for organizing larger applications. ### Source excerpt This how-to guide discusses the 'spin new' command app structure and tips on how to organize larger apps. ## Introducing Spin 1.1 DevFeed: [Introducing Spin 1.1]() Original publisher: [Read original article]() Author: Radu Matei Published: 2023-04-14T16:00:00Z Content type: release Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [Developer experience](), [Go Language](), [Rust](), [HTTP]() Tags: [command](), [configure](), [developer-experience](), [go](), [http](), [improvements](), [key-value-store](), [rust]() ### AI overview Spin 1.1 improves the developer experience with a new `spin watch` command, configurable key/value storage, and new HTTP routers for Rust and Go. ### Source excerpt Spin 1.1 brings improvements to the developer experience through a new `spin watch` command, the ability to configure the Spin key/value store, new HTTP routers for Rust and Go, and more! ## AWS IAM and Cost Explorer CLI Setup DevFeed: [AWS IAM and Cost Explorer CLI Setup]() Original publisher: [Read original article]() Published: 2023-02-01T16:15:02Z Content type: tutorial Language: en Sources: [Signs of Triviality]() Topics: [AWS IAM](), [Command-line interface](), [IAM](), [Amazon Web Services](), [account]() Tags: [account](), [admin](), [aws](), [aws-iam](), [cli](), [command](), [command-line](), [how-to](), [iam](), [setup]() ### AI overview A tutorial on creating an IAM administrator user and configuring another AWS account to use Cost Explorer from the command line. ### Source excerpt How to create an IAM admin user and configure another account to use Cost Explorer on the command-line. ## Maybe I can Stay in NuShell -or- Living in a Diverse Land of Shells DevFeed: [Maybe I can Stay in NuShell -or- Living in a Diverse Land of Shells]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2022-07-20T09:36:00Z Content type: opinion Language: en Sources: [Scott Johnson]() Topics: [Shell](), [Command-line interface](), [Bash](), [Zsh]() Tags: [bash](), [command](), [nushell](), [rails](), [ruby](), [rvm](), [shell](), [zsh]() ### AI overview The author explains that they can continue using NuShell as their main shell while switching to Bash or Zsh when tools such as RVM require them. A Rails project is successfully created after switching to Bash. ### Source excerpt I really, really like NuShell. The realization that maybe I had to leave was, I'll admit, mildly crushing. And then I just had the realization that maybe I don't have to leave NuShell and slink back to the dirty, byte infested corners of Bash and Zsh. Here's what just happened: /Users/sjohnson/Sync/coding/flow_analytics/open_source〉rails new pool_api --api Rails is not currently installed on this system. To get the latest version, simply type: $ sudo gem install rails You can then rerun your "rails" command. /Users/sjohnson/Sync/coding/flow_analytics/open_source〉ruby -v 07/20/2022 05:34:41 AM ruby 2.6.8p205 (2021-07-07 revision 67951) [universal.x86_64-darwin21] /Users/sjohnson/Sync/coding/flow_analytics/open_source〉rvm use And that was the point when I realized "Oh yeah - RVM doesn't work on NuShell" and then it struck me - I can run Bash: /Users/sjohnson/Sync/coding/flow_analytics/open_source〉/bin/bash 07/20/2022 05:34:57 AM bash: /Users/sjohnson/Library/Python/2.7/bin/powerline-config: /usr/bin/python: bad interpreter: No such file or directory bash: /Users/sjohnson/Library/Python/2.7/bin/powerline-config: /usr/bin/python: bad interpreter: No such file or directory bash: /Users/sjohnson/.iterm2_shell_integration.nu: No such file or directory ERROR: Can't find Ruby library file or shared library lunchy usage: dirname string [...] The default interactive shell is now zsh. To update your account to use zsh, please run `chsh -s /bin/zsh`. For more details, please visit https://support.apple.com/kb/HT208050. [sjohnson:~/Sync/coding/flow_analytics/open_source] [base] $ rails new pool_api --api create create README.md create Rakefile create .ruby-version create config.ru create .gitignore create .gitattributes create Gemfile run git init from "." ... So maybe my system can mostly run NuShell and I can drop in and out of Bash / Zsh when I need different things. Fingers Crossed. ## SSH Audit: How to use SSH Audit Logging DevFeed: [SSH Audit: How to use SSH Audit Logging]() Original publisher: [Read original article]() Author: info@goteleport.com (Jennifer Roberts) Published: 2022-01-04T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [audit](), [ssh](), [Logging](), [Security](), [Linux](), [Bash](), [Command-line interface]() Tags: [audit](), [bash](), [bash-history](), [command](), [how-to](), [linux](), [logging](), [security](), [ssh](), [terminal]() ### AI overview This tutorial explains how to implement SSH audit logging on Linux hosts. It covers unique user logins, detailed authentication logs, protecting log files from manipulation, terminal session recording, and safeguards for Bash history. ### Source excerpt This blog post will walk you through how you can track changes on Linux hosts with SSH Audit Logging. ## Rails 6 - Can't Find Application.js DevFeed: [Rails 6 - Can't Find Application.js]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2021-12-18T14:51:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Rails](), [Yarn](), [Development]() Tags: [asset-pipeline](), [bash](), [command](), [compilation](), [foreman](), [git](), [js](), [rails](), [rake]() ### AI overview A troubleshooting note about a Rails 6 project where Webpacker cannot find application.js. It explains installing Webpacker and using bin/dev with Foreman so the JavaScript and CSS asset processes run. ### Source excerpt So I started fiddling about with a new Rails project and after finding a likely starting point, I immediately ended up with this: Webpacker can't find application.js in I'm old school Rails and I find the whole asset compilation situation, honestly, perplexing. The solution turned out to be: bundle exec rails webpacker:install after the normal: git clone foo bundle install bundle exec rake db:migrate I have no idea why the bundler install doesn't handle executing webpacker:install but cie la vie. The more things change, the more they stay the same ... Update: I kept at this and kept finding that I didn't have webpacker or some other portion of the rails stack running. I finally traced this down to things having changed. Traditionally I've always run rails as: bundle exec rails s -pXYZ And the new approach is to run: bin/dev which in turn contains: #!/usr/bin/env bash if ! command -v foreman &> /dev/null then echo "Installing foreman..." gem install foreman fi foreman start -f Procfile.dev "$@" and the Procfile.dev file contains: web: bin/rails server -p 3000 js: yarn build --watch css: yarn build:css --watch I was literally missing the yarn command so part of the overall asset pipeline just wasn't running. Old habits die hard. [Next page]()