Sign inSign up

weaponsforge/gemini-cli

By weaponsforge

Updated about 1 year ago

Gemini CLI image with directories and .env config setup

Image
Developer tools
1

1.2K

weaponsforge/gemini-cli repository overview

gemini-cli

This repository contains Docker files and recommended configurations for a quick and minimal setup of the Google Gemini CLI, installing it in an isolated container to avoid direct installation in a host machine.

This image is only for local development purposes.

GitHub Repository
https://github.com/weaponsforge/gemini-cli

Requirements

  1. Docker
  2. Google Gemini API Key

Usage

  1. Pull the "latest" development image.
    docker pull weaponsforge/gemini-cli

  2. Create a .env file from the .env.example file. Replace the value of the GEMINI_API_KEY with your own Google Gemini API key.

  3. Copy existing projects into sub-directories following the basic projects folder structure. It requires having the sub-project directories inside the /projects directory in the host machine, e.g.,

    ├─ .env
    ├─ projects
    │   ├─ my-app
    │   ├─ cool-website
    │   ├─ my-portfolio
    │   ├─ ...
    

    WARNING: Avoid including the sub-projects' installation dependencies (e.g., /node_modules) to minimize the number of files/codes reflected in the Docker container (since it uses bind-mount.)

  4. Run the development image.
    Navigate to the parent directory that contains the "project" directory and the .env file using a terminal, then run:

    # Using PowerShell
    docker run -it -v ${pwd}/projects:/opt/app/projects --env-file .env --rm weaponsforge/gemini-cli gemini
    

    TIPS:

    • Refer to the project's GitHub README file for detailed usage information

Tag summary

Content type

Image

Digest

sha256:3b109c8b3

Size

118.9 MB

Last updated

about 1 year ago

docker pull weaponsforge/gemini-cli