No description
bacaa0ca8a
I'm attempting to setup my blog using the following: - Google Cloud Run: I whitelist a docker image that packages my application and then Google runs it "statelessly" (i.e. without persistence). The stateless part should be fine for the time being. - Nix: Using `<nixpkgs>.dockerTools.buildLayeredImage` to output docker images from Nix expressions. - Docker: Upload the output image from the Nix expressions and upload it to Google Container Registry from which it can be run from Google Cloud Run. Some helpful commands: ```shell > sudo gcloud auth login > nix-build ./docker/cloud_run.nix > sudo docker image import ./result > sudo docker tag <name> gcr.io/<google-cloud-project-id>/<name>:<tag> > sudo docker push gcr.io/<google-cloud-project-id>/<name>:<tag> ``` I'm unsure if Google Cloud Run is my desired end goal, but it may help me publish a blog faster than setting up a Kubernetes cluster, which is what I'd ultimately like to do. Cloud Run should be cheaper financially and time-wise. |
||
---|---|---|
advent-of-code | ||
blog | ||
clojure | ||
crack_the_coding_interview | ||
data_structures_and_algorithms | ||
deepmind | ||
docker | ||
haskell-file | ||
java | ||
lisp | ||
third_party/lisp | ||
.envrc | ||
.gitignore | ||
default.nix | ||
README.md |
Universe
This is my mono-repo. Having a personal mono-repo is a new idea for me, so at the time of this writing, the state of this repository is fledgling.
I'm attempting to amass a collection of functions across a variety of languages while minimizing the costs of sharing the code across a projects. Stay tuned for more updates as my definition of the mono-repo becomes more clear, my opinions evolve, and my preferences change.