/browser

[DEPRECATED] A browser with Code.org-specific extensions, built with Electron

Primary LanguageJavaScriptApache License 2.0Apache-2.0

Code.org Maker App - DEPRECATED

Maintenance

Simple browser exposing native node-serialport to web-based tools on allowlisted Code.org domains.

This repo is deprecated because the Code.org Maker App is no longer supported. Boards now connect directly through the browser, so no app is needed to access the Maker Toolkit. Read more here.

Installation

Silent install / group install

Development setup

  • Use Node v14: nvm use v14.16.1 (nvm install v14.16.1 if it's not available)
  • Clone the repository, then run yarn to install dependencies
  • yarn start launches the app in development mode.
  • yarn win|mac|linux will create builds for the given OS in the ./dist directory
  • yarn release will create OS X, Windows, and Linux builds and upload them to S3, and create a Github release (note: use the build command above to create pre-release builds and verify them on Windows, Mac, and Linux prior to releasing). For full instructions, see below
    • For S3 deployment, the same AWS credential configuration that we use for other Code.org AWS work suffices
    • For Github, you'll need to set an environment variable with a personal Github access token that has full "repo" permissions for this repository (you can set up personal access tokens at https://github.com/settings/tokens): export GITHUB_TOKEN="token_goes_here"
    • To build an MSI installer, see below

Releasing

Note: You can only release an OS X app from an OS X machine. If you are using Linux or Windows, you'll need to pair with someone with a Mac to release the Maker app! If you are on OS X, you may be able to release on all platforms; depending on your hardware and OS version, you may need a Windows (virtual) machine to successfully create a build with native extensions. However you create the builds, it is important that you verify they run on their intended platforms before uploading to S3.

AWS Access

First, read through the AWS Account Login doc to make sure you have the correct credentials. Once you have AWS account access, we can set up access through your command line with the steps below (note that some steps are duplicative of steps in the Google Doc).

  1. Run brew info awscli to make sure you have the AWS command line tool. If you don't, run brew install awscli.
  2. From the root of the code-dot-org repository, run ./bin/aws_access. A successful response should look like: AWS access: GoogleSignIn/<your_codeorg_google_email>.
  3. Check that you have an AWS credentials file by running cat ~/.aws/credentials.
  4. If your AWS credentials from step 2 are nested under a [cdo] profile, run export AWS_PROFILE=cdo to make cdo your default AWS profile.

Code signing

This is the process of setting up certificates (paired with private keys) on your personal machine that are required for releasing the Maker app.

  1. Download the .p12 file from the "MakerAppCertificate" note in LastPass. LastPass does not allow file downloads from its browser extension -- you have to have the desktop app for this.
  2. Open the Keychain Access app (comes with OS X by default). Double-click the downloaded .p12 file to add it to your keychain. You will be prompted for a password, which is stored in the LastPass note description.
  3. Examine the certificate in your keychain (make sure you're in the "login" Keychain and "Certificates" Category, which are found in the lefthand navigation). It should look something like the table below, where the "Developer ID Application" is the outer certificate, and the "Code.org" private key is nested within that certificate. If your certificate does not contain a private key, you will most likely need to generate a new certificate by following the steps in Generating a new Developer ID Application.
    Name Kind Expires Keychain
    Developer ID Application: Code.org ([codeorg_id_here]) certificate Mar 13, 2025 login
    > Code.org private key -- login
  4. To sign Windows builds, we need to set up two environment variables from the command line:
    1. export WIN_CSC_LINK=/SecretsDirectory/codeorg_signing_certificate.p12 (where path corresponds to the .p12 file downloaded in step 1)
    2. export WIN_CSC_KEY_PASSWORD='secret_password' (secret_password is stored in the "MakerAppCertificate" note in LastPass)
  5. To notarize the Mac builds, we need to set up two additional environment variables
    1. export APPLEID=[Apple ID from LastPass]
    2. export APPLEIDPASS=[App specific password in Apple entry in LastPass]

Testing a build before release

Note: It is important to verify working builds for each operating system we support (Mac, Linux, Windows 32 and 64 bit) before creating a release.

  1. Run yarn win && yarn mac && yarn linux
  2. Find the builds in the ./dist folder and run them on their intended OS verifying connectivity and core features

Verifying Windows and Linux builds using VirtualBox

  1. Download and install VirtualBox
  2. Download the lastest Windows 64 bit (x64) and 32 bit (x86) VirtualBox archives from the Microsoft Edge Tools site and unpack the zip files. For Linux, download the current Ubuntu LTS version
  3. Set up each of the downloaded builds in VirtualBox:
    1. Go to File -> Import Appliance -> select the .ovf file from the downloaded archive
    2. Select the VM and open Settings
    3. Fix any incompatible settings by following the instructions shown with the ⚠️ icon.
    4. Select Storage -> Add New Storage Attachment (floppy disk icon) -> Optical Drive -> select VboxGuestAdditions.iso
    5. Select Ports -> USB -> Enable USB Controller
    6. Save and exit Settings
    7. Start the VM (default Windows password is Passw0rd!)
    8. In Windows/Linux open the CD drive and run VBoxWindowsAdditions accepting all default settings (restart if prompted)
  4. In the running VM, install the Maker App build you would like to verify (copy installer from ./dist on your host machine)
  5. Connect a Circuit Playground and "capture" it in the VM by right clicking the USB icon in the bottom right and selecting your board
  6. Open the Maker App, verify connectivity by clicking the Setup cog in the top toolbar, try out the core features using this test project

Releasing a new version

  1. Bump the version in package.json
  2. If all builds from the verify process above were built on your mac, simply run yarn release. If your Windows executable either failed to build or failed to run then you will need to rebuild it on a Windows virtual machine.

Using a Virtual Machine to build and release a new Windows version

  1. Start the Windows 64 bit Virtual Machine that you installed in the Verify process above.
  2. Using the built-in Edge browser, download and install NodeJS 14. Accept all default settings until you reach Tool for Native Modules screen and Check "Automatically install the necessary tools." Several install scripts will run. Accept any default settings when prompted.
  3. Install Visual Studio Community. Select "Desktop development with C++" when prompted (this is necessary to build the native Serial adapter).
  4. See instruction in Code Signing above for downloading the .p12 certificate. Copy it to the virtual machine
  5. Copy over the the entire browser directory from your host machine to the VM (or download your branch from Github)
  6. Open Powershell as Administrator (use search box on Windows toolbar)
    1. cd path\to\browser
    2. node -v v14.x.x
    3. npm install -g yarn
    4. yarn install
    5. $Env:WIN_CSC_LINK = "/SecretsDirectory/codeorg_signing_certificate.p12"
    6. $Env:WIN_CSC_KEY_PASSWORD = "secret_password" (secret_password is stored in the "MakerAppCertificate" note in LastPass)
    7. yarn release-win
  7. Manually upload the files created in ./dist to S3 (automated S3 publishing does not work from Windows) and also copy them to ./dist on your host operating system.
  8. On your host OS run yarn release-mac && yarn release-linux && yarn github-release. This will create the mac and linux builds, upload them to S3, and draft a release in Github).

Generating a new Developer ID Application

These steps are only necessary if the certificate you have obtained from LastPass (or some other internal source) does not contain the private key. Try the steps in Code signing first before generating a new certificate. Apple allows 5 certificates before we have to start revoking older certificates.

  1. Obtain the LastPass credentials for our Apple Developer account and log in to developer.apple.com. The Accounts/A-Team have permissions to share these credentials.
  2. Go to "Account" > "Certificates, Identifiers & Profiles."
  3. Click the "+" button next to the "Certificates" header to create a new certificate.
  4. Choose the "Software" > "Developer ID Application" option and click "Continue".
  5. You should now be asked to upload a Certificate Signing Request (CSR). Open the Keychain Access app (comes default on OS X) to create a CSR.
  6. Within Keychain Access, use the top navbar to navigate to "Keychain Access" > "Certificate Assistant" > "Request a Certificate From a Certificate Authority"
  7. Fill out the certificate information -- "User Email Address" is your Code.org email, "Common Name" is your name, "CA Email Address" is the email associated with our Apple Developer account, and "Request is: Saved to disk".
  8. Upload the .certSigningRequest file to finish generating our new certificate.
  9. Download the certificate. Double-click the downloaded file to add the certificate to your keychain.
  10. Examine the certificate to make sure it includes a private key (see step 3 of Code signing for more details).
  11. If a private key is present, you can export the certificate + private key as a .p12 file, which will be needed for step 4 of Code signing.

MSI Installer (for networked Windows installs)

Options

The following environment variables are available to help with local development:

  • NODE_ENV controls the default Code.org host. If set to production it will point at the live Code.org site. Otherwise it will point to http://localhost-studio.code.org:3000.
  • DASHBOARD_HOST sets the dashboard host, overriding whatever would normally be selected by the NODE_ENV setting. Omit any trailing slash. (Example: DASHBOARD_HOST=https://dashboard-adhoc-maker.cdn-code.org yarn start)
  • OPEN_DEV_TOOLS, if set, will cause the developer tools for both the electron app and its contained webview to open when the app loads. (Example: OPEN_DEV_TOOLS=1 yarn start)

Resources