Standalone web client for Scratch
Where am I?
Physically? No idea.
Digitally? You’re at Scratch’s open source web client!
We’re working to update the Scratch website to use a new codebase, contained in this repository.
Before Getting Started
- Make sure you have node (v4.2 or higher) and npm installed We use npm (Node Package Manager) to maintain and update packages required to build the site.
It's important to make sure that all of the dependencies are up to date because the scratch-www code only works with specific versions of the dependencies. You can update the packages by running this command:
npm run build
If you want to run a server that rebuilds the files as you edit them, skip to the To Run section below.
Warnings during npm install
These warnings can be safely ignored:
npm WARN firstname.lastname@example.org requires a peer of react@^0.14.0 but none was installed. npm WARN email@example.com requires a peer of react@^0.14.0 but none was installed. npm WARN firstname.lastname@example.org requires a peer of redux@^2.0.0 || ^3.0.0 but none was installed. npm WARN email@example.com requires a peer of react@^0.14.7 but none was installed. npm WARN firstname.lastname@example.org requires a peer of react@^0.14.8 but none was installed.
These currently exist in static/js/lib
If you would like to create a temporary version of the site on your machine that you can access through your web browser run the command below. Building (see To Build above) is not necessary for this step and the temporary server can be turned off (see To Stop below).
The intl directory must be built separately with the
make translations line below in order for the text to appear properly.
make translations npm start
The site hosted on your local machine can now be accessed by a web browser by entering localhost:8333 into your web browser.
npm start watches any update you make to files in either
./src and triggers a rebuild of the project. In development, the build is stored in memory, and not served from the
npm start, here are some important log messages to keep an eye out for:
webpack: bundle is now VALID.– The bundle has been loaded into memory and is now viewable in the browser. This will show up both once
npm starthas completed its setup, and also once updates you make to files have been re-compiled for viewing in the browser.
webpack: bundle is now INVALID.– If you see this, then it means you have made updates to files that are still being compiled for browser viewing. Pages will still be viewable, but they will not see any updates you made yet.
To stop the process that is making the site available to your web browser (created above in To Start) use
npm start can be configured with the following environment variables
||Hostname for API requests|
||Hostname for asset requests|
||Hostname for backpack requests|
||Hostname for project requests|
||DSN for Sentry|
||Pass-through location for old site|
||Where to log Google Analytics data|
||Port for devserver (http://localhost:XXXX)|
NOTE: Because by default
API_HOST=https://api.scratch.mit.edu, please be aware that, by default, you will be seeing and interacting with real data on the Scratch website.
Deploying to staging or production will upload code to S3 and configure Fastly.
npm install virtualenv ENV . ENV/bin/activate pip install -r requirements.txt make deploy
||Fastly service ID for
||Fastly API key for
||Activate changes and purge all after configuring|
||AWS access key id for S3|
||AWS secret access key for S3|
||S3 bucket name to deploy into|
Current issues with the development
We're currently in the process of transitioning into this web client from Scratch's existing structure. As we transition, there are going to be some issues along the way that relate to how this client needs to interact with the existing infrastructure to work properly in production.
On top of migrating to using this as our web client, Scratch is also transitioning into using a new API backend, Scratch REST API. As that is also currently in development and incomplete, we are set up to fall back to using existing Scratch endpoints if an API endpoint does not exist – which is where the
FALLBACK comes in.
Most of the issues we have currently revolve around the use of
FALLBACK. This variable is used to specify what URL to fall back onto should a request fail within the context of this web client, or when using the
API_HOST. If not specified in the process, it will not be used, and any request that is not made through the web client or the API will be unreachable.
FALLBACK=https://scratch.mit.edu allows the web client to retrieve data from the Scratch website in your development environment. However, because of security concerns, trying to send data to Scratch through your development environment won't work. This means the following things will be broken for the time being:
- Login on the splash page (In the process of being fixed)
- Some update attempts to production data made through a development version of the web client
Additionally, if you set
FALLBACK=https://scratch.mit.edu, be aware that clicking on links to parts of the website not yet migrated over (currently such as
Profile, etc.) will take you to the Scratch website itself.
Some users have experienced difficulties when trying to get our web client to work on Windows. One solution could be to use Cygwin. If that doesn't work, you might want to use Wubi (Windows XP, Vista, 7) or Wubiuefi (Windows 8 or higher). Wubi(uefi) is a Windows Installer for Ubuntu that allows you to have Ubuntu and Windows on one disk, without the need of an extra partition.
This section is only relevant to the Scratch Team since it requires access to private repositories, so is not usable by 3rd party contributors.
Docker Quick Start (CLI)
Make sure you already have the Scratch REST API running locally in its docker environment.
$ docker-compose up
After this has launched you will be able to access a running copy of
scratch-www on port 8333 via
Dockerfile defines how a
scratch-www docker image is created.
docker-compose.yml takes care of launching
scratch-www into a development environment that is composed of other components, such as the Scratch REST API server and the legacy Scratch code. If you have not already setup the Scratch REST API in your local environment, you will need to modify
docker-compose.yml by removing
external: true from:
networks: scratchapi_scratch_network: external: true