https://github.com/creoone/edgeintracomm

AssemblyScript boilerplate for Docker+Wasm
https://github.com/creoone/edgeintracomm

assemblyscript docker wasi wasm

Last synced: 9 days ago
JSON representation

AssemblyScript boilerplate for Docker+Wasm

• Host: GitHub
• URL: https://github.com/creoone/edgeintracomm
• Owner: CreoOne
• License: mit
• Created: 2022-11-06T20:51:17.000Z (about 2 years ago)
• Default Branch: master
• Last Pushed: 2022-11-06T21:22:56.000Z (about 2 years ago)
• Last Synced: 2024-07-29T16:58:17.838Z (5 months ago)
• Topics: assemblyscript, docker, wasi, wasm
• Language: WebAssembly
• Homepage:
• Size: 23.4 KB
• Stars: 2
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# EdgeIntraComm

This is [AssemblyScript](https://github.com/AssemblyScript/assemblyscript) boilerplate that works in [Docker+Wasm](https://docs.docker.com/desktop/wasm/).

## Advantages

1. Compiles straight into wasm.

2. **Doesn't require any runtime** inside docker.

3. Generated docker image weights **3.33kB**.

## Running

1. Clone repo.

2. Run/look into [run.ps1](./run.ps1).

## Dependencies

- [Docker+Wasm](https://docs.docker.com/desktop/wasm/) (at the moment of making this repo just released as beta).

- [optional] [PowerShell](https://learn.microsoft.com/en-us/powershell/) for execution of run script.

## What next?

1. I'd like to introduce HTTP server inside, so that this boilerplate is a microservice ready to be filled with domain logic, but there are [some issues](https://github.com/AssemblyScript/wasi-shim#considerations) with [WASI](https://wasi.dev/) direction in AS. Whatever i support any side of the conflict, doesn't matter, in the current state of the WASI in AS it's too much hustle to implement HTTP server so i'm waiting until situation is resolved or alternatives are implemented.

2. Some kind of tests boilerplate can be added. You are welcome to do so.