# staging Published articles for staging. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Blog: Install and Test Atomic Red in Kubernetes DevFeed: [Blog: Install and Test Atomic Red in Kubernetes]() Original publisher: [Read original article]() Published: 2023-12-12T00:00:00Z Content type: tutorial Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Kubernetes](), [Falco](), [threat detection](), [Testing](), [Security](), [Open Source]() Tags: [deployment](), [falco](), [installation](), [kubernetes](), [mapping](), [open-source](), [security](), [security-concept](), [staging](), [test-lab](), [testing](), [threat-detection]() ### AI overview This tutorial explains how to deploy and test Atomic Red Team in Kubernetes and use the open source Falco to detect simulated threats in real time. It describes evaluating detections against the MITRE ATT&CK framework, identifying coverage gaps, and refining custom rules. The article recommends using a test lab or staging environment rather than production. ### Source excerpt In cloud-native environments, where applications scale up and down much faster than traditional monolithic application architectures, the ability to proactively identify and respond to threats in real time is paramount. As more organizations embrace cloud-native architectures for application delivery, more robust security measures need to be introduced. In this blog post, we delve into the dynamic realm of Kubernetes threat detection by exploring how open source Falco can seamlessly detect Atomic Red Team tests in real time within Kubernetes environments. Atomic Red Team is a powerful framework designed to simulate real-world attacks, providing organizations with a controlled environment to validate the effectiveness of their security measures. We take this a step further by deploying Atomic Red to Kubernetes with a single command, creating a realistic testing ground for evaluating the responsiveness of Falco. Our journey begins with the effortless deployment of Atomic Red to Kubernetes, showcasing the simplicity and efficiency of orchestrating security testing within containerized environments. Once deployed, we invoke specific Atomic Red Team tests, simulating a range of threat scenarios. The true test lies in Falco's ability to detect these threats in line with the MITRE ATT&CK framework, a globally-recognized matrix mapping adversary techniques to defensive tactics. This exploration is not just about identifying threats; it's a collaborative effort to enhance Falco's coverage. Should we identify any gaps in detection, we dive deeper, revising the executed techniques and crafting custom rules. This iterative process aims to extend our MITRE ATT&CK coverage, aligning Falco with the industry's best practices for threat detection and mitigation. Deploying Atomic Red Team To avoid any potential service disruption in production environments, we recommend installing Atomic Red in a test lab environment, or at least a staging environment of Kubernetes. We have a step-by ## The staging Mobian distro DevFeed: [The staging Mobian distro]() Original publisher: [Read original article]() Author: Mobian team Published: 2021-03-15T00:00:00Z Content type: tutorial Language: en Sources: [Mobian's Blog]() Topics: [Debian](), [apt]() Tags: [apt](), [debian](), [distro](), [packages](), [repository](), [stable](), [staging](), [switching](), [testing]() ### AI overview This tutorial explains Mobian staging, a newer Mobian package repository layered over Debian bullseye. It describes how to switch to the staging repository and distinguish packages from Mobian and Debian. ### Source excerpt Most of us just want their phone to be working. But some like to be more on the edge of things, trying out the newest bugsfeatures. The recently announced staging distribution allows users to do just that. Read further to learn its purpose and how to enable it. Mobian is an overlay over the regular Debian bullseye repository. Its package source is configured in /etc/apt/sources.list with a single line: deb http://deb.debian.org/debian bullseye main. 1 Currently the (relatively) stable Mobian overlay is configured in /etc/apt/sources.list.d/mobian.list containing the following: deb http://repo.mobian.org/ bullseye main non-free If you had flashed your device with an image older than April 26th, 2021, you may have a file named /etc/apt/sources.list.d/extrepo_mobian.sources instead, containing the following: Types: deb Architectures: amd64 arm64 armhf Uris: http://repo.mobian.org/ Suites: mobian Components: main non-free Signed-By: /var/lib/extrepo/keys/mobian.asc Recently we introduced Mobian staging, in which we include packages that are pretty new and/or might need a bit more testing. Mobian staging is a full Mobian repository, so it includes everything that the "normal" repository includes and a bit more (and some packages a bit newer). By switching to it, you agree to name your firstborn Debian and to never eat cookies again after 3pm! So think twice before you do it! The easiest way you can switch to using this repository is by simply changing the word bullseye to staging in /etc/apt/sources.list.d/mobian.list, or the line Suites: mobian to Suites: staging in /etc/apt/sources.list.d/extrepo_mobian.sources. This way, you will be getting all your Mobian packages from https://repo.mobian.org/dists/staging instead of https://repo.mobian.org/dists/mobian. Some of the packages you install will be from the staging Mobian repo and most will be coming directly and unmodified from one of the Debian mirrors. How do I find out if a package comes from Debian or Mobian? Great ## Preventing Google from Indexing Staging Sites DevFeed: [Preventing Google from Indexing Staging Sites]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2017-02-02T09:00:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Search engine optimization (SEO)](), [Crawler](), [Content Management System](), [Web Development]() Tags: [config](), [diluting](), [environments](), [google](), [indexing](), [insights](), [multi-environment](), [prevent](), [robots-txt](), [seo](), [seomatic](), [sites](), [staging](), [value]() ### AI overview This tutorial explains how to prevent Google and other search engines from indexing staging sites. It presents robots.txt and SEOmatic as an alternative to password protection, allowing external performance and SEO testing while avoiding duplicate-content concerns. ### Source excerpt SEOmatic and a multi-environment config can prevent Google from indexing your staging sites, and diluting your SEO value ## Multi-Environment Config for Craft CMS DevFeed: [Multi-Environment Config for Craft CMS]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2016-12-02T20:32:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [Development](), [Website]() Tags: [cms](), [configs](), [craft](), [effectively](), [efficacious](), [environment](), [environments](), [help](), [here-s](), [insights](), [multi-environment](), [production](), [project](), [settings](), [staging](), [strategy](), [work]() ### AI overview This tutorial explains how to configure a Craft CMS 2.5.x project for live, staging, and local environments. It covers environment-specific settings, including development mode, template caching, databases, passwords, file-system locations, and configuration overrides. ### Source excerpt Multi-environment configs help you work more effectively with Craft CMS. Here's an efficacious strategy ## pg\_staging PostgreSQL backup restoration tool enters Debian's NEW queue DevFeed: [pg\_staging PostgreSQL backup restoration tool enters Debian's NEW queue]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2009-11-25T10:49:00Z Content type: release Language: en Sources: [Dimitri Fontaine]() Topics: [PostgreSQL](), [Tool](), [backups](), [Databases](), [Debian]() Tags: [backups](), [commands](), [databases](), [debian](), [pg-dump](), [postgresql](), [release](), [server](), [snapshot](), [staging]() ### AI overview The article introduces pg_staging, a PostgreSQL tool entering Debian's NEW queue. It provides commands for dumping and restoring databases and supports creating staging environments from backups for backup validation, development, integration, pre-live testing, and snapshots. ### Source excerpt So there it is, this newer contribution of mine that I presented at PGDay is now in debian NEW queue. pg_staging will empower you with respect to what you do about those nightly backups ( pg_dump -Fc or something). The tool provides a lot of commands to either dump or restore a database. It comes with documentation covering about it all, except for the londiste support part, which will be there in time for 1.0.0 release. The Todo list is getting smaller and smaller, the version you'll soon find in debian sid is already called 0.9. ## PGDay.eu in Paris and the pg\_staging tool for production backups and staging environments DevFeed: [PGDay.eu in Paris and the pg\_staging tool for production backups and staging environments]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2009-11-09T08:50:00Z Content type: opinion Language: en Sources: [Dimitri Fontaine]() Topics: [PostgreSQL](), [backups](), [Tool]() Tags: [backups](), [community](), [events](), [postgresql](), [production](), [staging]() ### AI overview The article reflects on PGDay.eu in Paris, describing its talks, food, party, and PostgreSQL community. It also introduces pg_staging, a tool intended to use production backups to help maintain staging environments for developers and testers. ### Source excerpt moment. Lots of attendees, lots of quality talks ( slides are online), good food, great party: all the ingredients were there! It also was for me the occasion to first talk about this tool I've been working on for months, called pg_staging, which aims to empower those boring production backups to help maintaining staging environments (for your developers and testers). All in all such events keep reminding me what it means exactly when we way that one of the greatest things about PostgreSQL is its community. If you don't know what I'm talking about, consider joining!