mycelia

Open Source Application Stack & PaaS

Installation

cargo run build

IMPORTANT: cargo build will fail because we have to use cargo-xtask to build the ./components/ folder before building the project. Reason: Cargo's build.rs is not supported for workspaces

CLI

Info

cargo run

Start Development Server

cargo run start

Stop Development Server

cargo run stop

Deploy

cargo run deploy --component="your_component_name"

Development Server

RUST_LOG=info cargo run --package development_server

Logging

We use env_logger for logging. Please see their documentation for more information on setting custom log levels, filtering, and more.

Default CLI log level is info.

Basic example usage:

RUST_LOG=error cargo run start
RUST_LOG=warn cargo run start
RUST_LOG=debug cargo run start
RUST_LOG=info cargo run start # default
RUST_LOG=trace cargo run start

Community & Contributing & Help

Come join our Discord

wasi_snapshot_preview1.reactor.wasm

search_tags: import not found, guest wasm won't build, wasi, wasi build error

Current version in repo is taken from the v12.0.1 Release

More information on "what the heck" this is can be found here. In the lliekly event that's not enough context, the repo previously hosting this file can be found here: here.

Hazel: My best explanation is.. When compiling the wasm target to wasm32-wasi the guest program expects to find a bunch wasi resources in the table(?). The build script contains an --adapt argument which takes the wasi_snapshot_preview1.reactor.wasm and injects the correct links into the guest code. I think that is what this is expressing. Here is the generated output from a working example

Resources

1. The lifetime error you're seeing means you should think about using async_trait. Notice the name of the lifetime async_trait ;)
2. Everything you wanted to know about Resources

Questions

1. Whats the lifetime behavior of resources??

/// Todo..

• Lock more dep versions in workspace.deps

• Build FunctionComponentService

  • a thing that takes invocation requests and produces responses wrapped in a tower service

• ^ take above into development_server :D