RecapTimeSquad / db-fleet-okteto

Make your Postgres and Redis containers available through Okteto Cloud

DB Fleet in Okteto via Compose file

Need Redis and Postgres, but don't have money, especially your credits ran out in Railway?

Basic Deployment Docs/Usage

We recommend to duplicate this repository so you can keep updated with the upstream changes. If you have an copy of this repo, we recommend to use Git branches.

Tools Needed for Local Development

You probably don't need for these if you open this repo in Gitpod. To open, prefix gitpod.io/# to your repository URL, log in and volia. Scroll to Local Dev / Gitpod section for details.

• Node.js and Yarn (install with npm i -g yarn or pnpm add -g yarn; if you prefer to run yarn <script-name> instead of typing long lines of commands one-by-one)
• Bash (you should be also fine on WSL, but if you're not on Windows 10 or WSL isn't enabled you need Git Bash through Git for Windows)
• Okteto CLI
• kubectl, optional but recommended
• Docker (Docker Engine for Linux or DOcker Desktop for macOS and Windows 10) to build custom Gitpod workspace image, optional

For GitHub users

1. Go to this page and paste this GitHub repo URL in the old repository clone URL.
2. In the new repo details section, make sure to set the privacy to Private. Then pick the owner and repository name.
3. Hit Begin import. When its done, it'll refresh at will.
4. Skip to Post Repository Creation section below to complete the remaining tasks.

Post Repository Creation

1. Sign in to Okteto Cloud. If you rather use Okteto Enterprise, contact your sysadmin for details about your company's setup.
2. On the namespaces tab, click Deploy > From Git. If your repo is on GitHub, make sure to add the Okteto Cloud (or your instance's app) to your organization. When done, just find and select your repo.

• For GitLab/Bitbucket users, use the Git URL option in the form of https://<username of your bot account>:<PAT of your bot account with readonly access>/git.host/namespace/subgroup/repo.git

3. If you configured Redis through the config file (either with requirepass key or using the external ACL file) and followed the instructions in the redis/README.md file, then leave DBFLEET_REDIS_PASSWORD (or what the var you set for the default Redis user) to blank. Otherwise fill it up.
4. For Postgres, set DBFLEET_POSTGRES_PASSWORD to any value. We recommend strong password for this one,and if you're in the terminal, jsut use the output from openssl rand -hex 32.
5. Hit Deploy and cross your fingers.
6. For continuous deplyments of changes, run ./scripts/prepare-autodeploys.sh (for Yarn users, run yarn ci:setup) and follow prompts.

Local Dev / Gitpod

1. Clone the repo with Git. (Make sure you followed GitHub/GitLab/Bitbucket sections above first!) and change working directory to your local copy. For Gitpod users, wait until the custom workspace image is successfully built and you're redirected to your new workspace in a browser tab.
2. Login with yarn okteto:login. If you see No browser could be found error, try again with yarn okteto:login-headless and follow instructins.

How to connect?

When connecting to your instance through their HTTPS endpoints in Okteto, use port 443 as you'll experience Connection timed out errors.

Why Compose file? You should use f**king Kubernetes instead.

Yeah, we know that, but Okteto supports Docker Compose files, so we can free up our headaches on managing Kubernetes resource files on our own and instead do Docker image builds instead.