Create the following files in the .vscode
folder of your repo
{
"import": ["./cspell-node.config.cjs"]
}
#!/bin/bash | |
############################################################################################################### | |
# UPDATE: # | |
# This has been merged to a more complete example: # | |
# https://github.com/jaketf/ci-cd-for-data-processing-workflow/blob/master/helpers/run_relevant_cloudbuilds.sh# | |
############################################################################################################### | |
FROM ruby:2.7.1-slim AS base | |
LABEL maintainer="Yann Defretin <[email protected]" | |
# Common dependencies | |
RUN apt-get update -qq \ | |
&& DEBIAN_FRONTEND=noninteractive apt-get install -yq \ | |
--no-install-recommends \ | |
build-essential=12.6 \ | |
gnupg2=2.2.12-1+deb10u1 \ |
Cloud Build is a product of GCP (Google Cloud Platform) used to build software quickly across all languages.
Function:
This guide was written because I don't particularly enjoy deploying Phoenix (or Elixir for that matter) applications. It's not easy. Primarily, I don't have a lot of money to spend on a nice, fancy VPS so compiling my Phoenix apps on my VPS often isn't an option. For that, we have Distillery releases. However, that requires me to either have a separate server for staging to use as a build server, or to keep a particular version of Erlang installed on my VPS, neither of which sound like great options to me and they all have the possibilities of version mismatches with ERTS. In addition to all this, theres a whole lot of configuration which needs to be done to setup a Phoenix app for deployment, and it's hard to remember.
For that reason, I wanted to use Docker so that all of my deployments would be automated and reproducable. In addition, Docker would allow me to have reproducable builds for my releases. I could build my releases on any machine that I wanted in a contai
Generally, you will add a git remote for your Heroku app during the Heroku app creation process, i.e. heroku create
. However, if you are working on an existing app and want to add git remotes to enable manual deploys, the following commands may be useful.
Note that on Heroku, you must always use master
as the destination branch on the remote. If you want to deploy a different branch, you can use the syntax local_branch:destination_branch
seen below (in this example, we push the local staging
branch to the master
branch on heroku.
$ git remote add staging https://git.heroku.com/staging-app.git
#!/bin/bash | |
#encrypt files with aes-256-cbc cipher using openssl | |
#install: | |
# sudo wget -O /usr/bin/enc https://gist.github.com/krisf/5391210/raw/4a105a6b8f98f39e9e74a1dd2a78ef6f631acdb1/enc | |
# sudo chmod +x /usr/bin/enc | |
# enc --help | |
#encrypt files | |
if [ $1 == "-e" ]; | |
then |
1. Install Zsh with Homebrew | |
brew install zsh | |
2. Add "/usr/local/bin/zsh" to "/etc/shells" file | |
sudo vim /etc/shells | |
3. Change to default login shell | |
chsh -s /usr/local/bin/zsh $USER | |
4. Make sure new version of Zsh is in active |