mfts

#!/bin/bash

adduser sdui
usermod -aG sudo sdui

apt update	
apt install ufw	
ufw allow OpenSSH	
ufw allow 10000/udp
ufw allow 4443/tcp

mfts

apt update

# install acme.sh
curl https://get.acme.sh | sh

# install heroku-cli
apt install snapd
sudo snap install --classic heroku
heroku login --interactive

mfts

{
  "environments": {
    "review": {
      "scripts": {
        "postdeploy": "bundle exec rake heroku:review_app_setup",
        "pr-predestroy": "bundle exec rake heroku:review_app_predestroy"
      }
    }
  }
}

mfts

distributable:
  url: https://example.org/download/{{version}}/src.tar.gz
  strip-components: 1

versions:
  - 1.0.0

build:
  script: |
    touch "{{prefix}}"/example

mfts

Helpful commands for tea/cli

Install tea/cli

sh <(curl https://tea.xyz)

Check currently installed stowed packages

ls ~/.tea

mfts

tea pantry overview

What is a Pantry?

Pantries provide consistent metadata about open source packages. This metadata shouldn’t require manual collection, but at this current state in open source it does.

It is collected and duplicated thousands of times. A huge waste of effort.

mfts

console.log("%cHappy New Year from @mfts0 🎉", "color: red");

mfts

Motivation

One of the core benefits of tea: it's relocatable. tea does not pollute your system environment, everything gets "installed" in a relocatable folder ~/.tea.

tea can also install languages like node and ruby and it's dependency managers, npm and gem, respectively. However, these language dependency managers install packages to global directories like ~/.npm and ~/.gem. Tools from these ecosystems expect to find packages in these locations.

In this RFC, we would love to hear feedback from the community.