Migrations are a way to make database changes or updates, like creating or dropping tables, as well as updating a table with new columns with constraints via generated scripts. We can build these scripts via the command line using knex command line tool.
To learn more about migrations, check out this article on the different types of database migrations!
| /* Create a database in Athena */ | |
| CREATE DATABASE s3_AccessLogsDB; | |
| /* | |
| Create a table within the Athena database | |
| Replace s3://MY_S3_BUCKET/ with your S3 bucket | |
| which has the access logs you want to query | |
| */ | |
| CREATE EXTERNAL TABLE IF NOT EXISTS s3_AccessLogs.Accesslogs( | |
| BucketOwner string, |
FINALLY no need for tricks!
bonus tip: for more darkness > https://darkreader.org/
| #!/bin/sh | |
| set -e | |
| HOST=localhost | |
| DB=test-entd-products | |
| COL=asimproducts | |
| S3PATH="s3://mongodb-backups-test1-entd/$DB/$COL/" | |
| S3BACKUP=$S3PATH`date +"%Y%m%d_%H%M%S"`.dump.gz | |
| S3LATEST=$S3PATH"latest".dump.gz | |
| /usr/bin/aws s3 mb $S3PATH |
Permalink: git.io/vps
| Provider | Type | RAM | Cores | Storage | Transfer | Network | Price |
|---|
| #!/bin/bash | |
| # Usage: ./init.sh once to initialize remote storage for this environment. | |
| # Subsequent tf actions in this environment don't require re-initialization, | |
| # unless you have completely cleared your .terraform cache. | |
| # | |
| # terraform plan -var-file=./production.tfvars | |
| # terraform apply -var-file=./production.tfvars | |
| tf_env="production" |
Inspired by jubalm's version
| daemon off; | |
| error_log /dev/stderr warn; | |
| worker_processes 4; | |
| events { | |
| worker_connections 1024; | |
| multi_accept on; | |
| } |
| docker exec -it container-name redis-cli FLUSHALL |
