Results for container-terminal

Uses nsenter to provide a terminal to a Docker container. Looks and feels like an ssh client.

Durable Dockerpage provides a terminal user interface for managing Docker containers

Appear is a tool for revealing a given process in your terminal. Given a process ID, `appear` finds the terminal emulator view (be it a window, tab, or pane) containing that process and shows it to you. Appear understands terminal multiplexers like `tmux`, so if your target process is in a multiplexer session, `appear` will reveal a client connected to that session, or start one if needed. This project intends to support all POSIX operating systems eventually, but currently only supports macOS.

A terminal command for running logic-less project templates. Templates are just git repositories whose files and directories are copied to the working directory when run. Directory names, file names, and file content can contain Mustache tags - the values of which are prompted for in the terminal and substituted when the template is run.

This gem allows you to analyze an input file (contains several terminal commands and output related to files and directories) and finally detect all directories candidate for deletion based on the maximum size.

Are you an OS X prefnerd? Do you keep a base set of OS X preferences in version control to make it easier to set up new machines? Do you want to know which items are being changed, and to what values, whenever you alter a setting on OS X? The prefnerd gem contains a simple executable that watches the defaults database for changes and prints them to your terminal.

'Sith-Lord, Jedi, Ewok' is a game targeting younger audiences who may not have grown up playing 'Scissors, Paper, Rock', but will also more broadly appeal to fans of the Star Wars franchise. *NB! The gem installation currently contains pathing errors when running the gem. To run the application, download source code from https://github.com/waldowred5/T1A3-Terminal-App, and then run the following command* `sith_jedi_ewok` in terminal from the following directory: `/Users/[user_name]/T1A3-Terminal-App/src/sith_jedi_ewok` To download all dependencies, run `bundle install` in the same directory. "If importing to your own application, add this line to your application's Gemfile:" `gem 'Sith-Lord_Jedi_Ewok'` And then execute: $ bundle install Or install it yourself as: $ gem install Sith-Lord_Jedi_Ewok

A minimal, self-contained bash dashboard for monitoring a home media server. Displays service health, disk usage, active Plex streams, download speed, uptime, and quick-access links in a single terminal window.

Inquirex lets you define multi-step questionnaires as directed graphs with conditional branching, using a conversational DSL (ask, say, mention) and an AST-based rule system (contains, equals, greater_than, all, any). The engine walks the graph, collects structured answers, and serializes everything to JSON — making it the ideal backbone for cross-platform intake forms where the frontend is a chat widget, a terminal, or a mobile app. Framework-agnostic, zero dependencies, thread-safe immutable definitions.

go (to project) do (stuffs) godo provides a smart way of opening a project folder in multiple terminal tabs and, in each tab, invoking a commands appropriate to that project. For example if the folder contains a Rails project the actions might include: starting mongrel, tailing one or more logs, starting consoles or IRB sessions, tailing production logs, opening an editor, running autospec, or gitk. godo works by searching your project paths for a given search string and trying to match it against paths found in one or more configured project roots. It will make some straightforward efforts to disambiguate among multiple matches to find the one you want. godo then uses configurable heuristics to figure out what type of project it is, for example "a RoR project using RSpec and Subversion". From that it will invokes a series of action appropriate to the type of project detected with each action being run, from the project folder, in its own terminal session. godo is entirely configured by a YAML file (~/.godo) that contains project types, heuristics, actions, project paths, and a session controller. A sample configuration file is provided that can be installed using godo --install. godo comes with an iTerm session controller for MacOSX that uses the rb-appscript gem to control iTerm (see lib/session.rb and lib/sessions/iterm_session.rb). It should be relatively straightforward to add new controller (e.g. for Leopard Terminal.app), or a controller that works in a different way (e.g. by creating new windows instead of new tabs). There is nothing MacOSX specific about the rest of godo so creating controllers for other unixen should be straightforward if they can be controlled from ruby. godo is a rewrite of my original 'gp' script (http://matt.blogs.it/entries/00002674.html) which fixes a number of the deficiencies of that script, turns it into a gem, has a better name, and steals the idea of using heuristics to detect project types from Solomon White's gp variant (http://onrails.org/articles/2007/11/28/scripting-the-leopard-terminal). godo now includes contributions from Lee Marlow <lee.marlow@gmail.com> including support for project level .godo files to override the global configuration, support for Terminal.app, and maximum depth support to speed up the finder. godo lives at the excellent GitHub: http://github.com/mmower/godo/ and accepts patches and forks.

pikuri-workspace adds "operate on a directory tree" to pikuri-core agents: the +Pikuri::Workspace::Filesystem+ class that scopes filesystem access to an anchor + explicit readable / writable prefix lists (with optional ephemeral temp playground), the +Pikuri::Workspace::Confirmer+ seam (+AUTO_APPROVE+ + +TERMINAL+) for user-state mutations, and five tools wired to those seams: +Pikuri::Workspace::Read+, +Pikuri::Workspace::Write+, +Pikuri::Workspace::Edit+, +Pikuri::Workspace::Grep+, and +Pikuri::Workspace::Glob+. Self-contained — no shell execution; +Pikuri::Code::Bash+ ships in pikuri-code on top of these.

# Studio Game Studio Game is a Ruby-based project that demonstrates object-oriented programming concepts. It includes classes and modules to manage players, games, and scoring. ## Project Structure - `lib/`: Contains the core Ruby files for the game logic. - `game.rb`: Defines the main game class. - `player.rb`: Manages player attributes and behaviors. - `treasure_trove.rb`: Handles treasures and their values. - `bin/`: Contains executable scripts to run the game. - `studio_game`: The main entry point to start the game. - `spec/`: Contains unit tests for the game. - `game_spec.rb`: Tests for the game class. - `player_spec.rb`: Tests for the player class. - `README.md`: Project documentation. - `LICENSE`: MIT License file. ## How to Run 1. Clone the repository. 2. Navigate to the `studio_game` directory. 3. Run the game using: ```bash ruby bin/studio_game ``` ## Testing To ensure the game logic works as expected, run the unit tests included in the `spec/` directory. Use the following command: ```bash rspec spec/ ``` This will execute all the test files and display the results in the terminal.

No description provided.