wasmerio / docs.wasmer.io Goto Github PK

The path doesn't exist - https://docs.wasmer.io/get-started

Issue Location : https://github.com/wasmerio/docs.wasmer.io/blob/main/pages/edge/index.mdx#L115

Fix : I think it must be - https://docs.wasmer.io/edge/get-started

Specify in quickstart guide for edge to update the value public attribute to some other folder such as build or release or app etc. So that public assets such as favicon.ico, og.png,etc. that should remain inside the public folder should not conflict with the wasmer.toml.

Following the tutorial for markdown-editor-improved I've noticed that using the version published on the registry

import { init, Wasmer, Command } from "@wasmer/sdk";

async function initialize() {
  await init();
  return await Wasmer.fromRegistry("wasmer-examples/markdown-renderer");
}

either wasmer-examples/markdown-renderer or the one I've published @kandros/markdown-renderer the markdown transformation doesn't work (video below)

While using the locally imported version it does work!

⚠️⚠️ NB: when running the package using wasmer CLI it's working as intended!

Can you explain to me how can I contribute to the project by adding an AMD64 build release for FreeBSD?

when i input “wasmer run python/python -- -c "print(1+1)"”
it fedback：
Exception ignored error evaluating path:
Traceback (most recent call last):
File "", line 297, in
OSError: failed to make path absolute
Fatal Python error: error evaluating path
Python runtime state: core initialized

Current thread 0x00080014 (most recent call first):

Edge will only relay packets on port 80 for now which are forwarded through port 443 but this needs to be mentioned in wasix axum example in the edge documentation.

Mention about things like:

• Dev server starter port
• Default starter port

@theduke can you give some more context here.

Automatically deploy new versions to Wasmer Deploy

Following the how to use packages guide:

it states:

wasmer run syrusakbary/cowsay hello wasmer

But this does not provide the documented output

❯ wasmer run syrusakbary/cowsay hello wasmer
error: The `[email protected]` package doesn't have a default entrypoint, but has multiple available commands:
│   1: You can run any of those by using the --command-name=COMMAND flag
│   2: `cowsay`, `cowthink`
╰─▶ 3:   -> wasmer run [email protected] --command-name=cowsay

The docs need updating to this:

❯ wasmer run syrusakbary/cowsay --command-name=cowsay hello wasmer
 ______________
< hello wasmer >
 --------------
        \   ^__^
         \  (oo)\_______
            (__)\       )\/\
               ||----w |
                ||     ||

device: MacBook Air (M1, 2020)

let port = std::env::var("PORT").unwrap_or("3000".to_string()); works

error was:

Listening on http://127.0.0.1:80
thread 'main' panicked at 'error binding to 127.0.0.1:80: error creating server listener: Operation not permitted (os error 63)', /Users/johndoe/.cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-0.14.27/src/server/server.rs:79:13```

Update the login through browser when 4.1 releases in edge docs for quickstart guides.

Issue opened here

I followed https://docs.wasmer.io/wasmer-pack/tutorial/01-hello-world#publishing-to-wapm

In the stage Publish To WAPM, cargo wapm --dry-run failed with the following error.

cargo wapm --dry-run

2024-05-01T07:54:06.901658Z  INFO publish: cargo_wapm::publish: Getting ready to publish dry_run=true pkg="hello-world"
Error: Unable to publish "hello-world"

Caused by:
    0: Unable to deserialize the [metadata] table
    1: expected one of "wit-bindgen" or "wai-version" to be provided, but not both

[package]
name = "hello-world"
version = "0.1.0"
edition = "2021"
description = "hello-world"
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[package.metadata.wapm]
namespace = "huakunshen"
abi = "none"
bindings = { wai-bindgen = "0.1.0", exports = "src/hello-world.wai" }

[dependencies]
wai-bindgen-rust = "0.2.3"


[lib]
crate-type = ["cdylib", "rlib"]

Update Wasmer.toml configuration to accommodate the following fields in [command.annotations.wasi]:

• main-args
• env

Both of these are now used in Python example too.

1. Main args are the set of commands passed to the wasi runner
2. Env are the set of environment variables passed to the wasi runner

Document for app create for http and browser-shell in the edge-cli:

https://github.com/wasmerio/edge/issues/749

Make Documentation pages for the following:

• Logging
• Metering
• SSH
• Analytics
• Debugging (low priority) - @john-sharratt 's working on it

https://docs.wasmer.io/ecosystem/wapm/cli
https://docs.wasmer.io/ecosystem/wapm/getting-started

Mention about the introduction of the commands:

• wasmer app info

Mention the changed behaviour of wasmer app get that it will work by automatically detecting the app.yaml in your directory.

Hi,

I'm trying to test boot time for wasm runtimes using a noop wasm file compiled from rust:

fn main() {}

When I excute wasmer run noop.wasm, it takes much more time than other runtimes (< 50ms).

Here's the output of time wasmer run noop.wasm -q (I use -q option to avoid printing time):

real    0m0.319s
user    0m3.088s
sys     0m0.314s

Did I take wrong method to measure boot performance of the runtime?
Do I need more command options to optimize execute time for this simple wasm file?
Or how can I measure boot time for this runtime?

Thanks for your answer : )

Add Wasmer Edge CI for the docs.

Add FAQ section for most questions asked on Discord or from users.

• Overview
  Hints:
  • only Webassembly
  • stateless first: spawned and scaled on demand, most apps should be stateless
  • global edge network with automatic scaling, load balancing , ...
  • Based on wasmer packagesDep
• optional: Why Deploy? (Benefits)
• Usage
  Notes:
  Manage via CLI or web UI.
  • CLI
    • wasmer deploy
    • wasmer app init [static-site]
    • wasmer app [get,list]
    • wasmer app logs
  • Web UI
• Tutorials
  • Static site
  • WASIX: Axum
  • WCGI: Rust
  • Introspection: Generating and showing logs
  • Optional: WCGI with Python
  • Optional: WASIX Axum + Leptos
• FAQ
• Architecture
  • high level overview (global edge network, ultra scalable, ...)
  • (future): Private encrypted network overlay (dnet)
  • (future): Persistent volumes and persistent workloads