https://github.com/andrewchambers/hermes

Hermes software environment manager
https://github.com/andrewchambers/hermes

deployment-automation package-manager

Last synced: 1 day ago
JSON representation

Hermes software environment manager

• Host: GitHub
• URL: https://github.com/andrewchambers/hermes
• Owner: andrewchambers
• License: mit
• Created: 2020-03-12T05:42:30.000Z (over 4 years ago)
• Default Branch: master
• Last Pushed: 2020-06-06T01:41:03.000Z (over 4 years ago)
• Last Synced: 2024-08-04T04:01:06.354Z (3 months ago)
• Topics: deployment-automation, package-manager
• Language: C
• Homepage:
• Size: 396 KB
• Stars: 311
• Watchers: 13
• Forks: 8
• Open Issues: 41
• Metadata Files:
  • Readme: README.md
  • License: LICENSE
  • Support: support/dev-env.hpkg

Awesome Lists containing this project

• awesome-janet - hermes

README

        
# Hermes

Hermes is a software environment manager used for installing and uninstalling

collections of software. Hermes may be considered similar to a package manager, but certainly

works quite differently from traditional tools in this space.

Hermes helps with tasks similar to other tools like [homebrew](https://brew.sh/)

or perhaps [docker](https://www.docker.com/), but in a totally different way. For those who know

[Nix](https://nixos.org/) and [Guix](https://guix.gnu.org/), things will be familiar, but

there are also some [key differences](./doc/compared-to-nix-and-guix.md).

## So what does it do?

When using Hermes your *entire* software stack is defined and saved in a set of

package definitions along side the rest of your source code. This means Hermes

gives you strict reproducible control over your entire software stack. With

a single command you can reliably (and quickly) rebuild a development environment,

deployment, docker image or vm image *entirely* from source.

With Hermes you can also share, review, clone, fork, patch and pin your whole software stack

the same way you do with your existing source code.

Hermes also provides some nifty features:

* A decentralized packaging model.

* Easy installation of software over URLS.

* Easy transfer of software environments between computers.

* Avoidance of version conflicts with already installed software.

* Installing software from source code.

* Strong support for software auditability.

* Transparent build caching.

* Remote package builds.

* Remote deployments.

* Atomic upgrades and rollback.

* and more...

## What does using Hermes look like?

- See my annoucement [blog post](https://acha.ninja/blog/introducing_hermes/).

- See the [quickstart guide](./doc/quick-start/quick-start.md).

- Browse some package definitions [here](https://github.com/andrewchambers/hpkgs).

## Does Hermes replace my language package manager like npm,jpm,cargo,pip... ?

No.

Hermes can be used to manage the system level dependencies during software

development while still using these tools normally. For example you could install

a specific C compiler and libcurl with hermes, but just invoke npm as normal for your

javascript project.

During deployment of your software you can invoke these tools from within

package definitions to build your software in a well defined sandbox.

These packages can then be deployed to remote machines using 'hermes cp'.

## Does Hermes replace my system package manager?

Maybe.

Hermes packages are totally separate from your system packages. When you enter

a hermes environment, your PATH and other environment variables are set to paths

within the hermes package store.

Hermes does not care what other package managers you use, and does not install

packages in the traditional ```/bin``` path so will not conflict with them.

## How can you help?

- Give hermes and hpkgs a star on github.

- [Donate](https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=JX43FQRV6H7XW&source=url) to

  the project to keep it sustainable and show interest.