You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* emcc using custom cache directory for permissions reasons
* ignoring a build artifact
* Dockerized!
* little addition to readme
* why is this in the repo??
* keep track of the validator compile product
* this cache is temporary
* json cleanup and no longer serving from devbox
* now passing build artifacts to new image for serving
* no longer using cache directory in repo
* updated to match new docker build process
* trimming down the devbox configuration
* Dockerfile with multiple targets for flexibility
* setting emscripten cache to writeable local directory
- emscripten and nix don't play nice together; this seems to be a/the common workaround NixOS/nixpkgs#139943
* only installing rust stuff if necessary
* simpler checks
---------
Co-authored-by: Shane Liesegang <[email protected]>
Copy file name to clipboardExpand all lines: README.md
+38-3
Original file line number
Diff line number
Diff line change
@@ -14,12 +14,47 @@ The [documentation can also be useful](./docs/), or maybe just [the development
14
14
15
15
It's a big ole monorepo. Sorry about that; it's what happens when a proof-of-concept just grows organically. I presumptively registered a [wasmbots org on GitHub](https://github.com/wasmbots) just in case this becomes A Thingβ’ in which case I'll split things out more productively.
16
16
17
-
Prereqs on macOS; modify this appropriately if you're using something else:
17
+
18
+
### Devbox
19
+
You can always build and run with [devbox](https://www.jetify.com/devbox). ([Installation instructions are here.](https://www.jetify.com/docs/devbox/installing_devbox/))
20
+
21
+
Run `devbox shell` to be in a usable environment where you can run
22
+
23
+
24
+
### Docker
25
+
The [Dockerfile](./Dockerfile) just pipes everything through devbox, but makes it a little more turnkey, especially if you're already a Docker user.
26
+
27
+
```sh
28
+
# produces a container with a built frontend,
29
+
# including example bots, served with Caddy
30
+
docker build -t wasmbots .
31
+
32
+
# to actually get it serving:
33
+
docker run -d -p 8080:80 wasmbots
34
+
# Then look for it in your favorite browser at:
35
+
# `http://localhost:8080`
36
+
# (change out the port number to whatever you want)
18
37
```
19
-
brew install deno wabt rust zig emscripten node go tinygo-org/tools/tinygo
38
+
39
+
```sh
40
+
# this will drop you into a shell within the container
41
+
# where all the tools are installed and paths are set
42
+
# and everything.
43
+
docker build --target dev -t wasmbots-dev .
44
+
docker run -it -v $PWD:/code wasmbots-dev
45
+
```
46
+
47
+
48
+
### Manual Installation
49
+
If you don't want to install a whole other package manager, here's what I (used to) use to get up and running with [Homebrew](https://brew.sh/) on macOS. Modify appropriately if you're using something else.
50
+
51
+
52
+
```sh
53
+
brew install deno node wabt emscripten rust zig go tinygo-org/tools/tinygo
20
54
```
21
55
22
-
At the moment you can verify everything is working as expected by running:
56
+
### Simple Checks
57
+
Regardless of how you get your dev environment running, you can verify everything is working as expected by running:
0 commit comments