Skip to main content

macOS Automated Package Manager

Project description

OS X Yosemite, OS X El Capitan, macOS Sierra
macOS High Sierra, macOS Mojave
:Language: Python (version โ‰ฅ 3.4)
:Environment: Console | Terminal

MacDaily - macOS Automated Package Manager

|download| |version| |status| |format|

|python| |implementation|

- `About <#about>`__
- `Installation <#installation>`__
- `Configuration <#configuration>`__
- `Usage Manual <#usage-manual>`__

- `Start-Up <#start-up>`__
- `Commands <#commands>`__
- `Generals <#generals>`__

- `Troubleshooting <#troubleshooting>`__
- `TODO <#todo>`__



Package day-care manager on macOS.

**MacDaily** is an all-in-one collection of console utility written in Python
with support of `PTY <>`__.
Originally works as an automated housekeeper for Mac to update all packages
outdated, **MacDaily** is now fully functioned and end-user oriented.

**MacDaily** can manage packages of various distributions of
`Atom <>`__, `RubyGems <>`__,
`Homebrew <>`__, `Python <>`__,
`Node.js <>`__, and even macOS software updates (c.f.
``softwareupdate(8)``). Without being aware of everything about your Mac, one
can easily work around and manage packages out of no pain using **MacDaily**.


MacDaily runs only with support of Python from version **3.4**
or higher. And it shall only work ideally on **macOS**.

.. raw:: html

<a name="brew">
MacDaily is now <code>brew</code>able ๐Ÿบ

Though not introduced to
`Homebrew core <>`__ database yet,
**MacDaily** is still available for ``brew``. Use the following commands to
add the `Tap <>`__ to your local
Homebrew installation (``$(BREW_PREFIX)/Homebrew/Library/Taps/``) and install
**MacDaily** through Homebrew.

.. code:: shell

$ brew tap jarryshaw/tap
$ brew install macdaily
# or simply, a one-liner
$ brew install jarryshaw/tap/macdaily

.. raw:: html

<a name="pip">
Legacy approach through <code>pip</code> ๐Ÿ

Just as many Python packages, MacDaily can be installed through
``pip`` using the following command, which will get you the latest
version from `PyPI <>`__.

.. code:: shell

$ pip install macdaily

Or if you prefer the hard-core real-latest version and fetch from this GitHub
repository, then the script below should be used.

.. code:: shell

$ git clone
$ cd MacDaily
$ pip install -e .
# and to update at any time
$ git pull

Also, for best performance of MacDaily, the notable automation tool
|expect|_ is expected to be installed on your Mac. Recommended installation
approach is from `Homebrew <>`__, as shown below.

.. code:: shell

$ brew install expect

.. |expect| replace:: ``expect``
.. _expect:

Or if you prefer not to install |expect|_, MacDaily will use
|UNIX script utility|_ instead. Make sure that ``/usr/bin/script``
exists and ``/usr/bin`` is in your ``PATH`` environment variable.

.. |UNIX script utility| replace:: UNIX ``script`` utility
.. _UNIX script utility:

For the worst case, MacDaily adopts |ptyng|_ as an alternative. It is
a revised version of |Python pty module|_, intended to support
pseudo-terminal (PTY) on macOS with no further issue. To install ``ptyng``,
you may use the script below.

.. |ptyng| replace:: ``ptyng``
.. _ptyng:
.. |Python pty module| replace:: Python ``pty`` module
.. _Python pty module:

.. code:: shell

$ pip install macdaily[ptyng]
# or explicitly...
$ pip install macdaily ptyng

For **tree** format support in ``dependency`` command, you will need
|dictdumper|_, then implicitly you can use the following script to do so.

.. |dictdumper| replace:: ``DictDumper``
.. _dictdumper:

.. code:: shell

$ pip install macdaily[tree]
# or explicitly...
$ pip install macdaily dictdumper

And |configupdater|_ is required to support modification of the configuration
file in ``config`` command, since MacDaily intends to maintain the original
layout and information of original configuration file after modification. To
install, the sample script is as below.

.. |configupdater| replace:: ``ConfigUpdater``
.. _configupdater:

.. code:: shell

$ pip install macdaily[config]
# or explicitly...
$ pip install macdaily configupdater

To install all requirements for full support of MacDaily, you may simply run
the following script when installation.

.. code:: shell

$ pip install macdaily[all]
# or explicitly...
$ pip install macdaily configupdater dictdumper ptyng


This part might be kind of garrulous, for some may not know what's
going on here. ๐Ÿ˜‰

Since robust enough, MacDaily now supports configuration upon
user's own wish. One may set up log path, hard disk path, archive path
and many other things, other than the default settings.

MacDaily now supports configuration commands,
see manual of |config|_ command for more information.

The configuration file should lie under ``~/.dailyrc``, which is hidden
from Finder by macOS. To review or edit it, you may use text editors
like ``vim`` and/or ``nano``, or other graphic editors, such as Sublime
Text and/or Visual Studio Code, or whatever you find favourable.

.. code:: ini

# In this section, paths for log files are specified.
# Please, under any circumstances, make sure they are valid.
logdir = ~/Library/Logs/MacDaily ; path where logs will be stored
dskdir = /Volumes/Your Disk ; path where your hard disk lies
arcdir = ${dskdir}/Developers ; path where ancient logs archive

# In this section, flags for modes are configured.
# If you would like to disable the mode, set it to "false".
apm = true ; Atom plug-ins
app = true ; macOS Applications
brew = true ; Homebrew Formulae
cask = true ; Homebrew Casks
cleanup = true ; cleanup caches
gem = true ; Ruby gems
mas = true ; Mac App Store applications
npm = true ; Node.js modules
pip = true ; Python packages
system = true ; macOS software
tap = true ; Homebrew Taps

# In this section, scheduled tasks are set up.
# You may append and/or remove the time intervals.
archive = false ; archive logs
bundle = false ; bundle packages
cleanup = false ; cleanup caches
config = false ; config MacDaily
dependency = false ; show dependencies
install = false ; install packages
launch = false ; launch daemons
logging = true ; log installed packages
postinstall = false ; postinstall packages
reinstall = false ; reinstall packages
uninstall = false ; uninstall packages
update = true ; update packages
schedule = ; scheduled timing (in 24 hours)
8:00 ; update & logging at 8:00
22:30-update ; update at 22:30
23:00-logging ; logging at 23:00

# In this section, command options are picked.
# Do make sure these options are available for commands.
update = --all --quiet --show-log
logging = --all --quiet --show-log

# In this section, miscellaneous specifications are assigned.
# Please, under any circumstances, make sure all fields are valid.
askpass = ... ; SUDO_ASKPASS utility for Homebrew Casks
confirm = ... ; confirm utility for MacDaily
timeout = 1000 ; timeout limit for shell commands in seconds

Above is the default content of ``.dailyrc``, following the grammar of
``INI`` files. Lines and words after number sign (``#``) and semicolon
(``;``) are comments, whose main purpose is to help understanding the
contents of this file.

In section ``Path``, there are path names where logs and some other
things to be stored. In section ``Mode``, there are ten different
modes to indicate if they are *enabled* or *disabled*.

You may wish to set the ``dskdir`` -- *path where your hard disk lies*,
which allows MacDaily to archive your ancient logs and caches into
somewhere never bothers.

Please **NOTE** that, under all circumstances, of section ``Path``,
all values would better be a **valid path name**, possibly with ``~``
user-home expansion.

Besides, in section ``Daemon``, you can decide which command is
scheduled and when to run such command, with the format of
``HH:MM[-CMD]``. The ``CMD`` is optional, which will be ``any`` if
omits. And you may set up which command(s) will be registered as daemons
and run with schedule through booleans above. These boolean values
help MacDaily indicate which is to be launched when commands in
schedule omit. That is to say, when ``CMD`` omits in schedule, MacDaily
will register all commands that set ``true`` in the above boolean values.

Also, in section ``Option``, you may set up optional arguments for
the daemons above. Do please make sure these commands are **valid**. And
if omit, the help command ``--help`` will be given.

Last but no least, in section ``Miscellaneous``, you should **NEVER**
modify any contents under this section in order to keep MacDaily
working. However, you may set up this part with |config|_ command.

Usage Manual


Before we dive into the detailed usage of MacDaily, let's firstly
get our hands dirty with some simple commands.

**NOTE** -- all acronyms and aliases are left out for a quick and
clear view of MacDaily

1. How to use MacDaily?

.. code:: shell

# call from PATH
$ macdaily <command> [option ...]
# or call as Python module
$ python -m macdaily <command> [option ...]
# or call a certain command
$ md-${command} [option ...]

2. How to set up my disks and daemons interactively?

.. code:: shell

$ macdaily config --interactive

3. How to relaunch daemons after I manually modified ``~/.dailyrc``?

.. code:: shell

$ macdaily launch daemons

4. How to archive all ancient logs without running any commands?

.. code:: shell

$ macdaily archive --all

5. How to update all outdated packages?

.. code:: shell

$ macdaily update --all

6. How to update a certain package (eg: ``hello`` from Homebrew)?

.. code:: shell

$ macdaily update brew --package=hello

7. How to update without a certain package (eg: update all packages
except Python package ``ptyng``)?

.. code:: shell

$ macdaily update --all --pip='!ptyng'

8. How to uninstall a certain package along with its dependencies (eg:
``pytest`` from brewed CPython version 3.6)?

.. code:: shell

$ macdaily uninstall pip --brew --cpython --python=3.6 --package=pytest

9. How to reinstall all packages but do not cleanup caches?

.. code:: shell

$ macdaily reinstall --all --no-cleanup

10. How to postinstall packages whose name ranges between "start" and
"stop" alphabetically?

.. code:: shell

$ macdaily postinstall --all --start=start --end=stop

11. How to show dependency of a certain package as a tree (eg: ``gnupg``
from Homebrew) ?

.. code:: shell

$ macdaily dependency brew --tree --package=gnupg

12. How to log all applications on my Mac, a.k.a. ``*.app`` files?

.. code:: shell

$ macdaily logging app

13. How to dump a ``Macfile`` to keep track of all packages?

.. code:: shell

$ macdaily bundle dump


MacDaily supports several different commands. Of all commands,
there are corresponding **aliases** for which to be reckoned as

| Command | Aliases |
| |archive|_ | |
| |bundle|_ | |
| |cleanup|_ | ``clean`` |
| ``commands`` | |
| |config|_ | ``cfg`` |
| |dependency|_ | ``deps``, ``dp`` |
| |help|_ | ``doc``, ``man`` |
| |install|_ | ``i`` |
| |launch|_ | ``init`` |
| |logging|_ | ``log`` |
| |postinstall|_ | ``post``, ``ps``, |
| |reinstall|_ | ``re`` |
| |uninstall|_ | ``un``, ``unlink``, ``remove``, ``rm``, ``r`` |
| |update|_ | ``up``, ``upgrade`` |

For more information, MacDaily provides ``commands`` to help you find out the
expecting command.

.. code:: shell

$ macdaily commands
MacDaily available commands & corresponding subsidiaries:
bundle dump, load
cleanup brew, cask, npm, pip
dependency brew, pip
install apm, brew ,cask, gem, mas, npm, pip, system
launch askpass, confirm, daemons
logging apm, app, brew, cask, gem, mas, npm, pip, tap
reinstall brew, cask
uninstall brew, cask, pip
update apm, brew, cask, gem, mas, npm, pip, system


.. code:: man

usage: macdaily [options] <command> ...

macOS Automated Package Manager

optional arguments:
-h, --help show this help message and exit
-V, --version show program's version number and exit

command selection:
MacDaily provides a friendly CLI workflow for the administrator of macOS
to manage and manipulate packages, see 'macdaily commands' for more

Commands for ``macdaily`` is shown as above and they are mandatory. For
more detailed usage information, please refer to manuals of corresponding
commands. For developers, internal details can be found in |miscellaneous|_
manual. And here is a brief catalogue for the manuals.

- `Archive Command <>`__
- `Bundle Command <>`__

- `Dump Macfile <>`__
- `Load Macfile <>`__

- `Cleanup Command <>`__

- `Homebrew Formulae <>`__
- `Caskroom Binaries <>`__
- `Node.js Modules <>`__
- `Python Packages <>`__

- `Config Command <>`__
- `Dependency Command <>`__

- `Homebrew Formulae <>`__
- `Python Packages <>`__

- `Help Command <>`__
- `Install Command <>`__

- `Atom Plug-Ins <>`__
- `Homebrew Formulae <>`__
- `Caskroom Binaries <>`__
- `Ruby Gems <>`__
- `macOS Applications <>`__
- `Node.js Modules <>`__
- `Python Package <>`__
- `System Software <>`__

- `Launch Command <>`__

- `Askpass Helper Program <>`__
- `Confirm Helper Program <>`__
- `Daemons Helper Program <>`__

- `Logging Command <>`__

- `Atom Plug-Ins <>`__
- `Mac Applications <>`__
- `Homebrew Formulae <>`__
- `Caskroom Binaries <>`__
- `Ruby Gem <>`__
- `macOS Applications <>`__
- `Node.js Modules <>`__
- `Python Packages <>`__
- `Third-party Repositories <>`__

- `Postinstall Command <>`__
- `Reinstall Command <>`__

- `Homebrew Formulae <>`__
- `Caskroom Binaries <>`__

- `Uninstall Command <>`__

- `Homebrew Formulae <>`__
- `Caskroom Binaries <>`__
- `Python Package <>`__

- `Update Command <>`__

- `Atom Plug-Ins <>`__
- `Homebrew Formulae <>`__
- `Caskroom Binaries <>`__
- `Ruby Gems <>`__
- `macOS Applications <>`__
- `Node.js Modules <>`__
- `Python Package <>`__
- `System Software <>`__

- `Developer Manual <>`__

- `Project Structure <>`__
- `Command Classes <>`__
- `Miscellaneous Utilities <>`__

- `ANSI Sequences <>`__
- `Print Utilities <>`__
- |script|_

.. |script| replace:: UNIX ``script``
.. _script:


1. Where can I find the log files?
It depends. Since the path where logs go can be modified through
``~/.dailyrc``, it may vary as your settings. In default, you may
find them under ``~/Library/Logs/Scripts``. And with every command,
logs can be found in its corresponding folder. Logs are named after
its running time, in the fold with corresponding date as its name.

Note that, normally, you can only find today's logs in the folder,
since ``macdaily`` automatically archive ancient logs into
``${logdir}/arcfile`` folder. And every week, ``${logdir}/arcfile``
folder will be tape-archived into ``${logdir}/tarfile``. Then after a
month, and your hard disk available, they will be moved into
``/Volumes/Your Disk/Developers/``.

2. What if my hard disk ain't plugged-in when running the scripts?
Then the archiving and removing procedure will **NOT** perform. In
case there might be some useful resources of yours.

3. Which directory should I set in the configuration file?
First and foremost, I highly recommend you **NOT** to modify the
paths in ``~/.dailyrc`` manually, **EXCEPT** your disk path

But if you insist to do so, then make sure they are **VALID**, possibly
with ``~`` user-home expansion and most importantly, they must be
**available** with permission granted.


- โœ”๏ธ support configuration
- โœ”๏ธ support command aliases
- โœ”๏ธ reconstruct archiving procedure
- โŒ support ``gem`` and ``npm`` in all commands
- โœ”๏ธ considering support more versions of Python
- โœ”๏ธ optimise ``KeyboardInterrupt`` handling procedure
- โŒ implement further specifications for package indication mini-language
- โœ”๏ธ review ``pip`` implementation and version indication
- โœ”๏ธ add ``--user`` for ``pip`` commands
- โŒ implement ``bundle`` and ``help`` commands

.. |archive| replace:: ``archive``
.. _archive:
.. |bundle| replace:: ``bundle``
.. _bundle:
.. |cleanup| replace:: ``cleanup``
.. _cleanup:
.. |config| replace:: ``config``
.. _config:
.. |dependency| replace:: ``dependency``
.. _dependency:
.. |help| replace:: ``help``
.. _help:
.. |install| replace:: ``install``
.. _install:
.. |launch| replace:: ``launch``
.. _launch:
.. |logging| replace:: ``logging``
.. _logging:
.. |miscellaneous| replace:: ``miscellaneous``
.. _miscellaneous:
.. |postinstall| replace:: ``postinstall``
.. _postinstall:
.. |reinstall| replace:: ``reinstall``
.. _reinstall:
.. |uninstall| replace:: ``uninstall``
.. _uninstall:
.. |update| replace:: ``update``
.. _update:

.. |download| image::
.. |version| image::
.. |format| image::
.. |status| image::
.. |python| image::
.. |implementation| image::

Project details

Release history Release notifications

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Filename, size & hash SHA256 hash help File type Python version Upload date
macdaily-2019.1.22-cp34-none-macosx_10_14_x86_64.whl (816.8 kB) Copy SHA256 hash SHA256 Wheel cp34
macdaily-2019.1.22-cp35-none-macosx_10_14_x86_64.whl (816.8 kB) Copy SHA256 hash SHA256 Wheel cp35
macdaily-2019.1.22-cp36-none-macosx_10_14_x86_64.whl (816.1 kB) Copy SHA256 hash SHA256 Wheel cp36
macdaily-2019.1.22-cp37-none-macosx_10_14_x86_64.whl (816.1 kB) Copy SHA256 hash SHA256 Wheel cp37
macdaily-2019.1.22-pp35-none-macosx_10_14_x86_64.whl (816.8 kB) Copy SHA256 hash SHA256 Wheel pp35
macdaily-2019.1.22-py3.4.egg (1.0 MB) Copy SHA256 hash SHA256 Egg 3.4
macdaily-2019.1.22-py3.5.egg (1.0 MB) Copy SHA256 hash SHA256 Egg 3.5
macdaily-2019.1.22-py3.6.egg (995.1 kB) Copy SHA256 hash SHA256 Egg 3.6
macdaily-2019.1.22-py3.7.egg (995.5 kB) Copy SHA256 hash SHA256 Egg 3.7
macdaily-2019.1.22.tar.gz (698.1 kB) Copy SHA256 hash SHA256 Source None

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN SignalFx SignalFx Supporter DigiCert DigiCert EV certificate StatusPage StatusPage Status page