wasmerio/docs.wasmer.io

The Wasmer Docs Website (website deployed using Wasmer Edge)

docs.wasmer.io's Issues

Chore: Update the login methods in quickstart guides

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

Error in "How to use packages" on https://wasmer.io/

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 |
                ||     ||

Mention that edge deployment examples only work on Wasmer 4.1

Document: app create for http and browser-shell

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

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

README: build wasmer from source link is broken

Issue opened here

Deploy Docs - Metering, Logging, Analytics and SSH

Make Documentation pages for the following:

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

Automatically deploy new versions to Wasmer Deploy

Automatically deploy new versions to Wasmer Deploy

Update: Runtime Configuration

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

Create tutorial and documentation for deploying Javascript apps

Mention new commands and behavioural changes in `wasmer app get`

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.

Mention to update public attribute value in wasmer.toml

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.

Package Manifest: Document how to use dependency modules in commands

Add an FAQs section for Edge

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

Example Binary panics with port 80

device: MacBook Air (M1, 2020)

docs.wasmer.io/pages/edge/quickstart/http-server.mdx

Line 91 in 460dcf2

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

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```

Invalid resource path : /edge - Getting started Guide

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

Add release for FreeBSD

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

Why `wasmer run` takes seconds to execute

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 : )

CI Setup for docs

Add Wasmer Edge CI for the docs.

Feedback for “Get Started with the Wasmer Runtime”

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):

Deploy Documentation

• 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

Mention about default ports in wasix-axum example

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.

Broken links

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