Lesson 1

.gitignore

@@ -0,0 +1,20 @@
+# dependencies
+node_modules/
+
+# production
+frontend/build
+
+#compile contract files
+**/*.abi
+**/*.wasm
+**/*.wast
+
+#blockchain data
+**/data/*
+
+# misc
+.DS_Store
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*

.nvmrc

@@ -0,0 +1 @@
+v8.11.3

Contributing.md

@@ -0,0 +1,139 @@
+# Contributing to developer documentation site
+
+Interested in contributing? That's awesome! Here are some guidelines to get started quickly and easily:
+
+- [Reporting An Issue](#reporting-an-issue)
+  - [Reporting A Game Issue](#reporting-a-game-issue)
+  - [New Feature Request](#new-feature-request)
+  - [Change Requests](#change-requests)
+- [Working on Elemental Battles](#working-on-elemental-battles)
+  - [Branches](#branches)
+  - [Submitting Pull Requests](#submitting-pull-requests)
+- [Conduct](#conduct)
+- [Contributor License & Acknowledgments](#contributor-license--acknowledgments)
+- [References](#references)
+
+## Reporting An Issue
+
+If you're about to raise an issue because you think you've found a problem with documentation, please read this first.
+
+The GitHub issue tracker is the preferred channel for [Reporting A Game Issue](#reporting-a-game-issue), [New Feature Requests](#new-feature-request), and [Submitting Pull Requests](#submitting-pull-requests), but please respect the following restrictions:
+
+* Please **search for existing issues**. Help us keep duplicate issues to a minimum by checking to see if someone has already reported your problem or requested your idea.
+
+* Please **be civil**. Keep the discussion on topic and respect the opinions of others. See also our [Contributor Code of Conduct](#conduct).
+
+### Reporting a Game Issue
+
+A game issue is a _demonstrable problem_ that is present in the card-game repository. Good reports are extremely helpful - thank you!
+
+Guidelines for documentation issue reports:
+
+1. **Use the GitHub issue search** — check if the issue has already been reported.
+
+2. **Check if the issue has been fixed** — look for [closed issues in the
+   current milestone](https://github.com/EOSIO/eosio-card-game-repo/issues?q=is:issue+is:closed) or try to find it using the latest branch for the relevant lesson.
+
+A good issue report shouldn't leave others needing to chase you up for more information. Be sure to include the details of your environment and relevant tests that demonstrate the problem.
+
+[Report an issue](https://github.com/EOSIO/eosio-card-game-repo/issues/new?title=%5Bdocs%5D%20Suggestion%20/%20Change%20Request)
+
+### New Feature Request
+
+New feature requests are welcome. Before you submit one be sure to have:
+
+1. **Use the GitHub search** and check the new document hasn't already been requested.
+2. Take a moment to think about whether your idea fits with the scope and aims of the project.
+3. Remember, it's up to *you* to make a strong case to convince the project's leaders of the merits of this documentation request.
+
+### Change Requests
+
+If you have an idea for improvement - please be sure to:
+
+1. **Use the GitHub search** and check someone else didn't get there first
+2. Take a moment to think about the best way to make a case for, and explain what you're thinking. Are you sure this shouldn't really be
+   [New Feature Request](#new-feature-request)?  Is it really one idea or is it many? What's the context? Why is what you are suggesting better than what's already there?
+
+## Working on Elemental Battles
+
+Contributions are welcome and encouraged! If you are looking for a good place to start, check out the [good first issue](https://github.com/EOSIO/eosio-card-game-repo/labels/good%20first%20issue) label in GitHub issues.
+
+Also, please follow these guidelines when submitting your proposed documentation changes:
+
+### Branches
+
+To get it out of the way:
+
+- **Lesson Branches** contain the contents of each lesson. Changes are usually made in lesson-0 or lesson-1 and then merged into later lesson branches to ensure consistency.
+- **[master](https://github.com/EOSIO/welcome/tree/master)** contains the main README file only.Do **NOT** use this branch to add any code.
+
+### Submitting Pull Requests
+
+Pull requests are awesome. If you're looking to raise a PR for something which doesn't have an open issue, please think carefully about [raising an issue](#reporting-an-issue) which your PR can close. This makes it more likely that there will be enough information available for your PR to be properly tested and merged.
+
+## Conduct
+
+While contributing, please be respectful and constructive, so that participation in our project is a positive experience for everyone.
+
+Examples of behavior that contributes to creating a positive environment include:
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior include:
+- The use of sexualized language or imagery and unwelcome sexual attention or advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others’ private information, such as a physical or electronic address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Contributor License & Acknowledgments
+
+Whenever you make a contribution to this project, you license your contribution under the terms of the [MIT LICENSE](https://github.com/EOSIO/eos/blob/master/LICENSE), and you represent and warrant that you have the right to license your contribution under those terms.  Whenever you make a contribution to this project, you also certify in the terms of the Developer’s Certificate of Origin set out below:
+
+```
+Developer Certificate of Origin
+Version 1.1
+
+Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
+1 Letterman Drive
+Suite D4700
+San Francisco, CA, 94129
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+
+
+Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I
+    have the right to submit it under the open source license
+    indicated in the file; or
+
+(b) The contribution is based upon previous work that, to the best
+    of my knowledge, is covered under an appropriate open source
+    license and I have the right under that license to submit that
+    work with modifications, whether created in whole or in part
+    by me, under the same open source license (unless I am
+    permitted to submit under a different license), as indicated
+    in the file; or
+
+(c) The contribution was provided directly to me by some other
+    person who certified (a), (b) or (c) and I have not modified
+    it.
+
+(d) I understand and agree that this project and the contribution
+    are public and that a record of the contribution (including all
+    personal information I submit with it, including my sign-off) is
+    maintained indefinitely and may be redistributed consistent with
+    this project or the open source license(s) involved.
+```
+
+## References
+
+* Overall CONTRIB adapted from https://github.com/mathjax/MathJax/blob/master/CONTRIBUTING.md
+* Conduct section adapted from the Contributor Covenant, version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

CopyrightNotice.md

@@ -0,0 +1 @@
+Copyright (c) 2017-2020 block.one and its contributors.  All rights reserved.

Dockerfile

@@ -0,0 +1,7 @@
+FROM ubuntu:18.04
+
+RUN apt-get update && apt-get install -y wget sudo curl
+RUN wget https://github.com/EOSIO/eosio.cdt/releases/download/v1.6.3/eosio.cdt_1.6.3-1-ubuntu-18.04_amd64.deb
+RUN apt-get update && sudo apt install -y ./eosio.cdt_1.6.3-1-ubuntu-18.04_amd64.deb
+RUN wget https://github.com/EOSIO/eos/releases/download/v2.0.5/eosio_2.0.5-1-ubuntu-18.04_amd64.deb
+RUN apt-get update && sudo apt install -y ./eosio_2.0.5-1-ubuntu-18.04_amd64.deb

ImportantNotice.md

@@ -0,0 +1,27 @@
+# Important Notice
+
+We (block.one and its affiliates) make available EOSIO and other software, updates, patches and documentation (collectively, Software) on a voluntary basis as a member of the EOSIO community.  A condition of you accessing any Software, websites, articles, media, publications, documents or other material (collectively, Material) is your acceptance of the terms of this important notice.
+
+## Software
+We are not responsible for ensuring the overall performance of Software or any related applications.  Any test results or performance figures are indicative and will not reflect performance under all conditions.  Software may contain components that are open sourced and subject to their own licenses; you are responsible for ensuring your compliance with those licenses.
+
+We make no representation, warranty, guarantee or undertaking in respect of Software, whether expressed or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement.  In no event shall we be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the Software or the use or other dealings in the Software.  
+
+Wallets and related components are complex software that require the highest levels of security. If incorrectly built or used, they may compromise users’ private keys and digital assets. Wallet applications and related components should undergo thorough security evaluations before being used. Only experienced developers should work with such Software.
+
+Material is not made available to any person or entity that is the subject of sanctions administered or enforced by any country or government or otherwise designated on any list of prohibited or restricted parties (including but not limited to the lists maintained by the United Nations Security Council, the U.S. Government, the European Union or its Member States, or other applicable government authority) or organized or resident in a country or territory that is the subject of country-wide or territory-wide sanctions.  You represent and warrant that neither you nor any party having a direct or indirect beneficial interest in you or on whose behalf you are acting as agent or nominee is such a person or entity and you will comply with all applicable import, re-import, sanctions, anti-boycott, export, and re-export control laws and regulations.  If this is not accurate or you do not agree, then you must immediately cease accessing our Material and delete all copies of Software.
+
+Any person using or offering Software in connection with providing software, goods or services to third parties shall advise such third parties of this important notice, including all limitations, restrictions and exclusions of liability.
+
+## Trademarks
+Block.one, EOSIO, EOS, the heptahedron and associated logos and related marks are our trademarks.  Other trademarks referenced in Material are the property of their respective owners.
+
+## Third parties
+Any reference in Material to any third party or third-party product, resource or service is not an endorsement or recommendation by Block.one.  We are not responsible for, and disclaim any and all responsibility and liability for, your use of or reliance on any of these resources. Third-party resources may be updated, changed or terminated at any time, so information in Material may be out of date or inaccurate.
+
+## Forward-looking statements
+Please note that in making statements expressing Block.one’s vision, we do not guarantee anything, and all aspects of our vision are subject to change at any time and in all respects at Block.one’s sole discretion, with or without notice. We call these “forward-looking statements”, which includes statements on our website and in other Material, other than statements of historical facts, such as statements regarding EOSIO’s development, expected performance, and future features, or our business strategy, plans, prospects, developments and objectives. These statements are only predictions and reflect Block.one’s current beliefs and expectations with respect to future events; they are based on assumptions and are subject to risk, uncertainties and change at any time. 
+
+We operate in a rapidly changing environment and new risks emerge from time to time. Given these risks and uncertainties, you are cautioned not to rely on these forward-looking statements. Actual results, performance or events may differ materially from what is predicted in the forward-looking statements. Some of the factors that could cause actual results, performance or events to differ materially from the forward-looking statements include, without limitation: technical feasibility and barriers; market trends and volatility; continued availability of capital, financing and personnel; product acceptance; the commercial success of any new products or technologies; competition; government regulation and laws; and general economic, market or business conditions. 
+
+All statements are valid only as of the date of first posting and Block.one is under no obligation to, and expressly disclaims any obligation to, update or alter any statements, whether as a result of new information, subsequent events or otherwise.  Nothing in any Material constitutes technological, financial, investment, legal or other advice, either in general or with regard to any particular situation or implementation. Please consult with experts in appropriate areas before implementing or utilizing anything contained in Material.

README.md

@@ -1,12 +1,50 @@
-# Elemental Battles Tutorial Lessons
+# Elemental Battles Tutorial Lesson 1
 
-The Elemental Battles Tutorial is divided into easy to follow lessons that take you through the process of creating your own fully-functional blockchain-based dApp.
+- *Account*: `player1`
+- *Private Key*: `5KFyaxQW8L6uXFB6wSgC44EsAbzC7ideyhhQ68tiYfdKQp69xKo`
+The account information is available in [eosio_docker/scripts/accounts.json](eosio_docker/scripts/accounts.json). The key pair in this file is generated **FOR TESTING ONLY** so please **DO NOT** use them for any other purposes.
 
-Each lesson will introduce new concepts and showcase how to include them in the existing code. Additionally, we will display explanations and source code side-by-side to make following the tutorial easy.
+## Prerequisites
 
-## About this repository
+Make sure Docker and Node.js are installed
 
-This repository contains the source code used in each of the tutorial lesson. Each lesson's code are stored in a branch. You can find all the lesson branches from the list below.
+* Install Docker: https://docs.docker.com/docker-for-mac/install/
+* Install Node.js: https://nodejs.org/en/
+
+The DApp and eosio will occupy the ports 3000, 8888 and 9876. Make sure nothing else is already running on these ports.
+
+Clone the repository:
+```sh
+git clone https://github.com/EOSIO/eosio-card-game-repo.git
+```
+
+The following guide assumes you are using macOS.
+
+## Quick start - Run the DApp
+
+In this section we provide a single command script to run all the commands needed to start both the blockchain and UI. For more detail on each component see the `Detailed guide` below.
+
+**To start**
+```sh
+./quick_start.sh
+```
+
+The above command will execute the following in sequence:
+
+1. `first_time_setup.sh`
+2. `start_eosio_docker.sh`
+3. `start_frontend.sh`
+
+- Login with the following credentials:
+
+**To stop**, press `ctrl+c` on your keyboard, and execute:
+```sh
+docker stop eosio_cardgame_container
+```
+
+## Detailed guide
+
+Please refer to [eosio-project-boilerplate-simple - Detailed guide](https://github.com/EOSIO/eosio-project-boilerplate-simple/blob/master/README.md#detailed-guide) for more information. This repository is using the similar structure as that.
 
 ## Lesson List
 
@@ -27,3 +65,33 @@ This repository contains the source code used in each of the tutorial lesson. Ea
   [Lesson 7: Building the Game Flow](https://github.com/EOSIO/eosio-card-game-repo/tree/lesson-7)
 
   [Lesson 8: Wrapping Up The Game](https://github.com/EOSIO/eosio-card-game-repo/tree/lesson-8)
+
+## Contributing
+
+See [Contributing](./Contributing.md)
+
+## Conduct
+
+While contributing, please be respectful and constructive, so that participation in our project is a positive experience for everyone.
+
+Examples of behavior that contributes to creating a positive environment include:
+
+•	Using welcoming and inclusive language
+•	Being respectful of differing viewpoints and experiences
+•	Gracefully accepting constructive criticism
+•	Focusing on what is best for the community
+•	Showing empathy towards other community members
+
+Examples of unacceptable behavior include:
+
+•	The use of sexualized language or imagery and unwelcome sexual attention or advances
+•	Trolling, insulting/derogatory comments, and personal or political attacks
+•	Public or private harassment
+•	Publishing others’ private information, such as a physical or electronic address, without explicit permission
+•	Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Important
+
+See [Copyright Notice](./CopyrightNotice.md) for copyright terms.
+
+All repositories and other materials are provided subject to the terms of this [IMPORTANT](./ImportantNotice.md) notice and you must familiarize yourself with its terms. The notice contains important information, limitations and restrictions relating to our software, publications, trademarks, third-party resources, and forward-looking statements. By accessing any of our repositories and other materials, you accept and agree to the terms of the notice.

contracts/cardgame/cardgame.cpp

@@ -0,0 +1 @@
+#include "gameplay.cpp"

contracts/cardgame/cardgame.hpp

@@ -0,0 +1,11 @@
+#include <eosio/eosio.hpp>
+
+using namespace std;
+using namespace eosio;
+class [[eosio::contract]] cardgame : public eosio::contract {
+
+  public:
+
+    cardgame( name receiver, name code, datastream<const char*> ds ):contract(receiver, code, ds) {}
+
+};

contracts/cardgame/gameplay.cpp

@@ -0,0 +1 @@
+#include "cardgame.hpp"

eosio_docker/scripts/accounts.json

@@ -0,0 +1,3 @@
+[
+  {"name":"player1", "privateKey":"5KFyaxQW8L6uXFB6wSgC44EsAbzC7ideyhhQ68tiYfdKQp69xKo", "publicKey":"EOS8Du668rSVDE3KkmhwKkmAyxdBd73B51FKE7SjkKe5YERBULMrw"}
+]

eosio_docker/scripts/continue_blockchain.sh

@@ -0,0 +1,31 @@
+#!/usr/bin/env bash
+set -o errexit
+
+# this file is used to continue the stopped blockchain
+
+echo "=== start blockchain with  ==="
+
+# set PATH
+PATH="$PATH:/opt/eosio/bin"
+
+set -m
+
+# start nodeos ( local node of blockchain )
+# run it in a background job such that docker run could continue
+nodeos -e -p eosio -d /mnt/dev/data \
+  --config-dir /mnt/dev/config \
+  --hard-replay \
+  --http-validate-host=false \
+  --plugin eosio::producer_plugin \
+  --plugin eosio::history_plugin \
+  --plugin eosio::chain_api_plugin \
+  --plugin eosio::history_api_plugin \
+  --plugin eosio::http_plugin \
+  --http-server-address=0.0.0.0:8888 \
+  --access-control-allow-origin=* \
+  --contracts-console \
+  --verbose-http-errors
+
+# `--hard-replay` option is needed
+# because the docker stop signal is not being passed to nodeos process directly
+# as we run the init_blockchain.sh as PID 1.