Static deployed URL for packages
Opened this issue · 7 comments
Hi,
Thank you for your awesome Wasm deploying tool!
As https://jsgo.io/github.com/hajimehoshi/ebiten/examples/2048 can be accessed, it would be much nicer if I could access this as a static URL like https://wasm.jsgo.io/github.com/hajimehoshi/ebiten/examples/2048 instead of https://jsgo.io/4289f8e26bd753770d6096d6934257379144996c (I just deployed now). This would enable me to show Wasm examples in my website in much easier way.
I would like this too... but how would you stop someone from deploying something else over your URL? The jsgo compiler actually pulls from GitHub so it only ever deploys to a human readable url when it knows the source. When you use the deploy function on play.jsgo.io it uses a hash for the url just like wasmgo because the code could have been changed...
how would you stop someone from deploying something else over your URL?
I cannot? However, the current GopherJS jsgo.io does the same way, right?
Ah, wasmgo works with the local repository, that is the difference. So would it be possible to deploy the remote repository by specifying the package name samely as GopherJS jsgo.io?
The problem is that jsgo does the compilation server side so everything is trusted. wasmgo compiles locally so you can’t trust the client...
I see. Would it be possible to compile packages on server side for Wasm? Probably this would be a different tool from wasmgo though.
Would love to but it doesn’t really fit into the jsgo architecture because you have to exec the go command. It would be an extensive rewite of the system to get that working.
In the first place, I was wondering why you didn't use the go command line tool.