UPDATE: This project is no longer maintained. Please check out Glitch.com instead.
Mozilla has made a strategic decision to sunset Thimble over the course of 2018-2019. We encourage you to check out Glitch and you can read our blog post to learn more about this partnership.
This also means that any issues, bugs, or pull requests created in this repository might not receive a reply or support. If you are encountering issues migrating your projects to Glitch or have questions about the partnership, please send us an email at [email protected].
Thimble is Mozilla's online code editor that makes it easy to create and publish your own web pages while learning HTML, CSS & JavaScript. You can try it online by visiting https://thimble.mozilla.org (or https://bramble.mofostaging.net for our staging server).
You can read more about some of Thimble's main features in the wiki, or watch a demo video.
Thimble uses a modified version of the amazing Brackets code editor updated to run within web browsers. You can read more about how it works in this blog post.
Thimble requires a modern web browser, and we recommend using Mozilla Firefox or Google Chrome. We use BrowserStack to test Thimble in modern browsers on different operating systems.
Thimble interacts with the Publish API (source managed in publish.webmaker.org) to store users, projects, files and other content as well as publish user projects.
For authentication and user management, Thimble uses Webmaker OAuth which consists of the Webmaker ID System (source managed in id.webmaker.org) and the Webmaker Login API (source managed in login.webmaker.org).
All three services are bundled together using Git subtrees to be run together using Vagrant, or, they may be run separately with Thimble manually.
Note: The Git subtree bundle mentioned above for use with the automated installation can be found in the /services
folder. It contains a subtree for each of the three services. These subtrees are not automatically kept in sync with their corresponding service's parent repositories. If you need to update one of the subtrees to match the history of its parent repository, follow these instructions:
git fetch https://github.com/mozilla/<service's repository name> <branch name>
Replace <service's repository name>
with the remote repository name of the service you are trying to update and <branch name>
with the name of the branch on that repository you want to update the subtree with.
For e.g. git fetch https://github.com/mozilla/publish.webmaker.org master
.
git subtree pull --prefix services/<service's repository name> https://github.com/mozilla/<service's repository name> <branch name> --squash
Replace <service's repository name>
and <branch name>
with the same values you used in the previous command.
For e.g. git subtree pull --prefix services/publish.webmaker.org https://github.com/mozilla/publish.webmaker.org master --squash
.
Note: If you aren't able to properly run virtualization software on your machine (for e.g. some versions of Windows only allow one virtualization client to run at a time and if that isn't VirtualBox, you can't run the required VirtualBox as well. This is often a problem if you have Docker installed on Windows) or are trying to host Thimble on your own, refer to the Manual Installation instructions instead.
In order for Thimble to be installed correctly, the following dependencies need to be installed in order:
setx VAGRANT_HOME c:\.vagrant.d -m
.
For further safety, you can also check to make sure your VM snapshots are stored in a folder without spaces. To do this, open the Virtualbox GUI, click Preferences > General > Default Machine Folder, and set your path here.git clone --recursive https://github.com/<your_username>/brackets.git
(replace <your_username>
with your Github username for the account you forked Brackets into)npm install
to install the dependencies for Bracketsnpm run build
to create the built editor files that will be used by Thimblenpm start
to start a server that will allow the editor to be accessed on http://localhost:8000/src
-- You can find out more information about setting up Brackets locally by referring to the instructions here
The first step is to fork and clone Thimble and navigate to the cloned directory in a terminal shell.
For the first time, you need to install Thimble's dependencies and start all dependent services. To do this, simply run the following commands in succession:
npm install
npm run env
vagrant up
This process can take a while depending on your internet connection speed as it needs to download all dependencies.
The Vagrant VM is set to use 1 virtual CPU and 1.5G of RAM. If you find you need to adjust these resource levels, you can do so in the /Vagrantfile
.
When Vagrant finishes provisioning the VM, all the services that Thimble relies on will be running. Now, you can start the Thimble server by running:
npm start
Once you see a log that says Client files have been built. You can now load Thimble at http://localhost:3500
, you can access Thimble on http://localhost:3500.
You can terminate the Thimble server by hitting Ctrl-C.
Once the Thimble server is on, if you make changes to any file inside the public
folder, your changes will automatically be picked up and you can see them by refreshing your browser tab. If you make changes to any other file, you will need to terminate the Thimble server and restart it using npm start
for the changes to take effect.
To suspend the VM and temporarily stop the services Thimble relies on, use vagrant suspend
(like putting it to sleep). You can also use vagrant halt
to do a full shutdown of the services.
To restart the VM and Thimble's services again, re-run vagrant up
.
To see logs for the services running in Vagrant, use npm run services:logs
.
You can also setup Thimble and its needed components outside Vagrant and Virtualbox. This might be needed if you want to:
In order for Thimble to be installed correctly, the following dependencies need to be installed:
The following is an abbreviated guide to getting it all set up. Please see each server's README for more details.
Please note: On Windows, use copy
instead of cp
npm install
to install dependenciesnpm run env
to create an environment filenpm start
to start the servercp sample.env .env
to create an environment filenpm install
to install dependenciesnpm start
to start the servernpm install
to install dependenciescp env.sample .env
to create an environment filenpm start
the serverinitdb -D /usr/local/var/postgres
to initialize PostreSQL
rm -rf /usr/local/var/postgres
to remove itpostgres -D /usr/local/var/postgres
to start the PostgreSQL servercreatedb publish
to create the Publish databasenpm install
to install dependenciesnpm run env
npm run knex
to seed the publish database created earliernpm start
to run the serverOnce everything is ready and running, Thimble will be available at http://localhost:3500/
To publish locally, you'll need to do the following...
createdb webmaker_oauth_test
to create a test databaseRun node scripts/create-tables.js
Edit scripts/test-data.sql
and replace its contents with:
INSERT INTO clients VALUES
( 'test',
'test',
'["password", "authorization_code"]'::jsonb,
'["code", "token"]'::jsonb,
'http://localhost:3500/callback' )
Run node scripts/test-data.js
INSERT 0 1
message if successfulTo publish locally, you'll need an account.
Sign In
if you have an account or click Create an account
and complete the process, you can use a fake emailIt's that simple! You are now ready to start using Thimble to its full potential!
Please refer to the Wiki for information on the localization procedures used in Thimble.
Our localization community is awesome! They work very hard to translate Thimble so that we can expand our global reach and engage even more users in other languages. We can't thank them enough!
To invalidate the production CloudFront distribution, make sure you have correct credentials set up in your env file. Then run node invalidate.js
. Alternatively, if you have access to the Heroku deployments, run the invalidation as a one-off dyno with heroku run npm run invalidate
Thimble uses the throng module to leverage Node's Cluster API for concurrency. To specify the number of server processes to start set WEB_CONCURRENCY
to a positive integer value.