We can recommend a free and open source emulator and provide tips to it in the README to make it easier to make sure we're not introducing breaking changes when we contribute.
In the future I also want to see if we could add CI to this project now that macOS CI setup is more widely available than it has been in the past.
While older versions may work, it is unrealistic for us to claim
official support for such old versions.
Also updates the copyright date in the README.
Qt, a dependency on capybara-webkit, causes a lot of install problems
and most recently more so. We're not using capybara-webkit so much now,
so we don't absolutely need Qt.
Fixes#499.
At first, we did Ruby work, so we needed a ruby version manager.
Then we needed Node, so some of us added a node version manager.
Some of work with varying versions of Python, Elixir, Elm, etc.
ASDF lets us stop searching out solutions to the same problem in
each of these languges by supporting [plugins][1].
[1]: https://github.com/asdf-vm/asdf-plugins/tree/master/plugins
For users running the Laptop script
who once had `heroku-toolbelt` installed,
it's possible their `PATH` may be out of date.
Use a similar pattern for updating the link to the `heroku` binary
as we used when migrating `qmake` for `qt5.5` from `qt`.
Also, update documentation.
Related: 3b7845b849
This reverts commit ef7408d6a1.
* `brew cleanup` removes Postgres.
* Migrating data in Postgres from old to new versions relies on
the previous version of Postgres to run `pg_upgrade`.
* Laptop shouldn't lose users' Postgres data.
* Those who don't mind starting their new Postgres databases
from scratch can `brew cleanup` in `~/.laptop.local`.
* thoughtbot/laptop doesn't explicitly depend on thoughtbot/dotfiles.
* So, we don't think it needs to be in the script.
* Show it as another example of customizations for those who might be
interested in updating their machine and dotfiles in one `sh mac`.
https://github.com/thoughtbot/laptop/pull/408
Sections:
* "Installing Homebrew packages ..."
* "Restarting services ..."
* "Relinking OpenSSL ..."
* "Configuring Ruby ..."
* "Running your customizations from ~/.laptop.local ..."
* "Cleaning up old Homebrew formulas ..."
Related:
* To make that work in the desired way,
print less noise in the custom functions.
* We don't need parity as customization in README.
* Match documentation to sections, move OpenSSL to Unix section.
* Move libyaml to after OpenSSL, before Ruby.
* The Parity Homebrew [package] installs Heroku Toolbelt, Git, Postgres
but it seems nice for documentation purposes to
keep the Homebrew packages installed for the other dependencies.
* Tap the Homebrew formula first, so it updates with `brew update`.
[package]: https://github.com/thoughtbot/homebrew-formulae/blob/master/Formula/parity.rb
> Homebrew-Cask will now be kept up to date together with Homebrew
> If you haven’t yet,
> run `brew uninstall --force brew-cask; brew update`
> to switch to the new system.
e83c0099aa
> To start using Homebrew-Cask, you just need Homebrew installed.
0d290b15e8
* Update supported versions list
* Update Debugging section of README
While updating to El Capitan, some users had problems installing or
updating Homebrew due to El Capitan's [SIP](https://en.wikipedia.org/wiki/System_Integrity_Protection)
security feature, which restricts access to `/usr`. Adding a link to
Homebrew's own El Capitan troubleshooting documentation so that users
who do have trouble will be able to see Homebrew's recommendations for
resolution.
* Update logo to use new HTTPS version.
* Change header from "Credits" to "About thoughtbot".
* Move "thank you" to contributors section.
* Make "About thoughtbot" the last thing in the README,
with the copyrights grouped closer to the LICENSE information.
* Link to LICENSE.
* Make the community link more obvious that we have other projects.
* Finish with a CTA to hire us.
* Include `utm_source` codes to improve tracking.
From @derekprior:
> I never used NVM. I just kept my homebrew installed version pinned to
> the version we were using. As a company this is probably totally fine
> because we don't jump back and forth between node projects like we do
> with Ruby projects. Also, there is no "system" node to worry about.
https://github.com/thoughtbot/laptop/pull/341#issuecomment-66179326
Thomas Riboulet
Chad Pytel