Solved: Adobe Lightroom CC 2015 update problem

After realizing my Adobe Lightroom CC 2015 at home hadn’t been auto-updating (and needed the latest update to be compatible with recent Sony raw format), nothing seemed to fix it — neither trying manual download nor updating permissions or other common online advice. (It was updating fine on another machine.)

The solution turned out to be: delete the file: /Library/Application Support/Adobe/AAMUpdaterInventory/1.0/AdobeUpdaterAdminPrefs.dat

Symptoms were: the “update” option under the help menu was disabled and the Creative Cloud showed the apps as current. The steps I did to fix it were

  • delete the “AdobeUpdaterAdminPrefs.dat” prefs file (see above)
  • log out of your Mac account (just to be safe)
  • log back in and both the Creative Cloud app as well as the in-app help menu should now offer the update option

    If this doesn’t work for you, it may be something else (like the oft-cited permission issues or conflicts with earlier versions of the app).

  • Basic HTTP Auth on Nginx

    Quick set-up for basic authentication on Nginx.

    Create htpasswd file on local or install tools via apt or yum, e.g.,

    apt-get install apache2-utils
    sudo htpasswd -c /etc/nginx/.htpasswd exampleuser

    Will be presented with password prompts

    Update your Nginx site config with:

    auth_basic "Restricted";
    auth_basic_user_file /etc/nginx/.htpasswd;

    Reload or restart Nginx

    /etc/init.d/nginx reload

    RAR on CentOS 7

    sudo rpm -ivh
    sudo yum -y install rar unrar

    Change a homebrew app to previously installed version

    If a previous version isn’t available via homebrew brew search (even after installing brew tap homebrew/versions) so you can’t switch via brew [un]link $FORMULA and you have installed it previously, do:

    brew info $FORMULA
    brew switch $FORMULA $VERSION

    E.g., to downgrade phpmyadmin from 4.5.2, I used:

    brew switch /usr/local/Cellar/phpmyadmin 4.3.4

    See: homebrew Tips-N’-Tricks

    (Of course you can also always manually update the symlink in /usr/local/share or update/create your own formula.)

    Docker network info, linked containers

    To see network info for Docker host, use the network (v1.9+) command:

    docker network [OPTIONS] COMMAND [OPTIONS]

    To link containers by name, you now need to use the –link command:

    The docker network inspect command above shows all the connected containers and their network resources on a given network. Containers in this default network are able to communicate with each other using IP addresses. Docker does not support automatic service discovery on the default bridge network. If you want to communicate with container names in this default bridge network, you must connect the containers via the legacy docker run --link option.

    If you upgraded your Docker host from pre 1.9 and your containers were not longer able to communicate, this is probably why.

    $ docker run --rm -ti busybox ping my-container
    ping: bad address 'my-container'
    $ docker run --rm -ti --link=my-container busybox ping my-container
    PING my-container ( 56 data bytes


    And note:

    While links are still supported in this limited capacity, you should avoid them in preference of Docker networks. The link feature is expected to be deprecated and removed in a future release.

    So also see: etc.

    Basic Docker usage stats

    Display a live stream of container(s) resource usage statistics:

    docker stats [OPTIONS] CONTAINER [CONTAINER...]

    To see all running containers:

    docker stats $(docker ps -q)

    « Previous Entries