diff options
| -rw-r--r-- | README.md | 22 |
1 files changed, 10 insertions, 12 deletions
@@ -1,8 +1,6 @@ # submelon.dev -## Deploying - -### Using Docker +## Deploying Using Docker The Dockerfile works via a fresh clone, no pre-build or npm install is needed. It can be tagged as follows: @@ -13,9 +11,11 @@ docker build -t registry.digitalocean.com/submelon-tech/submelon.tech:1.0.0 . Or if using M1/ARM, ``` -docker buildx build --platform linux/amd64 -t registry.digitalocean.com/submelon-tech/submelon.tech:1.0.0 . +docker buildx build --platform linux/amd64 --push -t registry.digitalocean.com/submelon-tech/submelon.tech:1.0.0 . ``` +(Reference authenticating to use DigitalOcean's Container Registry below.) + If the build fails in error as a result of the image, the base gatsby images can be rebuilt. (The gatsby images as exist on Dockerhub do not work.) To rebuild those images, run the following commands: ``` @@ -38,7 +38,7 @@ docker buildx build --platform linux/amd64 -t gatsbyjs/gatsby:latest -f Dockerfi And then attempt rebuild of the submelon.tech image. -#### Authenticating with DO +### Authenticating with DO Install `doctl`. Create an access token via DO's web interface to authenticate with the registry, and connect docker: @@ -47,19 +47,17 @@ doctl auth init doctl registry login ``` -Then push the image to the registry: +### DO K8s Deployment -``` -docker push registry.digitalocean.com/submelon-tech/submelon.tect:1.0.0 -``` - -#### DO K8s Deployment +To access the DO k8s cluster, save the config. It will automatically switch to use this context: ``` doctl k8s cluster cfg save k8s-1-13-1-do-2-nyc1-1547908941746 +``` -## +Then to switch to use this context in the future: +``` kubectl config use-context do-nyc1-k8s-1-13-1-do-2-nyc1-1547908941746 ``` |