Simple browser exposing native node-serialport to web-based tools on allowlisted Code.org domains.
- For installation links and setup instructions, see https://studio.code.org/maker/setup
Silent install / group install
We support a few approaches for installing Code.org Maker App to a group of computers on a school network.
Here's our MSI package. Windows network administrators may find this is the easiest approach to deploy to computers on a network. Please note that auto-updates are disabled when the app is installed via MSI.
Another approach is a silent install using the installer we've provided on the downloads page. It accepts the following command switches:
/S(case-sensitive) puts the installer in "silent" mode for unattended install
/D=<directory>(also case-sensitive) lets you specify an install directory from the command line
Code.org Maker App-1.1.5-win.exe /S /D="C:\Program Files\Code.org Maker App"
These are standard install options for a Nullsoft (NSIS) installer. You can read more about them in the NullSoft manual in chapter 3 (Installer Usage) and chapter 4 (Silent Installers). Please give these options a try and let us know if they work for you. We're always looking for feedback!
- Use Node v8:
nvm use v8.9.1(
nvm install v8.9.1if it's not available)
- Close the repository, then run
yarnto install dependencies
yarn startlaunches the app in development mode.
yarn releasewill create OS X, Windows, and Linux builds, upload them to S3, and create a Github release
- For S3 deployment, the same AWS credential configuration that we use for other Code.org AWS work suffices
- For Github (currently disabled due to a bug in the builder), 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):
- To build an MSI installer, see below
- If you build on OS X, you can sign both Windows and OS X applications when building. Code signing will happen automatically if you set up credentials correctly; if they are not provided, unsigned builds will be created.
- OS X: once you've obtained the credentials for OS X app signing, add them to your keychain
- Windows: to sign Windows builds, obtain the appropriate Authenticode p12 file and the password, and set the following environment variables on the command line (assuming you're using OS X or Linux):
MSI Installer (for networked Windows installs)
- First time setup:
- Copy the
codeorg-authenticode.p12Windows code signing file into the
- Copy the
- Make sure Docker is running on your computer (https://docs.docker.com/docker-for-mac/install/ for OS X, should show up in your toolbar as running when you’re ready)
- Pull the
msi-installerbranch from this repo, merge desired changes in from master, and bump to the correct version number
- The build will appear on the local machine in dist
- Copy to the S3 bucket (requires AWS CLI and Code.org credentials):
aws s3 cp ./dist/<filename>.msi s3://downloads.code/org/maker/
The following environment variables are available to help with local development:
NODE_ENVcontrols the default Code.org host. If set to
productionit will point at the live Code.org site. Otherwise it will point to http://localhost-studio.code.org:3000.
DASHBOARD_HOSTsets the dashboard host, overriding whatever would normally be selected by the
NODE_ENVsetting. 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)
- I used libicns via the icnsutils package to generate OSX icon files from Ubuntu.