{"id":13539749,"url":"https://github.com/cloudposse/geodesic","last_synced_at":"2025-05-14T19:07:59.593Z","repository":{"id":37982918,"uuid":"75686762","full_name":"cloudposse/geodesic","owner":"cloudposse","description":"🚀 Geodesic is a DevOps Linux Toolbox in Docker","archived":false,"fork":false,"pushed_at":"2025-05-05T01:57:05.000Z","size":10532,"stargazers_count":1017,"open_issues_count":7,"forks_count":122,"subscribers_count":31,"default_branch":"main","last_synced_at":"2025-05-05T02:24:56.187Z","etag":null,"topics":["alpine","aws","containers","devops","docker","dockerfile","ec2","elasticbeanstalk","helm","helmfile","infrastructure-as-code","infrastructure-management","k8s","kops","kubectl","kubernetes","kubernetes-cluster","shell","terraform","toolbox"],"latest_commit_sha":null,"homepage":"https://cloudposse.com/accelerate","language":"Shell","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/cloudposse.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":".github/CODEOWNERS","security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null},"funding":{"github":"cloudposse"}},"created_at":"2016-12-06T02:31:57.000Z","updated_at":"2025-05-05T01:16:24.000Z","dependencies_parsed_at":"2024-02-03T05:28:16.525Z","dependency_job_id":"a0749a55-3367-4cbb-835d-5fc2527237fd","html_url":"https://github.com/cloudposse/geodesic","commit_stats":{"total_commits":651,"total_committers":29,"mean_commits":"22.448275862068964","dds":0.7311827956989247,"last_synced_commit":"a42555c6a07b582afec641d4b5eda4a821c886cf"},"previous_names":[],"tags_count":470,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cloudposse%2Fgeodesic","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cloudposse%2Fgeodesic/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cloudposse%2Fgeodesic/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cloudposse%2Fgeodesic/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/cloudposse","download_url":"https://codeload.github.com/cloudposse/geodesic/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":254209859,"owners_count":22032897,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["alpine","aws","containers","devops","docker","dockerfile","ec2","elasticbeanstalk","helm","helmfile","infrastructure-as-code","infrastructure-management","k8s","kops","kubectl","kubernetes","kubernetes-cluster","shell","terraform","toolbox"],"created_at":"2024-08-01T09:01:31.386Z","updated_at":"2025-05-14T19:07:58.051Z","avatar_url":"https://github.com/cloudposse.png","language":"Shell","readme":"\n\n\u003c!-- markdownlint-disable --\u003e\n\u003ca href=\"https://cpco.io/homepage\"\u003e\u003cimg src=\"https://github.com/cloudposse/geodesic/blob/main/.github/banner.png?raw=true\" alt=\"Project Banner\"/\u003e\u003c/a\u003e\u003cbr/\u003e\n    \u003cp align=\"right\"\u003e\n\u003ca href=\"https://github.com/cloudposse/geodesic/actions?query=workflow%3Adocker\"\u003e\u003cimg src=\"https://github.com/cloudposse/geodesic/workflows/docker/badge.svg\" alt=\"Build Status\"/\u003e\u003c/a\u003e\u003ca href=\"https://github.com/cloudposse/geodesic/releases/latest\"\u003e\u003cimg src=\"https://img.shields.io/github/release/cloudposse/geodesic.svg\" alt=\"Latest Release\"/\u003e\u003c/a\u003e\u003ca href=\"https://slack.cloudposse.com\"\u003e\u003cimg src=\"https://slack.cloudposse.com/badge.svg\" alt=\"Slack Community\"/\u003e\u003c/a\u003e\u003ca href=\"https://archive.sweetops.com/geodesic\"\u003e\u003cimg src=\"https://img.shields.io/badge/slack-archive-blue.svg\" alt=\"Slack Archive\"/\u003e\u003c/a\u003e\u003c/p\u003e\n\u003c!-- markdownlint-restore --\u003e\n\n\u003c!--\n\n\n\n\n  ** DO NOT EDIT THIS FILE\n  **\n  ** This file was automatically generated by the `cloudposse/build-harness`.\n  ** 1) Make all changes to `README.yaml`\n  ** 2) Run `make init` (you only need to do this once)\n  ** 3) Run`make readme` to rebuild this file.\n  **\n  ** (We maintain HUNDREDS of open source projects. This is how we maintain our sanity.)\n  **\n\n\n\n\n\n--\u003e\n\nGeodesic is a robust Linux toolbox container, crafted to optimize DevOps workflows.\nThis container comes loaded with essential dependencies for a DevOps toolchain.\nIt's designed to bring consistency and boost efficiency across development environments.\nIt achieves this without the need for installing additional software on your workstation.\nThink of Geodesic as a containerized parallel to Vagrant, offering similar functionality within a Docker container context.\n\nAlthough Geodesic is packed with essentials, it is designed to be extended and customized to suit your specific needs.\nCreate your own Dockerfile based on Geodesic and add your favorite tools to the mix.\nThen share the resulting container with everyone on your team to ensure everyone is working in the same environment.\n\u003cimg align=right src=\"docs/geodesic-small.png\"\u003e\n\n## Key Features\n\n- **Unified Toolchain**: By packaging all necessary DevOps tools and dependencies, Geodesic eliminates the \"works on my machine\" problem, ensuring toolchain uniformity across different machines.\n- **Consistent Environment**: Geodesic guarantees that every developer operates in a uniform OS environment with consistent tool versions, sidestepping discrepancies that often arise in diverse development setups.\n- **Quick Start for New Developers**: It streamlines the onboarding process for new team members, allowing them to bypass lengthy workstation configurations and dive straight into productivity.\n- **Cross-Platform Compatibility**: With native support for Mac OSX, Linux, and [Windows (via WSL)](https://docs.microsoft.com/en-us/windows/wsl/install-win10), Geodesic extends its versatile toolchain to a wide range of operating systems, ensuring broad accessibility and functionality.\n- **Version Control for Tools**: Geodesic facilitates easy versioning of tools for different environments, enabling repeatable setups and minimizing compatibility issues.\n- **Reusable Base Image for Toolboxes**: Empower teams to create and maintain consistent toolbox images, ensuring a standardized development environment across the board.\n\n## Screenshots\n\n\u003cimg src=\"docs/demo.gif\" alt=\"Demo\" /\u003e*\u003cbr/\u003eExample of running a shell based on the `cloudposse/geodesic` base docker image.*\n\n\n\n\n## Introduction\n\nThese days, the typical software application is distributed as a docker image and run as a container. Why should infrastructure be any different? Since everything we write is \"Infrastructure as Code\", we believe that it should be treated the same way. This is the \"Geodesic Way\". Use containers+envs instead of unconventional wrappers, complicated folder structures and symlink hacks. Geodesic is the container for all your infrastructure automation needs that enables you to truly achieve SweetOps.\n\nGeodesic is best used in one of these two ways:\n\n  1. **Interactive Shell** It is optimized to work as an interactive command-line shell.\n     The shell includes a powerful set of tools for the DevOps practitioner, with many more available through our [packages](https://github.com/cloudposse/packages). Installation of the shell is as easy as running a docker container or using it as a base image for your own Docker toolbox.\n  2. **Docker Base Image** You can create your own `Dockerfile` and use `cloudposse/geodesic` as the base image.\n     This way, all you need to add are the few of your favorite tools not already installed, and then you have a consistent toolbox for everyone to share.\n\nAn organization may chose to leverage all of these components, or just the parts that make their life easier.\n\nWe recommend starting by using `geodesic` as a Docker base image (e.g. `FROM cloudposse/geodesic:...` pinned to a release and base OS) in your projects.\n\n\u003e [!IMPORTANT]\n\u003e **Note**: Starting with Geodesic 3.0, we distribute Geodesic as a multi-platform (`linux/amd64`, `linux/arm64`) Debian-based Docker image only.\n\u003e We no longer publish an Alpine version, but continue to include the `debian` labels for compatibility. As with Geodesic 2.0, the `latest` tag points to the Debian image.\n\u003e\n\u003e Starting with Geodesic 2.0, we distributed Geodesic as a multi-platform (`linux/amd64`, `linux/arm64`) Debian-based Docker image and a single-platform (`linux/amd64`) Alpine-based image.\n\u003e We moved the `cloudposse/geodesic:latest` Docker image tag from the Alpine version to the Debian version at that time.\n\n\n### What’s Changed in Geodesic 4.0\n\nGeodesic 4.0 is a major release that brings many new features and improvements. The most notable changes are:\n\n- The first launched shell is no longer special. All shells are now equal, and you can quit them in any order.\n  The geodesic container remains running until the last shell exits.\n- The `geodesic` command now has a `--solo` option that allows you to launch a new Geodesic container for just that one shell.\n- Geodesic no longer mounts the host user's entire home directory into the container. Instead, it mounts only selected directories.\n- The `geodesic stop` command has been enhanced to shut down the Geodesic container gracefully, rather than forcefully, allowing,\n  among other things, shell scripts to run their exit handlers.\n\nSee extensive release notes for Geodesic 4.0 [here](ReleaseNotes-v4.md).\n\n### What’s Changed in Geodesic 3.0\n\nRather than bringing new features, Geodesic 3.0 is focused on slimming down the Docker image and removing outdated tools.\nGeodesic 3.0 is approximately half the size of Geodesic 2.10!\nSee the [v3.0.0 release notes](https://github.com/cloudposse/geodesic/releases/tag/3.0.0)\nfor details on what was removed, but for most users, we expect the impact to be minimal.\n\nThis release is intended to set the stage for future improvements, so although we cannot announce a time frame,\nbe on the lookout for Geodesic 4.0, which will bring many long-requested new features.\n\nWant to learn more? [Check out our getting started with Geodesic guide!](https://docs.cloudposse.com/tutorials/geodesic-getting-started/)\n\n#### Alpine and Terraform dropped\n\nThe biggest impacts are that the Alpine-based image has been dropped, and Terraform has been replaced with OpenTofu.\n\n- OpenTofu is installed as a `terraform` alternative using the [Debian alternatives system](https://wiki.debian.org/DebianAlternatives),\n  so `terraform` commands will still work without modification.\n- We have been encouraging users to switch from Alpine to Debian for years, so we hope most people have already done so.\n  For the rest, switching to Debian should be straightforward, and brings the added advantage of support for Apple Silicon.\n\n#### Highlights from Geodesic 2.11\n\nSince the release of Geodesic 2.0, we have been continuing to improve the Geodesic experience.\n\n- We have added preliminary support for \"dark mode\" terminals. Your terminal mode should be detected automatically,\n  but you can force it by running `update-terminal-mode {dark|light}`.\n- The `GEODESIC_TF_PROMPT_ENABLED` environment variable has been revived. Set it to `true` and when in a Terraform\n  or Tofu directory, the prompt will display the currently selected workspace. (We had, for a time, incorrectly suggested\n  you control this feature via `GEODESIC_TF_PROMPT_ACTIVE`. That environment variable is for internal use and you should\n  never set it.)\n\n### What’s New in Geodesic 2.0\n\nGeodesic 2.0 introduces support for Apple Silicon (M1 and later chips), and prioritizes Debian over Alpine as the base OS.\nUsers new to Geodesic should use the Debian-based version and existing users of the Alpine-based image should switch to\nthe Debian-based image as soon as is convenient. They each have nearly all the same tools pre-installed, so switching\nis mainly a matter of updating how you customize it, replacing Alpine packages with Debian packages.\n\nIn order for a tool to be included in Geodesic 2.0, it must be available as both a `linux/amd64` and `linux/arm64` binary.\n(In exceptional cases, if a tool is written in the `go` language and distributes source code only, Cloud Posse may build the needed binaries.)\nA few tools that were in Geodesic 1.0 had not yet been updated to provide `linux/arm64` binaries and were omitted from Geodesic 2.0.\n(See the Geodesic 2.0 [Release Notes](https://github.com/cloudposse/geodesic/releases/tag/2.0.0)\nfor details on which tools were removed.)\n\n### Docker Tags and Their Evolution\n\nGeodesic Docker images are tagged with `VERSION-BASE_OS`, e.g. `2.0.0-debian` or `2.0.0-alpine`.\nThe `latest` tag points to the latest Debian-based image, although we recommend pinning to a specific version.\n\n- Prior to Geodesic 2.0, the `latest` tag pointed to the latest Alpine-based image.\n- Prior to Geodesic 0.138.0, all Docker images were based on Alpine only and simply tagged `VERSION`.\n\n\n\n\n## Usage\n\n### Quickstart\n\n#### Installing Geodesic\n\nLaunching Geodesic is a bit complex, so we recommend you install a launch script by running\n```\ndocker run --rm cloudposse/geodesic:latest-debian init | bash\n```\nAfter that, you should be able to launch Geodesic just by typing\n```\ngeodesic\n```\n\nAlternately, customize the Makefile as described below and use `make install` to build your custom image\nand install the launch script.\n\n#### Running Geodesic\n\nGeodesic has only a few commands and command-line options. The most important command is `geodesic`, which launches the Geodesic shell.\nThe only other command you might normally use is `geodesic stop`, which stops the Geodesic container, but\nGeodesic automatically quits (and removes the Docker container) when you exit the last shell, so you should rarely need to use `geodesic stop`.\n\nRun `geodesic help` for a list of command-line options.\n\nSee [customization](/docs/customization.md) documentation for information on how to customize your Geodesic environment.\nGeodesic has many customization options, but they are most commonly set in configuration files, not on the command line.\n\n### Customizing your Docker image\n\nIn general we recommend creating a customized version of Geodesic by creating your own `Dockerfile` starting with\n```\n# We always recommend pinning versions to avoid surprises and breaking changes.\n# We put the version up top here so it is easy to find and update.\n# Find the latest version at https://github.com/cloudposse/geodesic/releases\nARG VERSION=4.0.0\n# If you don't want to bothered with updating the version, you can use `latest` instead,\n# but keep in mind that as long as you have a local image with the `latest` tag,\n# it will not be updated by `docker run`. You will have to explicitly pull the latest image.\n# ARG VERSION=latest\nARG OS=debian\nFROM cloudposse/geodesic:$VERSION-$OS\n\n# Add configuration options such as setting a custom BANNER,\n# setting the initial AWS_PROFILE and AWS_DEFAULT_REGION, etc. here\n\nENV BANNER=\"my-custom-geodesic\"\n```\n\nYou can see some example configuration options to include in [Dockerfile.options](./Dockerfile.options).\n\n#### Makefile customizations\n\nWe also recommend creating a `Makefile` to simplify building and running your custom image.\nYou can use the [Makefile](/Makefile) in this repository with minimal modifications.\n\n- Update `DOCKER_ORG` and `DOCKER_IMAGE` to match your Docker Hub username and the name of your custom image.\n- Update `DOCKER_FILE` to match the path to your custom `Dockerfile`.\n- Update `APP_NAME` to give the command to launch your custom image a custom name.\n\nThen you can build your custom image with `make build` and run it with `make run`.\n\n#### Multi-platform gotchas\n\nAlthough the Geodesic base image is provided in 2 architectures, when you do a local build\nof your custom image, it will, by default, only be built for the architecture of the machine you are building on.\nThis is fine until you want to share it. You need to be aware that if you push just the image you\nbuilt with `docker build` you will only be supporting a single architecture. You should use `docker buildx`\nto build a multi-platform image and push it to a Docker repository for sharing.\n\nIf you intend to support both architectures, you need to be sure that any customizations\nyou install are properly installed for both architectures. Package managers handle this for you\nautomatically, but if you are downloading files directly, you need to be careful to select the right one.\nSee the use of `TARGETARCH` in [Dockerfile.debian](./os/debian/Dockerfile.debian) for some examples.\n\n#### Installing extra packages\n\nYou can also add extra commands by installing \"packages\".\n- Debian has a large selection of packages to choose from.\n- Cloud Posse also provides a large set of packages for installing common DevOps commands\nand utilities via [cloudposse/packages](https://github.com/cloudposse/packages).\n- Google Cloud provides a set of packages for working with GCP\n- OpenTofu provides a packge for installing it, too.\n\nThose package repositories are pre-installed in Geodesic, so\nall you need to do is add the packages you want via\n\n```Dockerfile\nRUN apt-get update \u0026\u0026 apt-get install -y \u003cpackage-name\u003e...\n```\ncommands in your Dockerfile. The package manager will automatically select the correct architecture for the package.\n\n#### Pinning package versions in Debian\n\nDebian uses [`apt`](https://wiki.debian.org/Apt) for package management and we generally recommend using\nthe [`apt-get`](https://www.debian.org/doc/manuals/apt-guide/ch2.en.html) command to install packages.\nHowever, `apt-get` does not let you specify a version range on the command line, but it does\nallow wildcards. Package versions include a release number (typically \"1\") at the end, to allow for\nupdated packages when there is a bug in the package itself. Therefore, best practice is to use a wildcard\nfor the release number when specifying a package version. For example,\nto install the Google Cloud SDK at a version 300.0.0:\n\n```dockerfile\nRUN apt-get update \u0026\u0026 apt-get install -y google-cloud-sdk=\"400.0.0-*\"\n```\n\nNote the `-y` flag to `apt-get install`. That is required for scripted installation, otherwise the command\nwill ask for confirmation from the keyboard before installing a package.\n\nUnfortunately, OpenTofu does not follow this convention, so you will need to specify the exact version number\n(only) when installing OpenTofu. For example, to install OpenTofu version 1.6.2:\n\n```dockerfile\nRUN apt-get update \u0026\u0026 apt-get install -y tofu=1.6.2\n```\n\n### Customizing your shell at launch time\n\nAfter you have built your Docker image, or if you are using a shared Docker image, you can\nadd further customization at launch time. When Geodesic starts up, it looks for customization\nscripts and configuration so you can do things like add command aliases or override preconfigured options.\nDetailed information about launch-time configuration is in the [customization](./docs/customization.md)\ndocument, available from within the shell via `man customization`.\n\n\n\n\n\n\n\n\n## Related Projects\n\nCheck out these related projects.\n\n- [Atmos](https://atmos.tools/) - Cloud Posse's FOSS DevOps Automation Tool\n- [Packages](https://github.com/cloudposse/packages) - Cloud Posse installer and distribution of native apps\n- [terraform-aws-components](https://github.com/cloudposse/terraform-aws-components) - Catalog of reusable Terraform components and blueprints for provisioning reference architectures\n\n\n\n## ✨ Contributing\n\nThis project is under active development, and we encourage contributions from our community.\n\n\n\nMany thanks to our outstanding contributors:\n\n\u003ca href=\"https://github.com/cloudposse/geodesic/graphs/contributors\"\u003e\n  \u003cimg src=\"https://contrib.rocks/image?repo=cloudposse/geodesic\u0026max=24\" /\u003e\n\u003c/a\u003e\n\nFor 🐛 bug reports \u0026 feature requests, please use the [issue tracker](https://github.com/cloudposse/geodesic/issues).\n\nIn general, PRs are welcome. We follow the typical \"fork-and-pull\" Git workflow.\n 1. Review our [Code of Conduct](https://github.com/cloudposse/geodesic/?tab=coc-ov-file#code-of-conduct) and [Contributor Guidelines](https://github.com/cloudposse/.github/blob/main/CONTRIBUTING.md).\n 2. **Fork** the repo on GitHub\n 3. **Clone** the project to your own machine\n 4. **Commit** changes to your own branch\n 5. **Push** your work back up to your fork\n 6. Submit a **Pull Request** so that we can review your changes\n\n**NOTE:** Be sure to merge the latest changes from \"upstream\" before making a pull request!\n\n### 🌎 Slack Community\n\nJoin our [Open Source Community](https://cpco.io/slack?utm_source=github\u0026utm_medium=readme\u0026utm_campaign=cloudposse/geodesic\u0026utm_content=slack) on Slack. It's **FREE** for everyone! Our \"SweetOps\" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally *sweet* infrastructure.\n\n### 📰 Newsletter\n\nSign up for [our newsletter](https://cpco.io/newsletter?utm_source=github\u0026utm_medium=readme\u0026utm_campaign=cloudposse/geodesic\u0026utm_content=newsletter) and join 3,000+ DevOps engineers, CTOs, and founders who get insider access to the latest DevOps trends, so you can always stay in the know.\nDropped straight into your Inbox every week — and usually a 5-minute read.\n\n### 📆 Office Hours \u003ca href=\"https://cloudposse.com/office-hours?utm_source=github\u0026utm_medium=readme\u0026utm_campaign=cloudposse/geodesic\u0026utm_content=office_hours\"\u003e\u003cimg src=\"https://img.cloudposse.com/fit-in/200x200/https://cloudposse.com/wp-content/uploads/2019/08/Powered-by-Zoom.png\" align=\"right\" /\u003e\u003c/a\u003e\n\n[Join us every Wednesday via Zoom](https://cloudposse.com/office-hours?utm_source=github\u0026utm_medium=readme\u0026utm_campaign=cloudposse/geodesic\u0026utm_content=office_hours) for your weekly dose of insider DevOps trends, AWS news and Terraform insights, all sourced from our SweetOps community, plus a _live Q\u0026A_ that you can’t find anywhere else.\nIt's **FREE** for everyone!\n## License\n\n\u003ca href=\"https://opensource.org/licenses/Apache-2.0\"\u003e\u003cimg src=\"https://img.shields.io/badge/License-Apache%202.0-blue.svg?style=for-the-badge\" alt=\"License\"\u003e\u003c/a\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003ePreamble to the Apache License, Version 2.0\u003c/summary\u003e\n\u003cbr/\u003e\n\u003cbr/\u003e\n\nComplete license is available in the [`LICENSE`](LICENSE) file.\n\n```text\nLicensed to the Apache Software Foundation (ASF) under one\nor more contributor license agreements.  See the NOTICE file\ndistributed with this work for additional information\nregarding copyright ownership.  The ASF licenses this file\nto you under the Apache License, Version 2.0 (the\n\"License\"); you may not use this file except in compliance\nwith the License.  You may obtain a copy of the License at\n\n  https://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing,\nsoftware distributed under the License is distributed on an\n\"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY\nKIND, either express or implied.  See the License for the\nspecific language governing permissions and limitations\nunder the License.\n```\n\u003c/details\u003e\n\n## Trademarks\n\nAll other trademarks referenced herein are the property of their respective owners.\n\n\n---\nCopyright © 2017-2025 [Cloud Posse, LLC](https://cpco.io/copyright)\n\n\n\u003ca href=\"https://cloudposse.com/readme/footer/link?utm_source=github\u0026utm_medium=readme\u0026utm_campaign=cloudposse/geodesic\u0026utm_content=readme_footer_link\"\u003e\u003cimg alt=\"README footer\" src=\"https://cloudposse.com/readme/footer/img\"/\u003e\u003c/a\u003e\n\n\u003cimg alt=\"Beacon\" width=\"0\" src=\"https://ga-beacon.cloudposse.com/UA-76589703-4/cloudposse/geodesic?pixel\u0026cs=github\u0026cm=readme\u0026an=geodesic\"/\u003e\n","funding_links":["https://github.com/sponsors/cloudposse"],"categories":["Shell","aws","Tools"],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcloudposse%2Fgeodesic","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fcloudposse%2Fgeodesic","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcloudposse%2Fgeodesic/lists"}