Code Monkey home page Code Monkey logo

eos-local's Introduction

MIT

EOS Mainnet Local Network

Description

EOS Local provides a quick way to setup an EOS local network for development.

The primary benefits of containers are consistency across different environments and deployment ease.

This project works along with a full-stack-boilerplate to help you build your EOS dApp.

Why to use a local environment?

Having a local environment provides a series of benefits that you cannot in a public network, for example, with EOS Mainnet locally, transaction costs are avoided since they are carried out in a development environment and not in production, also, they are accessed to system contracts to modify them as appropriate.

In a Blockchain network every transaction creates an immutable record and everything that is modified can affect both positively and negatively the users within it, it is for this reason that it is essential to have an environment premises where functionality tests, performance tests, stress tests, among others, can be carried out without the risk of producing a failure that affects users.

Finally, a factor to consider is the time that is reduced in the initial configuration of any network, this image allows directly, with only two commands to have the network installed and ready to perform functionality tests as necessary.

Contracts

The EOSIO image is based on the eosio.system, eosio.token and eosio.msig contracts for its configuration. Your code can be found at this link.

  1. eosio.system: Defines the structures and actions needed for blockchain's core functionality.
  2. eosio.token: Defines the structures and actions that allow users to create, issue, and manage tokens for EOSIO-based blockchains.
  3. eosio.msig: Allows the creation of proposed transactions that require authorization from a list of accounts.

Deployable projects

As EOS Mainnet Local Network is based on EOSIO protocol, some already smart contract production projects can be deployed on our local network due to the local dev environment setup. Some of them are:

  1. Eden: Take a look at the smart contract code here.
  2. simpleassets: A simple standard for digital assets on EOSIO blockchains: Non-Fungible Tokens (NFTs), Fungible Tokens (FTs), and Non-Transferable Tokens (NTTs). Take a look at the smart contract code here.
  3. atomicassets: AtomicAssets is a Non Fungible Token (NFT) standard for eosio blockchains developed by pink.network. Take a look at the smart contract code here.
  4. dgoods: dGoods is an open source and free standard for handling the virtual representation of items, both digital and physical, on the EOS blockchain led by Mythical Games. Take a look at the smart contract code here.

Configuration key

The preconfigured key to setup our genesis node is passed throw Dockerfile using the --build-arg option, so make sure to create a start key and save it to continue using the local dev environment with full access.

To create a key, you can use cleos create key --to-console or cleos create key --file <file_name>.key depending on your preference:

Private key: 5Jkvw1DbsGx7W8vSnrHtXSYxM9bfKoJvwEnH51KJYQGv6D5LZyA
Public key: EOS5FCRb5XtkMKFTow2dfPQDQ11ZbfYrmhP4rxWPzZn6pzp1nugpz

Prerequisites

Quick start

  • Download the Docker image docker pull eoscostarica506/eos-local
  • Run the Docker image docker run -dp 8888:8888 eoscostarica506/eos-local
  • Run the command cleos get info or check the link in the browser http://127.0.0.1:8888/v1/chain/get_info

If you run the command cleos get info or go to http://127.0.0.1:8888/v1/chain/get_info and get information like the following it is because you already have the environment ready to work.

{"server_version":"e57a1eab","chain_id":"981453d176ddca32aa278ff7b8af9bf4632de00ab49db273db03115705d90c5a","head_block_num":66,"last_irreversible_block_num":65,"last_irreversible_block_id":"00000041fcc36403c71cebfc95810f610412b474f60735639fcaa2d241fe5ffa","head_block_id":"00000042a08478812c642d311f5ff22b9212559eeb9ee1042925742d8b46dd7f","head_block_time":"2021-07-08T05:48:45.500","head_block_producer":"eosio","virtual_block_cpu_limit":213407,"virtual_block_net_limit":1118998,"block_cpu_limit":199900,"block_net_limit":1048576,"server_version_string":"v2.0.12","fork_db_head_block_num":66,"fork_db_head_block_id":"00000042a08478812c642d311f5ff22b9212559eeb9ee1042925742d8b46dd7f","server_full_version_string":"v2.0.12-e57a1eab619edffc25afa7eceb05a01ab575c34a"}

Note: As the docker image were pulled from eoscostarica506, the eosio keys are:

Private key: 5JV5XER5ouVYfghE6AEgDeViqkH4VNAJaxwB6wVe4Mk2JHZywPQ
Public key: EOS5hyZZRePAFyKVTEReHLErXviH6chc3w84pQcwtHnsNJWCWj3Jp

Instructions for creating EOS Mainnet Local Network image locally

To create the Docker image locally, you must run the following commands:

  • Clone the local Eos repository https://github.com/eoscostarica/eos-local
  • Enter to the cloned repository folder cd <path/eos-local>
  • Copy the example env file .env.example with cp .env.example .env and fill it with your keys
  • Build the Dockerfile image with env variables make build-docker or docker build -t eos-local --build-arg testnet_eosio_public_key="<public_key>" --build-arg testnet_eosio_private_key="<private_key>" .
  • Run the Dockerfile image make run or docker run -dp 8888:8888 eos-local
  • Run the command cleos get info or check the link in the browser http://127.0.0.1:8888/v1/chain/get_info

By this point, you already have the EOS Mainnet Local Network image running locally.

File structure

/
β”œβ”€β”€ .github
β”‚   └── workflows
β”‚       └── publish-docker-image.yml
β”œβ”€β”€ docs ..................... Some media content for README
β”œβ”€β”€ config.ini ............... Nodeos configuration file
β”œβ”€β”€ Dockerfile ............... Contains instructions for building the EOS Mainnet Local Network image
β”œβ”€β”€ genesis.json ............. Specifies the network genesis node parameters
β”œβ”€β”€ LICENSE .................. Terms and Conditions
β”œβ”€β”€ README.md ................ Repository specification
└── start.sh ................. Instructions for configuring contracts and usage characteristics

License

MIT Β© EOS Costa Rica

Contributing

If you want to contribute to this repository, please follow the steps below:

  1. Fork the project
  2. Create a new branch (git checkout -b feat/sometodo)
  3. Commit changes (git commit -m '<type>(<scope>): <subject>')
  4. Push the commit (git push origin feat/sometodo)
  5. Open a Pull Request

Read the EOS Costa Rica open source contribution guidelines for more information on scheduling conventions.

If you find any bugs, please report them by opening an issue at this link.

What is EOSIO?

EOSIO is a highly performant open-source blockchain platform, built to support and operate safe, compliant, and predictable digital infrastructures.

About EOS Costa Rica



EOS Costa Rica is an independently-owned, self-funded, bare-metal Genesis block producer that provides stable and secure infrastructure for EOSIO blockchains. We support open source software for our community while offering enterprise solutions and custom smart contract development for our clients.

eoscostarica.io

eos-local's People

Contributors

danazkari avatar gaboesquivel avatar gmory avatar joseboga avatar jsegura17 avatar leisterfrancisco avatar lucca65 avatar marianocodes avatar murillojorge avatar rubenabix avatar xavier506 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

eos-local's Issues

Reusability discussion

I would like to be able to run other apps on EOS Local without needing to fork or duplicate code, Ideally I want keep getting upgrades from EOS Local main repo and run all my dapps against it.

What would be a good setup for this? Perhaps git submodules for starters ?

make compile command

the make compile command should recompile your contracts using the eosio.cdt docker image.

Replace gulp-cli with eoslocal cli

We decided to use gulp instead of yarn to prevent yarn inception confusion since there are services using yarn already.

It would be even clearer if we had an eoslocal cli.

Gulp works for now, however gulp-cli doesn't support additional parameters being passed without flags. There for yarn cleos get info cannot be transalated to gulp cleos get info.. it would be great to support this with our cli eoslocal cleos get info.

I'm sure there are other cases where this would be handy.

Fail to build

Github workflows take too long and can't be created

Design Greetings Demo Inteface

The sample website will consist on a feed of greetings and a text box to send your greeting.

Let's design a simple and nice interface for it.

Problem running 'make setup'

When I run make setup, the eosio container gets stuck in the compilation of the contracts. Tried several times and it always stops at the same point:

[ 57%] Linking CXX executable eosio.bios.wasm

This is the relevant log:

=========== Building eosio.contracts ===========

-- The C compiler identification is Clang 4.0.1
-- The CXX compiler identification is Clang 4.0.1
-- Check for working C compiler: /usr/bin/clang
-- Check for working C compiler: /usr/bin/clang -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/clang++
-- Check for working CXX compiler: /usr/bin/clang++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Setting up Eosio Wasm Toolchain 1.5.0 at /usr
-- Using eosio.cdt version 1.5.0
-- Found Git: /usr/bin/git (found version "2.17.1")
-- Configuring done
-- Generating done
-- Build files have been written to: /opt/eosio.contracts/build
Scanning dependencies of target contracts_unit_tests
[  5%] Creating directories for 'contracts_unit_tests'
[ 10%] No download step for 'contracts_unit_tests'
[ 15%] No patch step for 'contracts_unit_tests'
[ 21%] No update step for 'contracts_unit_tests'
[ 26%] Performing configure step for 'contracts_unit_tests'
-- The C compiler identification is Clang 4.0.1
-- The CXX compiler identification is Clang 4.0.1
-- Check for working C compiler: /usr/bin/clang
-- Check for working C compiler: /usr/bin/clang -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/clang++
-- Check for working CXX compiler: /usr/bin/clang++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Setting up Eosio Tester 1.5.2 at /opt/eosio
CMake Warning at /usr/local/share/cmake-3.9/Modules/FindBoost.cmake:786 (message):
  New Boost version may have incorrect or missing dependencies and imported
  targets
Call Stack (most recent call first):
  /usr/local/share/cmake-3.9/Modules/FindBoost.cmake:892 (_Boost_COMPONENT_DEPENDENCIES)
  /usr/local/share/cmake-3.9/Modules/FindBoost.cmake:1523 (_Boost_MISSING_DEPENDENCIES)
  /opt/eosio/lib/cmake/eosio/EosioTester.cmake:44 (find_package)
  /opt/eosio/lib/cmake/eosio/eosio-config.cmake:5 (include)
  CMakeLists.txt:7 (find_package)


CMake Warning at /usr/local/share/cmake-3.9/Modules/FindBoost.cmake:786 (message):
  New Boost version may have incorrect or missing dependencies and imported
  targets
Call Stack (most recent call first):
  /usr/local/share/cmake-3.9/Modules/FindBoost.cmake:892 (_Boost_COMPONENT_DEPENDENCIES)
  /usr/local/share/cmake-3.9/Modules/FindBoost.cmake:1523 (_Boost_MISSING_DEPENDENCIES)
  /opt/eosio/lib/cmake/eosio/EosioTester.cmake:44 (find_package)
  /opt/eosio/lib/cmake/eosio/eosio-config.cmake:5 (include)
  CMakeLists.txt:7 (find_package)


CMake Warning at /usr/local/share/cmake-3.9/Modules/FindBoost.cmake:786 (message):
  New Boost version may have incorrect or missing dependencies and imported
  targets
Call Stack (most recent call first):
  /usr/local/share/cmake-3.9/Modules/FindBoost.cmake:892 (_Boost_COMPONENT_DEPENDENCIES)
  /usr/local/share/cmake-3.9/Modules/FindBoost.cmake:1523 (_Boost_MISSING_DEPENDENCIES)
  /opt/eosio/lib/cmake/eosio/EosioTester.cmake:44 (find_package)
  /opt/eosio/lib/cmake/eosio/eosio-config.cmake:5 (include)
  CMakeLists.txt:7 (find_package)


CMake Warning at /usr/local/share/cmake-3.9/Modules/FindBoost.cmake:786 (message):
  New Boost version may have incorrect or missing dependencies and imported
  targets
Call Stack (most recent call first):
  /usr/local/share/cmake-3.9/Modules/FindBoost.cmake:892 (_Boost_COMPONENT_DEPENDENCIES)
  /usr/local/share/cmake-3.9/Modules/FindBoost.cmake:1523 (_Boost_MISSING_DEPENDENCIES)
  /opt/eosio/lib/cmake/eosio/EosioTester.cmake:44 (find_package)
  /opt/eosio/lib/cmake/eosio/eosio-config.cmake:5 (include)
  CMakeLists.txt:7 (find_package)


CMake Warning at /usr/local/share/cmake-3.9/Modules/FindBoost.cmake:786 (message):
  New Boost version may have incorrect or missing dependencies and imported
  targets
Call Stack (most recent call first):
  /usr/local/share/cmake-3.9/Modules/FindBoost.cmake:892 (_Boost_COMPONENT_DEPENDENCIES)
  /usr/local/share/cmake-3.9/Modules/FindBoost.cmake:1523 (_Boost_MISSING_DEPENDENCIES)
  /opt/eosio/lib/cmake/eosio/EosioTester.cmake:44 (find_package)
  /opt/eosio/lib/cmake/eosio/eosio-config.cmake:5 (include)
  CMakeLists.txt:7 (find_package)


CMake Warning at /usr/local/share/cmake-3.9/Modules/FindBoost.cmake:786 (message):
  New Boost version may have incorrect or missing dependencies and imported
  targets
Call Stack (most recent call first):
  /usr/local/share/cmake-3.9/Modules/FindBoost.cmake:892 (_Boost_COMPONENT_DEPENDENCIES)
  /usr/local/share/cmake-3.9/Modules/FindBoost.cmake:1523 (_Boost_MISSING_DEPENDENCIES)
  /opt/eosio/lib/cmake/eosio/EosioTester.cmake:44 (find_package)
  /opt/eosio/lib/cmake/eosio/eosio-config.cmake:5 (include)
  CMakeLists.txt:7 (find_package)


CMake Warning at /usr/local/share/cmake-3.9/Modules/FindBoost.cmake:786 (message):
  New Boost version may have incorrect or missing dependencies and imported
  targets
Call Stack (most recent call first):
  /usr/local/share/cmake-3.9/Modules/FindBoost.cmake:892 (_Boost_COMPONENT_DEPENDENCIES)
  /usr/local/share/cmake-3.9/Modules/FindBoost.cmake:1523 (_Boost_MISSING_DEPENDENCIES)
  /opt/eosio/lib/cmake/eosio/EosioTester.cmake:44 (find_package)
  /opt/eosio/lib/cmake/eosio/eosio-config.cmake:5 (include)
  CMakeLists.txt:7 (find_package)


-- Boost version: 1.67.0
-- Found the following Boost libraries:
--   date_time
--   filesystem
--   system
--   chrono
--   iostreams
--   unit_test_framework
-- Using eosio version 1.5.2
-- Configuring done
-- Generating done
-- Build files have been written to: /opt/eosio.contracts/build/tests
[ 31%] Performing build step for 'contracts_unit_tests'
Scanning dependencies of target unit_test
[ 16%] Building CXX object CMakeFiles/unit_test.dir/eosio.msig_tests.cpp.o
[ 33%] Building CXX object CMakeFiles/unit_test.dir/eosio.system_tests.cpp.o
[ 50%] Building CXX object CMakeFiles/unit_test.dir/eosio.token_tests.cpp.o
[ 66%] Building CXX object CMakeFiles/unit_test.dir/eosio.wrap_tests.cpp.o
[ 83%] Building CXX object CMakeFiles/unit_test.dir/main.cpp.o
[100%] Linking CXX executable unit_test
[100%] Built target unit_test
[ 36%] No install step for 'contracts_unit_tests'
[ 42%] No test step for 'contracts_unit_tests'
[ 47%] Completed 'contracts_unit_tests'
[ 47%] Built target contracts_unit_tests
Scanning dependencies of target eosio.bios.wasm
[ 52%] Building CXX object eosio.bios/CMakeFiles/eosio.bios.wasm.dir/src/eosio.bios.cpp.o
Warning, empty ricardian clause file
Warning, empty ricardian clause file
Warning, action <newaccount> does not have a ricardian contract
Warning, action <updateauth> does not have a ricardian contract
Warning, action <deleteauth> does not have a ricardian contract
Warning, action <linkauth> does not have a ricardian contract
Warning, action <unlinkauth> does not have a ricardian contract
Warning, action <canceldelay> does not have a ricardian contract
Warning, action <onerror> does not have a ricardian contract
Warning, action <setcode> does not have a ricardian contract
Warning, action <setpriv> does not have a ricardian contract
Warning, action <setalimits> does not have a ricardian contract
Warning, action <setglimits> does not have a ricardian contract
Warning, action <setprods> does not have a ricardian contract
Warning, action <setparams> does not have a ricardian contract
Warning, action <reqauth> does not have a ricardian contract
Warning, action <setabi> does not have a ricardian contract
[ 57%] Linking CXX executable eosio.bios.wasm

Improve UI

  • overall code review
  • clean up ui and code
  • fix everything in red in the screenshot
  • review scatter integration ( make sure it's latest version )

greetings-ui

Add instructions for configuring Scatter with the Testing Users

The init chain script creates several users for testing.
Please add instructions on how to configure Scatter with their keys.

EOSLOCAL_ACCOUNT_PRIVATE_OWNER_KEY="5J5t5MuUmMgNcrFWiXyeBZEsCfHvgYE7Lec4W2wCaV5SiSoEqQr"
EOSLOCAL_ACCOUNT_PUBLIC_OWNER_KEY="EOS6P62N6D14ShhUnM7taEQHLTMmS7ohCyfikwAi46U7AT6jmUHyM"

EOSLOCAL_ACCOUNT_PRIVATE_ACTIVE_KEY="5JhTPDSe9ugHomFnhMgAdzzE2HniuR8rG3SyzzqvQrgJNPC4685"
EOSLOCAL_ACCOUNT_PUBLIC_ACTIVE_KEY="EOS5X6m7mxcKRsKvHDyCVp1DE5YAy5dEsb5TwFqG4F2xRvRYAAdZx"

EOSLOCAL_USERA_ACCOUNT="eoslocalusra"
EOSLOCAL_USERA_PVTKEY="5K4MHQN7sPdEURaxzjCnbynUwkEKRJzs8zVUf24ofaFiZNK815J"
EOSLOCAL_USERA_PUBKEY="EOS5k6Jht1epqZ2mnRLFVDXDTosaTneR6xFhvenVLiFfz5Ue125dL"

EOSLOCAL_USERB_ACCOUNT="eoslocalusrb"
EOSLOCAL_USERB_PVTKEY="5JHCQDi7jsbnQnWdyxteRjT2DdNZHePiEG1DTaPQQDDP2X6aor6"
EOSLOCAL_USERB_PUBKEY="EOS6TVQ6EmphCWavUuYiZMmDNYMRgbb96wgqWDncjrkvFPcpokgdD"

EOSLOCAL_USERC_ACCOUNT="eoslocalusrc"
EOSLOCAL_USERC_PVTKEY="5JXCt633pzYaUysn7exDHeVXwhwMjX2L231b37CdsSb7y1uvDH7"
EOSLOCAL_USERC_PUBKEY="EOS7CB47VMLWp49QhajE3uTuHuf9qoSeR6scUHMKGCD6LXYufRUDc"

EOSLOCAL_USERD_ACCOUNT="eoslocalusrd"
EOSLOCAL_USERD_PVTKEY="5JdRgeRBriBDdxb3r76sLJaQmwGgXkMU8GReTAmy8xYppMSAAoZ"
EOSLOCAL_USERD_PUBKEY="EOS6Jv4RykLZQQopCBdBHSwaGoMyFxyaxFNXimqFPdEXNWqgWbG1a"

EOSLOCAL_USERE_ACCOUNT="eoslocalusre"
EOSLOCAL_USERE_PVTKEY="5Jdwjwto9wxy5ZNPnWSn965eb8ZtSrK1uRKUxhviLpr9gK79hmM"

see https://github.com/eoscostarica/eos-local/blob/master/services/eos-dev/scripts/0000_init-chain.sh

Use CircleCI

CircleCI supports open source projects and allocates substantial resources for both paid and free users without affecting queue times. You have the ability to choose the CPU and RAM you need regardless of your project type with various price plans to fit your team’s needs across Linux and iOS projects. Teams building on TravisCI have reported long build queues, inability to adjust resources, and resorting to utilizing local machines just to speed up builds.

Teams Gain Complete Control with Workflows .

Teams looking to scale and customize their development process can do so with CircleCI. By breaking jobs into functional pieces, teams can decide when and how they’d like to configure their jobs and orchestrate parts of the build. Customizing workflows allows teams to persist artifacts across job stages, filter by branches, and schedule approved jobs.

Increased Efficiency with Shared Control and Workspaces

Having control centralized at an org-level is a helpful way to share variables across projects. This frees teams from having to reconfigure environmental variables per project. Though Travis CI offers convenience variables, sharing environment variables across an org isn’t currently supported. CircleCI provides Contexts to secure and share environment variables, and Workspaces to persist data, or move it between jobs.

Premium Support (custom SLAs, success team)

Whether you’re new to CircleCI or continuing to adopt continuous integration and delivery, your team will get the resources it needs to be successful. When choosing a CI provider, it’s important to select one that will grow with your team. Additionally, all customers can access Live System Status Updates, Ticket-based Global Support, and Community-based Support via Discuss for free.

Mobile Testing

Document how to test mobile web & native apps on EOS Local

Error un Gulp setup

Failed to connect to nodeos at http://127.0.0.1:8888/; is nodeos running?

use cleos system newaccount and stake resource upon creation

During BIOS process on the EOS Producer node I'm trying to the setup node with EOS as symbol and create accounts with staked tokens.

For some reason I cannot get that work and I'm getting the following message.

 cleos -u http://eosiodev:8888 system newaccount --stake-net '1 EOS' --stake-cpu '1 EOS' --buy-ram '1 EOS' eoslocal eoslocalusra EOS5k6Jht1epqZ2mnRLFVDXDTosaTneR6xFhvenVLiFfz5Ue125dL EOS5k6Jht1epqZ2mnRLFVDXDTosaTneR6xFhvenVLiFfz5Ue125dL
error 2018-11-10T05:24:46.671 thread-0  main.cpp:3151                 main                 ] Failed with error: Assert Exception (10)
!action_type.empty(): Unknown action buyram in contract eosio

see https://github.com/eoscostarica/eos-local/blob/master/services/eos-producer/scripts/0000_init-chain.sh

read messages from the graphql endpoint

Update the client to read data from the graphql endpoint with a query similar to this one:

{
  allGreetings {
    edges {
      node {
        createdEosacc,
        greeting
      }
    }
  }
}

Private Key for EOSIO in docs

Hi. Going through the instructions in the readme I found that the eosio keys given here did not work

`Note: As the docker image were pulled from eoscostarica506, the eosio keys are:

Private key: 5JV5XER5ouVYfghE6AEgDeViqkH4VNAJaxwB6wVe4Mk2JHZywPQ
Public key: EOS5hyZZRePAFyKVTEReHLErXviH6chc3w84pQcwtHnsNJWCWj3Jp`

after digging around I inspected the docker image using docker desktop and found in the image history that the testnet_eosio_private_key is being set there.

so I used that key and was able to create an account.

I still am having another issue that is not relevant here but I don't know where to look for help.

Create Greetings Contract

We want to have a demo contract that allows people to store greetings on the blockchain.

The sample website will have a form and stream of greetings. #11

Include a Block Explorer

We want to have an open source block explorer running locally so that one can use it to verify transactions on a nice interface, not just command line.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.