Android SDK without Studio

Enrique Matta-Rodriguez — Tue, 10 Nov 2020 20:00:24 +0000

Android SDK w/o Studio

Android Studio is bloat for developers who work on React Native or other third party tooling that isn't native or java Android development. It's a full blown IDE you might never open up, especially in a CI-CD pipeline. To get around this need, follow along and install Android SDK w/o the IDE.

Java

You will need to download and install java since most of the tooling revolves around it. I would highly suggest not using anything above Java 8. If you have a need for a newer version of the JVM you can follow a multi environment setup.

Single JVM Environment

The simplest way to get up and running with Java is to install the AdoptOpenJDK version 8 cask from brew:

brew tap adoptopenjdk/openjdk
brew cask install adoptopenjdk8

Another route (outside of brew) is with sdkman. This is a general JVM tooling that can allow for multiple JVMs to be installed. For our purpsoe, all you will need to do (after installing sdman is to run sdk install java 8.0.272.hs-adpt and then run sdk home java 8.0.272.hs-adpt to get the JAVA_HOME env var (export JAVA_HOME="$(sdk home java 8.0.272.hs-adpt)").

Multi JVM Environment

If there is a need to have multiple versions of the JVM I highly suggest you install via sdkman and install jenv. Unlike other version management toolings, like pyenv, nvm, or nodenv, you cannot install a JVM directly from jenv. Instead, you install them via sdkman and add all your JVMs in via jenv add $(sdk home java [version]). Once in the list, go to the root of the app and ensure that your local is pointed to Java 8 (jenv local 1.8). This is very important for the next portion.

Android SDK

First, you will need to visit the Android Studio download site and scroll until you see Command line tools only near the bottom and download the zip. I have a cURL below but it might be outdated by the time you read this, so go and download it there first instead.

When downloaded unzip that badboy anywhere you want and make sure you point ANDROID_SDK_ROOT to it.

Here is a convinient script for you, but keep in mind it might be outdated:

curl https://dl.google.com/android/repository/commandlinetools-mac-6858069_latest.zip -o $HOME/android-sdk.zip
unzip $HOME/android-sdk.zip -d $HOME/.tmp-android
mkdir $HOME/.android-sdk && mkdir $HOME/.android-sdk/cmdline-tools
mv $HOME/.tmp-android/cmdline-tools $HOME/.android-sdk/cmdline-tools/latest
rm -rf $HOME/android-sdk.zip $HOME/.tmp-android/
export ANDROID_SDK_ROOT="$HOME/.android-sdk"
yes | $ANDROID_SDK_ROOT/cmdline-tools/latest/bin/sdkmanager --update
yes | $ANDROID_SDK_ROOT/cmdline-tools/latest/bin/sdkmanager \
    "system-images;android-29;default;x86_64" \
    "platforms;android-29" \
    "build-tools;29.0.3" \
    "extras;google;m2repository" \
    "extras;android;m2repository"
yes | $ANDROID_SDK_ROOT/cmdline-tools/latest/bin/sdkmanager --licenses

If you are ever curious about what packages you have available to install you can run sdkmanager --list to view them. After installing the SDK you will need to add the following to either your .bash_profile or .zshrc:

export ANDROID_SDK_ROOT="$HOME/.android-sdk"
export PATH="$PATH:$ANDROID_SDK_ROOT/cmdline-tools/latest/bin"
export PATH="$PATH:$ANDROID_SDK_ROOT/platform-tools"
export PATH="$PATH:$ANDROID_SDK_ROOT/tools"

Once installed you can create simulators via the CLI with avdmanager create avd --name test-avd --package "system-images;android-29;default;x86_64".

And there you have it, a version of the SDK without having to download Android Studio.

Use Ansible to add users

Enrique Matta-Rodriguez — Mon, 10 Aug 2020 22:30:43 +0000

This will be a short but sweet dive into setting up users in your EC2 container with only their GitHub handles and ansible. I am expecting you have some ansible knowledge, so I won't dive deep into a beginner's tutorial. For that, I would suggest Ansible's own docs to get started.

Github

Every single GitHub user out there has access to their public key via curl. Don't believe me? Go to https://github.com/[your_handle].keys and voila your pub key is there for the taking. Here is mine. So, now that you have that bit of knowledge in your head, let's move on.

Ansible Playbook

vars

Step 1 is to create a vars file for the users. I've chosen the following structure for vars/users.yaml:

---
create_users: true

account_names:
  - { user: 'enriquem', key: 'https://github.com/ematta.keys' }

Add as many users you need to manage your EC2 instance. In this example, it's just me.

Users Role

Defaults

In your defaults folder you should add a main.yml file loaded with:

---
create_users: true

Files (sudoers)

Add the following under files/sudoers:

%sudo ALL=(ALL) NOPASSWD:ALL

Main Task `main.yaml`

Finally, you add this as your tasks for the users role.

---
- name: Verify you have wheel
  group:
    name: wheel
    state: present
  become: yes
  tags:
    - users

- name: Set wheel to passwordless sudo
  lineinfile:
    dest: /etc/sudoers
    state: present
    regexp: '^%wheel'
    line: '%wheel ALL=(ALL) NOPASSWD: ALL'
  become: yes
  tags:
    - users

- name: Create all users accounts
  user:
    name: "{{ item.user }}"
    shell: "/bin/bash"
    groups: 
      - users
      - wheel
    system: yes
    state: present
    append: yes
  with_items:
    - "{{ account_names }}"
  become: yes
  tags:
    - users

- name: Add ssh key for creted 
  authorized_key:
    user: "{{ item.user }}"
    key: "{{ item.key }}"
    state: present
  with_items:
    - "{{ account_names }}"
  become: yes
  tags:
    - users

Now, with all that in, just add users to your site.yaml file and poof you now have an easy way of adding users to an existing EC2 container.

DEV Community: Enrique Matta-Rodriguez