Takeout is a CLI tool for spinning up tiny Docker containers, one for each of your development environment dependencies.
It's meant to be paired with a tool like Laravel Valet. It's currently compatible with macOS, Linux, Windows 10 and WSL2.
With takeout enable mysql
you're running MySQL, and never have to worry about managing or fixing Homebrew MySQL again.
But you can also easily enable ElasticSearch, PostgreSQL, MSSQL, Mongo, Redis, and more, with a simple command. For a current list of services, look at the classes available in this directory: https://github.com/tighten/takeout/tree/main/app/Services
Install Takeout with Composer by running:
composer global require tightenco/takeout
Make sure the ~/.composer/vendor/bin
directory is in your system's "PATH".
Run takeout
and then a command name from anywhere in your terminal.
One of Takeout's primary benefits is that it boots ("enables") or deletes ("disables") Docker containers for your various dependencies quickly and easily.
Because Docker offers persistent volume storage, deleting a container (which we call "disabling" it) doesn't actually delete its data. That means you can enable and disable services with reckless abandon.
Show a list of all services you can enable.
takeout enable
Passed the short name of one or more services, enable them.
takeout enable mysql
takeout enable redis meilisearch
If you want to skip over being asked for each parameter and just accept the defaults. This also works with multiple services in one command.
takeout enable mysql --default
takeout enable redis meilisearch --default
Show a list of all enabled services you can disable.
takeout disable
Passed the short name of one or more services, disable the enabled services that match them most closely.
takeout disable mysql
takeout disable redis meilisearch
takeout disable --all
Show a list of all stopped containers you can start.
takeout start
Passed the container ID of one or more stopped containers, start the stopped containers that matches them.
takeout start {container_id}
takeout start {container_id1} {container_id2}
You may pass the -all
flag to start all enabled containers.
takeout start --all
Show a list of all running containers you can stop.
takeout stop
Passed the container ID of one or more running containers, stop the running containers that matches them.
takeout stop {container_id}
takeout stop {container_id1} {container_id2}
Another of Takeout's benefits is that it allows you to have multiple versions of a dependency installed and running at the same time. That means, for example, that you can run both MySQL 5.7 and 8.0 at the same time, on different ports.
Run takeout enable mysql
twice; the first time, you'll want to choose the default port (3306
) and the first version (5.7
), and the second time, you'll want to choose a second port (3307
), the second version (8.0
) and a different volume name (so that they don't share the same mysql_data
).
Now, if you run takeout list
, you'll see both services running at the same time.
+--------------+----------------+---------------+-----------------------------------+
| CONTAINER ID | NAMES | STATUS | PORTS |
+--------------+----------------+---------------+-----------------------------------+
| 4bf3379ab2f5 | TO--mysql--5.7 | Up 2 seconds | 33060/tcp, 0.0.0.0:3306->3306/tcp |
| 983acf46ceef | TO--mysql--8.0 | Up 35 seconds | 33060/tcp, 0.0.0.0:3307->3306/tcp |
+--------------+----------------+---------------+-----------------------------------+
Sadly, no.
First, run lsof -i :3306
(where 3306 is the port that's unavailable.)
If you see output like this:
com.docke 936 mattstauffer 52u IPv6 0xc0d6f0b06d5c4efb 0t0 TCP localhost:mysql->localhost:62919 (FIN_WAIT_2)
TablePlus 96155 mattstauffer 16u IPv4 0xc0d6f0b0b6dccf6b 0t0 TCP localhost:62919->localhost:mysql (CLOSE_WAIT)
The solution is to just close your database GUI, and then it should be released.
Using docker-compose
sets up your dependencies on a project-by-project basis, which is a perfectly fine way to do things. If it makes more sense to you to have a single copy of each of your dependencies for your entire global environment, Takeout makes more sense.
Nope! Your data will stick around! By default almost all of our services use a "volume" to attach your data to for exactly this reason.
So, when you disable the MySQL service, for example, that volume--with all your data in it--will just sit there quietly. And when you re-enable, as long as you attach it to the same volume, all your data will still be there.
The best way to see our future plans is to check out the Projects Board, but here are a few plans for the future:
self-remove
command: Deletes all enabled services and then maybe self-uninstalls?upgrade
: destroys the old container, brings up a new one with a newly-specified tag (prompt user for it, default latest
) and keeps all other parameters (e.g. port, volume) exactly the same as the old onept/passthrough
: proxy commands through to docker (./takeout pt mysql stop
)If you're working with us and are assigned to push a release, here's the easiest process:
Visit the Takeout Releases page; figure out what your next tag will be (increase the third number if it's a patch or fix; increase the second number if it's adding features)
On your local machine, pull down the latest version of main
(git checkout main && git pull
)
Build for the version you're targeting (php ./takeout app:build
)
Run the build once to make sure it works (php ./builds/takeout list
)
Commit your build and push it up
Draft a new release with both the tag version and release title of your tag (e.g. v1.5.1
)
Set the body to be a bullet-point list with simple descriptions for each of the PRs merged, as well as the PR link in parentheses at the end. For example:
- Fix internal Memcached port (#92)
Hit Publish release
Profit
HomeFragment.kt界面的逻辑 package com.example.takeout.ui.fragment import android.app.Fragment import android.graphics.Color import android.os.Bundle import android.util.Log import android.util.TypedValue