# Environment Published articles for Environment. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Native auto-activate in Flox DevFeed: [Native auto-activate in Flox]() Original publisher: [Read original article]() Author: garbas Published: 2026-08-03T20:37:51Z Content type: opinion Language: en Sources: [Announcements - NixOS Discourse]() Topics: [Nix](), [Development]() Tags: [announcements](), [environment](), [environments](), [functionality](), [services](), [setup](), [using]() ### AI overview The post discusses Flox 1.14.0, which adds native auto-activation for development environments. It compares this functionality with direnv and nix-direnv, noting that Flox also supports services, layered environments, shell aliases, and functions. ### Source excerpt So: if you are using nix and use it to setup your development environments you are probably using direnv. most of nixers I know use it. you change the directory and it automagically enters your development environment. at flox we call this auto activation. We released Flox 1.14.0 and we made this functionality native. Steve even wrote about it in detail: Flox | Auto-Activation Is Now Native in Flox. First question I would have as a Nix user would be: "Why didn't you just use direnv and extend like nix does it with nix-direnv?". In short: we would love to, but our activation includes deeper features like services, layered environments, shell aliases and functions. If nothing what you should take from this post is that you give direnv a try if using nix. and with flox this functionality comes out of the box. Do you also wish this functionality would come OOTB with nix? 3 posts - 2 participants Read full topic ## OpenTelemetry Spring Boot Starter Adds Declarative YAML Configuration in Version 2.26.0 DevFeed: [OpenTelemetry Spring Boot Starter Adds Declarative YAML Configuration in Version 2.26.0]() Original publisher: [Read original article]() Author: OpenTelemetry Authors; Docs CC BY Published: 2026-07-14T07:47:36Z Content type: article Language: en Sources: [Blog on OpenTelemetry]() Topics: [OpenTelemetry](), [Spring Boot](), [YAML](), [configuration](), [Environment Variables](), [telemetry](), [tracing]() Tags: [configuration](), [environment](), [java](), [opentelemetry](), [schema](), [setup](), [spring-boot](), [telemetry](), [traces](), [yaml]() ### AI overview The article explains how declarative configuration in the OpenTelemetry Spring Boot starter, available from version 2.26.0, embeds the SDK's YAML schema in application.yaml. It contrasts this approach with environment-variable configuration and describes how the YAML schema can represent telemetry pipelines and options beyond the fixed environment-variable catalog. ### Source excerpt The OpenTelemetry Spring Boot starter gained declarative-configuration support starting in version 2.26.0 -- the same YAML schema the Java agent introduced in late 2025, now embedded inside application.yaml. This post traces what one env var, OTEL_SERVICE_NAME=petclinic, does in that new world, and where the seams are. In a hurry? Jump straight to the Spring Boot starter declarative-config docs, paste your application.properties into the interactive converter, or pick your SDK setup in the Ecosystem Explorer with the Spring Boot starter target selected. Come back for the story when you have a coffee. ## Public Environment Variables For Your Tests Using cypress-expose Plugin DevFeed: [Public Environment Variables For Your Tests Using cypress-expose Plugin]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2026-03-12T04:00:00Z Content type: tutorial Language: en Sources: [Gleb Bahmutov]() Topics: [Cypress](), [Environment Variables](), [Processes]() Tags: [ci](), [configuration](), [cypress](), [environment](), [environment-variables](), [password](), [plugin](), [products](), [secrets](), [testing](), [tests]() ### AI overview This tutorial explains how the cypress-expose plugin passes public process environment variables into Cypress tests after Cypress v16 made such variables private by default. It warns that the plugin is intended only for non-secret data. ### Source excerpt Recently Cypress announced a change in how it will handle environment variables. Variables were always public and accessible to the appli ## Set Up a Python Project with uv DevFeed: [Set Up a Python Project with uv]() Original publisher: [Read original article]() Author: Boldizsár Published: 2025-11-10T07:28:01Z Content type: tutorial Language: en Sources: [MarvelousMLOps]() Topics: [Tutorial](), [Python]() Tags: [2025](), [command-line](), [environment](), [homebrew](), [install](), [linux](), [macos](), [python](), [terminal](), [tutorial](), [windows]() ### AI overview A tutorial for setting up a modern Python project with uv. It covers installing uv on macOS, Linux, and Windows, creating a project, reviewing its files, and creating and synchronizing a project-specific virtual environment and dependencies. ### Source excerpt In 2025 the best way to manage Python projects is using uv. This tutorial helps you set up a modern Python project from scratch using uv. ## PostmarketOS demonstrates Gboard integration for Linux mobile keyboards DevFeed: [PostmarketOS demonstrates Gboard integration for Linux mobile keyboards]() Original publisher: [Read original article]() Published: 2025-04-01T00:00:00Z Content type: tutorial Language: en Sources: [postmarketOS Blog]() Topics: [keyboard](), [Mobile](), [Linux](), [Android APK](), [Software](), [Android]() Tags: [android](), [android-apk](), [apk](), [crash](), [environment](), [focus](), [keyboard](), [linux](), [mobile](), [open-source](), [other](), [postmarketos](), [tensorflow](), [training-data]() ### AI overview PostmarketOS demonstrates an experimental keyboard setup in Phosh using Gboard through ATL. The prototype offers suggestions, swiping, autocorrection, and smart input detection, but it crashes often and will not ship because it relies on proprietary software. ### Source excerpt In our previous blog post 2025 Priorities: Reliability, Audio, Cameras and More, we asked "is there anything that you find terribly important that we have missed here?". And indeed, there was one thing that people would have liked us to focus more on, which is a better keyboard experience. This was unbelievably great timing, because we are actually integrating a new keyboard with the following features: Word complete suggestions Swiping Autocorrection of misspelled words Smart detection of what you meant to type vs. which buttons you have actually hit with your fingers We have hooked it up to Phosh, see it for yourself (this is a video, you might need to click it in order to have it start playing): Tech stack Please note that this is in early development. Currently it is still crashing often and you also need to be comfortable running proprietary software since this is actually Gboard running through ATL. So uh... on second thought we will not be shipping this in postmarketOS. However the underlying technology is very much worth showcasing since it allows running components and apps from that other operating system on proper Linux (Mobile) without running a full container! The video is real, and it shows that it is possible to build features like autocorrection and swiping with the APIs we already have in Linux Mobile today. In fact, phosh-osk-stub and swipeGuess can do most of this already! If somebody out there has the interest, skills and time to improve the Linux mobile keyboards to the point that they work as intuitively as proprietary ones: it is possible, get involved! Try it for yourself If you really want to, you can now run this proprietary piece of TensorFlow based software to tap into the results of training data from millions of Android user's keystrokes while tapping with your fingers on your postmarketOS phone. You can also use these instructions with the open source Hacker's Keyboard. Build ATL from sources: sudo apk add -t .atl-builddeps \ libopensles ## Using AI to expand global access to reliable flood forecasts DevFeed: [Using AI to expand global access to reliable flood forecasts]() Original publisher: [Read original article]() Author: Google AI (noreply@blogger.com) Published: 2024-03-20T16:06:00Z Content type: article Language: en Sources: [Google Research]() Topics: [Artificial Intelligence](), [Google](), [real-time](), [data](), [notifications]() Tags: [ai](), [data](), [environment](), [google](), [machine-learning](), [notifications](), [real-time](), [research](), [weather]() ### AI overview Google Research describes how AI and machine learning improved global flood forecasting in regions with scarce flood-related data. The work extended the average reliability of global nowcasts from zero to five days and supports real-time river forecasts up to seven days ahead across more than 80 countries. ### Source excerpt Posted by Yossi Matias, VP Engineering & Research, and Grey Nearing, Research Scientist, Google Research Floods are the most common natural disaster, and are responsible for roughly $50 billion in annual financial damages worldwide. The rate of flood-related disasters has more than doubled since the year 2000 partly due to climate change. Nearly 1.5 billion people, making up 19% of the world's population, are exposed to substantial risks from severe flood events. Upgrading early warning systems to make accurate and timely information accessible to these populations can save thousands of lives per year. Driven by the potential impact of reliable flood forecasting on people's lives globally, we started our flood forecasting effort in 2017. Through this multi-year journey, we advanced research over the years hand-in-hand with building a real-time operational flood forecasting system that provides alerts on Google Search, Maps, Android notifications and through the Flood Hub. However, in order to scale globally, especially in places where accurate local data is not available, more research advances were required. In "Global prediction of extreme floods in ungauged watersheds", published in Nature, we demonstrate how machine learning (ML) technologies can significantly improve global-scale flood forecasting relative to the current state-of-the-art for countries where flood-related data is scarce. With these AI-based technologies we extended the reliability of currently-available global nowcasts, on average, from zero to five days, and improved forecasts across regions in Africa and Asia to be similar to what are currently available in Europe. The evaluation of the models was conducted in collaboration with the European Center for Medium Range Weather Forecasting (ECMWF). These technologies also enable Flood Hub to provide real-time river forecasts up to seven days in advance, covering river reaches across over 80 countries. This information can be used by people, communi ## Garn: a Nix-, Deno-, and TypeScript-based build tool and environment manager DevFeed: [Garn: a Nix-, Deno-, and TypeScript-based build tool and environment manager]() Original publisher: [Read original article]() Published: 2023-11-02T00:00:00Z Content type: release Language: en Sources: [Garnix Blog]() Topics: [Tool](), [Deno](), [Nix](), [TypeScript]() Tags: [build-tool](), [environment](), [typescript]() ### AI overview Garn is announced as a build tool and environment manager based on Nix, Deno, and TypeScript. ### Source excerpt Announcing garn, a build tool and environment manager based on Nix, Deno and Typescript ## Accept E-Commerce Payments Easily with PayPal's Buttons Component DevFeed: [Accept E-Commerce Payments Easily with PayPal's Buttons Component]() Original publisher: [Read original article]() Author: Arit Developer Published: 2023-10-24T16:07:59Z Content type: tutorial Language: en Sources: [PayPal Technology]() Topics: [API](), [servers](), [Front end](), [HTML](), [npm](), [App]() Tags: [api](), [back-end](), [code](), [credentials](), [demo](), [e-commerce](), [ecommerce](), [environment](), [front-end](), [github](), [html](), [javascript](), [npm](), [package-json](), [payments](), [payments-technology](), [paypal](), [programming]() ### AI overview A tutorial for integrating PayPal Standard Checkout and its Payment Buttons component into a simple HTML and NodeJS shopping application. It covers prerequisites, sandbox credentials, backend and frontend setup, checkout flow, and custom integration guidance. ### Source excerpt Accepting online payments is now a universal must-have, catering to everyone from solo entrepreneurs to massive global corporations. PayPal's Standard Checkout allows for seamless integration of PayPal's Payment Buttons component into your e-commerce app, granting you the power to accept online payments. In this guide, I am going to show how to add Standard Checkout to a simple shopping app, built with HTML and NodeJS. Guide Overview Part 1. Prerequisites Part 2a. Basic Integration -- Code Setup Part 2b. Basic Integration -- Checkout Flow Part 3a. Custom Integration -- Code Setup Part 3b. Custom Integration -- Checkout Flow Part 4. Conclusion Part 5. Additional PayPal Payment Integrations Part 1. Prerequisites To complete this integration, you will need the following information: API Credentials (Client ID and Secret) for a PayPal REST app: paste these from your Developer Dashboard. Since we are working in a development environment in this demo, ensure that the Sandbox Toggle is on. Obtain Test API Credentials The username and password for a Personal Sandbox account: you will need this to complete the checkout process. Navigate to Sandbox Accounts under Testing ToolsObtain Personal Sandbox Account login details You can grab the code for our completed Checkout Integration demo from the PayPal Developer GitHub repository. Part 2a. Basic Integration -- Code Setup Navigate to PayPal's Integrate Checkout documentation. The documentation shows you how to set your development environment up: installing npm, verifying your package.json file, and setting up your .env file. Next, you will set up your back-end server and front-end code. The documentation presents the contents of three files: server.js (for the back-end server), app.js (for the client-side logic) and checkout.html (for the user interface). Copy the Backend CodeCopy the Frontend Code Grab these code snippets and paste them into your IDE (Integrated Development Environment). I strongly recommend that you implement the ## Using the Temporal CLI DevFeed: [Using the Temporal CLI]() Original publisher: [Read original article]() Author: Loren Sands-Ramshaw Published: 2023-04-27T04:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [Command-line interface](), [Development](), [Server]() Tags: [aliases](), [auto-completion](), [bash](), [cli](), [command-line](), [commands](), [development](), [docs](), [download](), [environment](), [how-to](), [json](), [pagination](), [server](), [temporal-concepts]() ### AI overview A tutorial on using the Temporal CLI to install the tool, run and interact with a Temporal Server, configure environments and aliases, enable shell completion, and understand changes when upgrading from the previous CLI. ### Source excerpt How to use the Temporal CLI to run a development version of the Temporal Server and interact with it. ## Fluent Multi-Environment Config for Craft CMS 4 DevFeed: [Fluent Multi-Environment Config for Craft CMS 4]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2022-07-26T04:00:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [data]() Tags: [allows](), [autocomplete](), [better](), [cms](), [config](), [craft](), [create](), [editor](), [environment](), [errors](), [fewer](), [files](), [fluent](), [insights](), [less](), [model](), [multi-environment](), [settings](), [using](), [work]() ### AI overview This tutorial explains how Craft CMS 4.2's optional fluent configuration interface improves multi-environment config files. It highlights autocomplete, inline documentation, and type-checking as ways to reduce lookup work and configuration errors. ### Source excerpt Using the new fluent model config settings in Craft CMS 4.2 allows you to create better config files, with less work and fewer errors ## A Craft CMS Plugin Local Development Environment DevFeed: [A Craft CMS Plugin Local Development Environment]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2021-04-21T04:00:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [Docker](), [PHP](), [Development](), [Testing](), [phpstorm](), [MySQL](), [Database](), [Front end]() Tags: [article](), [cms](), [composer](), [containerized](), [craft](), [debug](), [details](), [develop](), [development](), [docker](), [ease](), [environment](), [frontend](), [insights](), [local](), [mysql](), [php](), [phpstorm](), [plugin](), [plugin-development](), [plugins](), [postgres](), [test]() ### AI overview This tutorial presents a portable, cross-platform Docker development environment for building, debugging, and testing Craft CMS plugins. It covers preconfigured PHP and database environments, testing content, PhpStorm and XDebug support, and plugin development setup. ### Source excerpt This article details a containerized local development environment that you can use to develop, debug, and test Craft CMS plugins with ease ## An Annotated Docker Config for Frontend Web Development DevFeed: [An Annotated Docker Config for Frontend Web Development]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2020-03-22T16:12:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Docker](), [Web Development](), [DevOps](), [Development](), [Docker Compose](), [Dockerfile]() Tags: [allows](), [apple-silicon](), [config](), [development](), [devops](), [docker](), [docker-compose](), [environment](), [frictionless](), [frontend](), [insights](), [local](), [making](), [multi-arch](), [needs](), [onboarding](), [project](), [shrink-wrap](), [web-development]() ### AI overview This tutorial explains how to use Docker as a local development environment for frontend web projects. It presents a reusable configuration approach that packages each application with the environment and service versions it needs, making environments reproducible, disposable, and easier to share. Examples reference Craft CMS, Laravel, NodeJS, and Rails, with multi-architecture base images available for Apple Silicon. ### Source excerpt A local development environment with Docker allows you to shrink-wrap the devops your project needs as config, making onboarding frictionless ## Flat Multi-Environment Config for Craft CMS 3 DevFeed: [Flat Multi-Environment Config for Craft CMS 3]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2020-02-29T15:29:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [.env](), [Environment Variables](), [configuration](), [Development]() Tags: [aliases](), [api-keys](), [approach](), [article](), [cms](), [config](), [configs](), [craft](), [database](), [docker](), [environment](), [environment-variables](), [file](), [files](), [flat](), [git](), [heroku](), [insights](), [multi-environment](), [need](), [presents](), [secrets](), [sorts](), [variables]() ### AI overview A tutorial on configuring Craft CMS 3 across development, staging, and production environments using aliases, environment variables, .env files, and configuration files. It presents a flat configuration approach and discusses keeping environment-specific credentials and secrets separate from source code and databases. ### Source excerpt Multi-environment configs for Craft CMS are a mix of aliases, environment variables, and config files. This article sorts it all out, and presents a flat config file approach ## Rails Console and Test Mode DevFeed: [Rails Console and Test Mode]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-02-19T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Rails](), [test](), [Testing]() Tags: [console](), [environment](), [factorybot](), [rails](), [selenium](), [test](), [testing]() ### AI overview This short tutorial shows how to launch the Rails console in test mode with RAILS_ENV=test rails c. This lets developers inspect the test environment and work directly with FactoryBot to experiment with test factories. ### Source excerpt This one is a short one but a good one. One really useful trick is to launch Rails console in test mode: ❯ RAILS_ENV=test rails c Running via Spring preloader in process 41705 Loading test environment (Rails 6.0.2.1) irb: warn: can't alias context from irb_context. You can check the Rails environment this way: 2.7.0 :001 > Rails.env "test" The benefit to this is that you can work directly with FactoryBot and experiment with factories: 2.7.0 :002 > project = FactoryBot.create(:project, name: "Scott's Project") FactoryBot is installed via Gemfile and locked into test environment only (which is why you need to launch Rails console in test mode): group :test do # Adds support for Capybara system testing and selenium driver gem "capybara", ">= 2.15" gem "selenium-webdriver" # Easy installation and use of web drivers to run system tests with browsers gem "webdrivers" gem 'factory_bot_rails' #gem 'database_cleaner' # gem 'shoulda' # gem 'shoulda-matchers' end ## Rails -- NoMethodError undefined method unpack1 for nil NilClass DevFeed: [Rails -- NoMethodError undefined method unpack1 for nil NilClass]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-01-26T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Rails](), [test](), [Encryption]() Tags: [blog](), [encryption](), [environment](), [errors](), [process](), [rails](), [test](), [tests]() ### AI overview A Rails test run fails with NoMethodError because Base64.decode64 receives nil from Rails.application.credentials.access_token_encryption_key. The article explains that the test environment credentials file must be created with EDITOR=vi rails credentials:edit --environment test. ### Source excerpt I recently started a new application and tried running the generated tests and got this: rails test test/models/user_test.rb Running via Spring preloader in process 27379 Run options: --seed 14413 # Running: E Error: UserTest#test_can_delete_user_with_teams: NoMethodError: undefined method `unpack1' for nil:NilClass app/models/user/connected_account.rb:37:in `' app/models/user/connected_account.rb:31:in `
' rails test test/models/user_test.rb:57 E Error: UserTest#test_user_has_a_personal_team: NoMethodError: undefined method `unpack1' for nil:NilClass app/models/user/connected_account.rb:37:in `' app/models/user/connected_account.rb:31:in `
' rails test test/models/user_test.rb:52 E Error: UserTest#test_user_has_many_teams: NoMethodError: undefined method `unpack1' for nil:NilClass app/models/user/connected_account.rb:37:in `' app/models/user/connected_account.rb:31:in `
' rails test test/models/user_test.rb:46 Finished in 0.060465s, 49.6155 runs/s, 0.0000 assertions/s. 3 runs, 0 assertions, 0 failures, 3 errors, 0 skips Now this is the the first time I've used test (as opposed to RSpec) in more than a decade and I was more than a bit taken aback. A quick Stack Overflow led me to: The error happens if you call Base64.decode64(nil). The method however is strictly expecting a String object here. Now the line of code in question is: attr_encrypted :access_token, key: Base64.decode64(Rails.application.credentials.access_token_encryption_key) So the implication is that: Rails.application.credentials.access_token_encryption_key is returning nil. The solution is actually pretty simple - create the credentials file using: EDITOR=vi rails credentials:edit --environment test See this blog post for why you have to use EDITOR=vi. ## Oxide Computer Company formed to build integrated hardware and software for on-premises infrastructure DevFeed: [Oxide Computer Company formed to build integrated hardware and software for on-premises infrastructure]() Original publisher: [Read original article]() Published: 2019-12-02T13:09:26Z Content type: opinion Language: en Sources: [Jessie Frazelle]() Topics: [Hardware](), [Software](), [Architecture & Design](), [cloud-infrastructure]() Tags: [docker](), [environment](), [go](), [hardware](), [infrastructure](), [kubernetes](), [latency](), [security](), [software]() ### AI overview The article announces the formation of Oxide Computer Company by Steve Tuck, Bryan Cantrill, and the author. The company aims to address the challenges of running infrastructure on premises by integrating hardware and software, with stated goals including better power distribution, density, and energy efficiency. ### Source excerpt WE STARTED A COMPUTER COMPANY!! You have no idea how long I've been waiting to say that! I guess some context would help... Steve Tuck, Bryan Cantrill, and I officially started the Oxide Computer Company. Since then, we've been working on closing up fundraising, getting an awesome office, and hiring! You are probably thinking "a computer company? that's outrageous!".. well it is and it isn't. Over the last year, I had the opportunity to spend a lot of time talking with folks who are currently running workloads on premises. The consensus from all my conversations has been that everyone setting up infrastructure themselves is in a great deal of pain and they have been largely neglected by any existing vendor. All these folks have very good reasons for running on premises that include security, strategic reasons like latency, specialized workloads, or the reality that the unit economics of running at their scale in the cloud are unsustainable. I've had the privilege of working on projects in my career that have had a positive impact on a lot of people - from Docker, to the Go programming language, to Kubernetes. Over the course of talking to folks, I soon realized that working on solving the pain for those running on premises would have a huge amount of impact. Hyperscalers like Facebook, Google, and Microsoft have what I like to call "infrastructure privilege" since they long ago decided they could build their own hardware and software to fulfill their needs better than commodity vendors. We are working to bring that same infrastructure privilege to everyone else! This leads to better integration between the hardware and software stacks, better power distribution, and better density. It's even better for the environment due to the energy consumption wins! I can't think of a better problem space and group of folks to work with to build a company. I've known both Bryan and Steve from the container conference circuit and couldn't pass up an opportunity to work with both of ## Postgres Connection Strings and psql DevFeed: [Postgres Connection Strings and psql]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2019-09-04T09:38:02Z Content type: tutorial Language: en Sources: [Dimitri Fontaine]() Topics: [PostgreSQL](), [Command-line interface](), [Terminal]() Tags: [cli](), [command-line](), [environment](), [postgres](), [postgresql](), [psql](), [terminal]() ### AI overview This short tutorial explains how PostgreSQL connection strings can use key-value notation, a URI scheme, or psql command-line options with environment variables. It shows that psql can accept a complete connection string, allowing developers to reuse an application's connection string at the console to test a database connection. ### Source excerpt PostgreSQL connection strings embedded in your application can take two different forms: the key-value notation or the postgresql:// URI scheme. When it comes to using psql though, another form of connection string is introduced, with command line options -h -p -U and environment variable support. In this short article you will learn that you can use either of the three different forms in psql and thus easily copy & paste you application connection string right at the console to test it! ## Mobile Testing & Local Dev Sharing with Homestead DevFeed: [Mobile Testing & Local Dev Sharing with Homestead]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2017-05-06T18:55:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Mobile Testing](), [Vagrant](), [Mobile](), [Development](), [OpenSSH](), [Scripting, bash]() Tags: [environment](), [fantastic](), [here-s](), [homestead](), [hood](), [insights](), [local](), [mobile](), [mobile-testing](), [ngrok](), [share](), [ssh](), [test](), [testing](), [vagrant-homestead](), [want]() ### AI overview A tutorial showing how to use Homestead's share command and Ngrok to expose a local development environment for colleagues or clients, and to test and debug local sites on mobile devices such as an iPhone. ### Source excerpt Homestead is a fantastic local dev environment, but what about when you want to test on mobile or share your local dev environment? Here's how ## On-Prem vs SaaS Information Security Compliance DevFeed: [On-Prem vs SaaS Information Security Compliance]() Original publisher: [Read original article]() Author: taylor@goteleport.com (Taylor Wakefield) Published: 2017-04-19T00:00:00Z Content type: opinion Language: en Sources: [Teleport]() Topics: [on-prem](), [Software as a service](), [Security](), [Shared Responsibility Model](), [Architecture & Design]() Tags: [article](), [blog](), [cloud](), [compliance](), [customers](), [data-center](), [delivery](), [environment](), [infrastructure](), [on-prem](), [operational](), [partnership](), [review](), [saas](), [security](), [support](), [vs](), [work]() ### AI overview This follow-up article examines the security and compliance implications of offering SaaS applications on-premises. Using a representative SaaS security compliance questionnaire as a framework, it argues that vendors should provide operational management while customers provide the infrastructure, a model the article calls Private SaaS. ### Source excerpt We review the Vendor Security Alliance's security questionnaire to look at the security ## Local Development with Vagrant / Homestead DevFeed: [Local Development with Vagrant / Homestead]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2017-03-31T07:59:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Vagrant](), [Provisioning](), [Web Development](), [Linux](), [Tooling](), [Software Engineering]() Tags: [allows](), [debugging](), [debugging-tools](), [development](), [effectively](), [environment](), [homestead](), [insights](), [linux](), [local](), [modern-web-development](), [projects](), [provisioning](), [safely](), [vagrant](), [vagrant-homestead](), [work]() ### AI overview This tutorial explains how Vagrant/Homestead provides a separate virtual machine for local web development. It discusses safer project workflows, isolated environments, production-like Linux systems, and pre-installed development and debugging tools. ### Source excerpt A local development environment with Vagrant/Homestead allows you to work on projects more safely and effectively ## Database & Asset Syncing Between Environments in Craft CMS DevFeed: [Database & Asset Syncing Between Environments in Craft CMS]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2016-12-06T08:41:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [Databases](), [Git](), [Development](), [MySQL]() Tags: [assets](), [cms](), [database](), [development](), [environment](), [environments](), [git](), [help](), [here-s](), [important](), [insights](), [it-s](), [maintenance](), [pain](), [syncing](), [workflow]() ### AI overview This tutorial presents a practical workflow for syncing Craft CMS databases and assets across local development, staging, and production environments. It recommends using Git for one-way code flow and limiting the approach to small- and mid-size projects where more elaborate replication or migration techniques may be excessive. ### Source excerpt Syncing the database & assets between environments is an important workflow, but it's a pain. Here's some help ## 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 ## Word 2010 support - Weekly report - Part 2: Installation (cont.) DevFeed: [Word 2010 support - Weekly report - Part 2: Installation (cont.)]() Original publisher: [Read original article]() Published: 2016-11-20T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Environment Variables](), [configuration](), [Software](), [Framework]() Tags: [environment](), [environment-variables](), [error](), [failed](), [framework](), [free](), [function](), [installation](), [open-source](), [os](), [react](), [reactos](), [report](), [software](), [win32](), [winapi]() ### AI overview This second weekly report examines Word 2010 installation on ReactOS. It describes missing environment variables affecting the OSPPSVC service, a failed MSI action with error 1603, and a workaround that allowed installation to finish while leaving the underlying failure unresolved. ### Source excerpt In this second report I continue my investigations on the Word 2010 installation. Last time we saw that our services (and in particular the "Office Software Protection Platform" OSPPSVC service) were started without a complete environment block, and as a result some needed environment variables were missing, causing e.g. OSPPSVC to fail opening some of its files. We now analyse what happens after my local fix (NOTE: I have not committed the fix yet, as I validate it in my local installation first). ## Changing the Linux Shell Prompt DevFeed: [Changing the Linux Shell Prompt]() Original publisher: [Read original article]() Published: 2011-06-30T00:00:00Z Content type: tutorial Language: en Sources: [Radek Pazdera]() Topics: [Bash](), [Shell](), [Linux](), [Scripting, bash](), [Command-line interface](), [Variable]() Tags: [bash](), [change](), [command](), [environment](), [how-to](), [linux](), [prompt](), [shell](), [value](), [variable]() ### AI overview A tutorial on customizing the Bash shell prompt on Linux by changing the prompt string environment variable. It explains prompt escape sequences, colors, temporary changes, and how to make the configuration permanent. ### Source excerpt How to modify your shell prompt on Linux