Categories
Mac

Remote Control another Mac on your network

You need to go to the Mac you want to access and under System Preferences->Sharing activate the following:

macOS Sharing Settings

On all this options you can limit the users that can have access.

On the File Sharing option, you can determine what folders can be accessed in the network and by whom.

On Remote Management you will be asked what you want from this list, use option/alt click to select all:

macOS Remote Management Options

Once that is done you can go to the other Mac you want to use and in Finder you should see the Mac on the sidebar under Locations or click Network:

macOS Finder ScreenShare Connect As

You see on the top right options to Share Screen or Connect As. Click Share Screen to get remote control of the other Mac or Connect As to simple browse the folders that you gave permissions on the File Sharing step.

Categories
Dev Mac

Change macOS terminal shell to Bash 5

Since macOS Catalina that zsh is the default shell. From what I could understand this was caused by a change in Bash license to GPL after version 3.

So, since version 3 of Bash is pretty old they changed the default to zsh.

Since Homebrew is not yet fully Apple Silicon compatible using Homebrew was not an option. If your Mac runs Intel a simple brew install bash will install a newer version of Bash on /usr/local/bin/bash (if you had Homebrew installed obviously). You can follow the updates for Homebrew compatibility with Apple Silicon here.

This leaves us with installing Bash the good old fashion way:

curl -O https://ftp.gnu.org/gnu/bash/bash-5.1.tar.gz
tar xzf bash-5.1.tar.gz
cd bash-5.1
./configure --prefix=/usr/local && make && sudo make install

After that is done, you just need to add Bash to your available shells:

sudo bash -c "echo /usr/local/bin/bash >> /private/etc/shells"

And make Bash the active one:

chsh -s /usr/local/bin/bash

Open a new terminal window or restart your terminal app and check with:

echo "$SHELL"
bash --version

Categories
Dev Mac Tech

MAMP Pro – Oops, something is badly wrong!

Out of the blue, MAMP Pro started presenting me with an alert when I tried opening the app:

Oops, something is badly wrong!
Either you did not provide the necessary admin credentials or the MAMP PRO package could not be initialized correctly. You can either restart the application and try again or re-install the software.

I contacted support, they advised me to uninstall/reinstall and that didn’t help. The alert kept on being the only thing I saw when I tried to start the app and then it would just close.

After doing some digging around the web, I ended up here and the following command fixed it:

sudo launchctl load -w /Library/LaunchDaemons/de.appsolute.mampprohelper.plist

I suspect this might have been caused because I manually disabled MAMP Pro helper Launch Agent on macOS. Still not sure why MAMP Pro needs that running to start the app but it looks like it does.

BTW: the databases and settings for MAMP Pro are not in /Applications/MAMP but in /Library/Application Support/appsolute/MAMP PRO/

Categories
OpenStack OVH Tech

Transmit OVH OpenStack Swift v3 Configuration

Steps to configure OVH OpenStack Swift v3 on Transmit:

  • Click the + to add a New Server
  • Choose OpenStack Swift

Address: auth.cloud.ovh.net
User Name: TENANT_NAME:USER
Password: USER_PASSWORD
Remote Path: v3

Obviously replace TENANT_NAME, USER and USER_PASSWORD with your values.

Categories
OpenStack OVH Tech

CyberDuck OVH OpenStack Swift v3 Configuration

OVH disabled Keystone (OpenStack Identity Service) API v2.0 and requires all endpoints to now use v3.

Currently, the instructions to setup CyberDuck with OVH are not correct. They mention the Tenant_ID:Access_Key should be filled with Project_ID:Horizon_User_ID.

Currently CyberDuck requires Project:Domain:Username and in the case of OVH should be TENANT_NAME:default:USER

Steps to set it up on CyberDuck:

  • click the + to Add a New Bookmark
  • from the dropdown pick OpenStack Swift (Keystone 3)

Fields

Server – auth.cloud.ovh.net
Project:Domain:Username – TENANT_NAME:default:USER
Password: USER_PASSWORD
Path (under More Options): v3.0

Obviously replace TENANT_NAME, USER and USER_PASSWORD with your values.

Note: ‘default’ is the default domain and if not changed it should work.