Explore >> Select a destination
|
You are here 
|
github.com | ||
| | | | |
amanhimself.dev
|
|
| | | | | ||
| | | | |
jbrandhorst.com
|
|
| | | | | Putting it all together As we touched upon earlier, we generate a package from the generated JS (meta, right?), which can be served from the server. We'll create a new file, main.go, in which we can spin up a server, serve the frontend and the gRPC backend. Much of the logic in this file is inspired by the excellent blog post put together by Brandon Philips over at CoreOS. We're using his elegant solution to serve both the HTTP API and the gRPC API on the same port. | |
| | | | |
ukiahsmith.com
|
|
| | | | | Often times we need to unmarshal upstream data with unique constraints. Such as custom data types, or custom parsing of specific formats. Using the standard library could be impractical, and handling long structs manually can be tedious; however there is an alternative. | |
| | | | |
www.johndcook.com
|
|
| | | Example of a cryptographically secure random number generator with Python sample code | ||
