DoenetTools 🍩

The core libraries underlying the Distributed Open Education Network (Doenet)

Local Development Setup

1. fork this repository and clone your fork.

• Fork the project on Github
• $ cd /path/to/desired/location
• $ git clone [email protected]:<your_github_username>/DoenetTools
• $ cd DoenetTools

2. Install Docker

If you have a Desktop Environment (If you don't know what that is, you probably do):

Install Docker Desktop

Skip to step 3

If you do not have a DE on your build machine, install docker-engine and docker-compose

• Find the instructions to install Docker Engine for your platform here
• Install Docker Compose

$ sudo curl -L "https://github.com/docker/compose/releases/download/1.25.4/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose

• Add the execute permission to the docker-compose file

$ sudo chmod +x /usr/local/bin/docker-compose

Hopefully you are now done installing docker.

Note: If the command docker-compose fails after installation, check your path. You can also create a symbolic link to /usr/bin or any other directory in your path.

$ sudo ln -s /usr/local/bin/docker-compose /usr/bin/docker-compose

3. Install dependencies

• Go to the DoenetTools folder

$ cd /path/to/desired/location/DoenetTools

• Use NPM to install the build utilities. (Dependencies)

$ npm install

4. Build and run the containers!

Make sure that Docker is running, then:

$ npm start

Yay, they are starting!

The first time it is run, this does a few things.

1. Download the base containers from Docker Hub. This will take a while since they are large.
2. Build Doenet's environment on top of the base containers.
3. Start the containers in Doenet's composition.
4. Apache and PHP start. These are pretty quick, although if you try to access the website now, you wont get much since seeing the project depends on the MySQL database and the Webpacked project.
5. MySQL runs some first time setup. It sets up a new database and imports the database template that you downloaded when cloning this project. a. You can tell this is done when the text Version: '5.7.29' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server (GPL) appears, signaling that mysql is done starting and is ready for connections on port 3306.
6. Webpack (Node) runs a full pack on the project. This will be done every time the container starts. And it takes a while. Once the first pack is done, subsequent packs usually happen very quickly. a. You can tell the initial pack is done when the terminal shows something like

node_1    | Hash: [something]
node_1    | Version: webpack [something]
node_1    | Time: [something]ms
node_1    | Built at: [something]
node_1    | 
...[potential warnings and errors]...
node_1    |                                     ..,,,,,..
node_1    |                            ,,,,,,,,,,,,,,,,,,,,,,,,,,,
node_1    |                       ,,,,,,,.......................,,,,,,,
node_1    |                   .,,,,,.................................,,,,,.
node_1    |                .,,,,......................*///,.............,,,,,
node_1    |              .,,,,..................%*             %,..........,,,,.
node_1    |            .,,,...........&#   &.,/                   &..........,,,,.
node_1    |           ,,,,.........#                                %..........,,,,
node_1    |         .,,,..........&.            .*(##(*.             ,...........,,,
node_1    |        .,,,...........&.        %##############%          %...........,,,
node_1    |        ,,,.........(%#,%.     %%#######//#%%%#####        &............,,,
node_1    |       ,,,......%....         (%%####*      /%#####/          .##.......,,,,
node_1    |       ,,,....#..             /%%%#################*              ,,.....,,,
node_1    |      ,,,,....,.               **(%%%###########(**                ,,....,,,.
node_1    |      ,,,.....*.                  **************                   ,.....,,,.
node_1    |      ,,,,....%.                                                  ,*.....,,,.
node_1    |       ,,,...../*..                .............................(/.......,,,
node_1    |       ,,,........./###((((///////////****,,,,,............@@@@@@@@.....,,,,
node_1    |        ,,,.........@@@@........@@@@....@@@@@.@@....@@.@@@@@..@@........,,,
node_1    |         ,,,........@@..@@@...@@@..@@@..@@....@@@...@@.@@.....@@.......,,,
node_1    |          ,,,.......@@...@@..@@......@@.@@@@@.@@.@..@@.@@@@@..@@.....,,,,
node_1    |           ,,,,.....@@...@@..@@......@@.@@....@@..@.@@.@@.....@@....,,,,
node_1    |            .,,,,...@@..@@@...@@@..@@@..@@....@@...@@@.@@.....@@..,,,,
node_1    |              .,,,,.@@@@........@@@@....@@@@@.@@....@@.@@@@@..@@,,,,
node_1    |                 ,,,,,.......................................,,,,,
node_1    |                   .,,,,,,...............................,,,,,,
node_1    |                       ,,,,,,,......................,,,,,,,.
node_1    |                            .,,,,,,,,,,,,,,,,,,,,,,,,,.
node_1    |                                      .......

5. Stopping the containers

When you are not using them, you can stop the docker containers by going to the terminal you started them with and using ctrl+c. Let the containers stop gracefully. Keep in mind that Webpack takes a while to get going, so you probably don't want to stop the containers until you are done for the day. Or you can leave them running indefinitely.

Usage

Visit localhost in your browser to test the project. When you make changes to the code in the code in /static or /src, the Docker containers will automatically build the changes and serve the new files. There will be output to the terminal and you must reload pages manually.

Run the containers

To run the containers, you can just run $ npm start in the project's root directory. This command will only build the containers if they are not already built.

Note: You must have docker running before you can start the containers.

Stop the containers

Option 1: Use ctrl+c in the terminal that you started them with.

Option 2: Stop all four containers using whatever docker interface you have. The containers are "doenet_docker_node", "doenet_docker_apache", "doenet_docker_mysql", and "doenet_docker_php".

Re-build the containers.

If you need to re-build the containers for whatever reason, run $ npm run docker:build. Not to be confused with $ npm run build which will build the website for production.

Directly access the database

The database is exposed to your local machine by port 3306. You can use a program such as Sequel Pro (Mac), MySQLWorkbench (Most OS), or the MySQL CLI to interact with the database directly.

If port 3306 is in use, you can change the port in the docker-compose.yml file:

  mysql:
    build: './mysql'
    ports:
      - 3306:3306
      # - <desired_port>:3306
    volumes:
      - ./volumes/db:/var/lib/mysql
    restart: always

Create a new database template

If you want to save your current database as a template, run the following in bash in your mysql container:

Note: Make sure you don't already have a file in DoenetCourse/doenet_docker/volumes/db_init/dbdump.sql. If you do, this command will overwrite it!

$ mysqldump --all-databases --password=helloworld > /docker-entrypoint-initdb.d/dbdump.sql

You can then see this file at DoenetCourse/doenet_docker/volumes/db_init/dbdump.sql. You may want to verify that the database exported correctly before continuing.

To use a new database template:

1. Stop the docker containers.
2. Delete the old DoenetCourse/doenet_docker/volumes/db_init/db_template.sql.
3. Rename the dump file to db_template.sql.
4. Delete the contents (except for .gitignore) of DoenetCourse/doenet_docker/volumes/db/.
5. Start the containers:

$ npm start

6. Pet your cat (Optional). :3

Run only the LAMP stack in Docker

In certain use cases you may only want to run the LAMP stack in docker. For example, you may just want to demonstrate the project with an already present development build but you don't want the jet engine noises that come with starting Webpack (when it runs a full compilation).

To do this:

$ npm run docker:lamp

Usage of the LAMP stack is the same as it is for the full stack Docker composition.

Also keep in mind that the LAMP only uses the same database and database template as the full stack composition. If you want to change anything about the database or database template, follow the same instructions you would for the full stack composition.

Run only Webpack

In certain cases—such as when you are running your own AMP/NMP stack—you may want to run Webpack on its own. You have two options for this. Inside and outside its own Docker container.

Run only Webpack in Docker

$ npm run docker:webpack

Run Webpack outside of Docker

$ npm run webapck

Use your own AMP/NMP stack (advanced)

• Install a webserver that is compatible with PHP, we recommend Apache.
  • We use Apache 2.4.41 in Docker.
• Install PHP.
  • We use PHP 7.4 in Docker, we have also used 7.3.8.
• Install MySQL. You can probably also use MariaDB, but we have not tested that.
  • We use MySQL 7.7.26 in Docker.
• Have your server serve from /path/to/DoenetCourse/dist_local/.
  • Use port 3000.
• Initialize your MySQL database with /path/to/DoenetCourse/doenet_docker/volumes/db_init/db_template.sql.
  • Use the default port. (3306)
• Make sure the node dependencies are installed
  • npm install
• Run Webpack. (Or don't.)
  • Use $ npm run webpack to run Webpack on your normal namespace (not Docker).
    OR
  • Use $ npm run docker:webpack to run Webpack in Docker.

Notes:

You may also get MariaDB to work. Please let us know if you do. c:

We have not tested the current configuration with Nginx, you are on your own if you choose to use it. If you do, we would love to hear about how it turned out. c:

You must use port 80 for Apache/Nginx or our PHP probably won't work on your stack.