Important
These benchmark results are outdated.
Check out our blog post for the latest benchmark results.
- c5.xlarge AWS instance: 4 CPUs, 8 GB RAM
| // db/schema/auth.ts | |
| import { | |
| int, | |
| timestamp, | |
| mysqlTable, | |
| primaryKey, | |
| varchar, | |
| text | |
| } from "drizzle-orm/mysql-core" | |
| import type { AdapterAccount } from "@auth/core/adapters" |
Important
These benchmark results are outdated.
Check out our blog post for the latest benchmark results.
Este es un instructivo para un tutorial en Youtube https://youtu.be/pliGG1M87W8
Create a folder to store the databases :
mkdir -p /usr/share/GeoIP
Download Country IP database
wget http://geolite.maxmind.com/download/geoip/database/GeoLiteCountry/GeoIP.dat.gz
gunzip GeoIP.dat.gz
Set which editor git should use.
This is the program that will open during a commit with no -m flag, a merge, a rebase, etc...
Select from any installed editor. Examples:
emacsvi or vim| // This gist explains how to setup scalable Parse LiveQuery server on Heroku | |
| // Because there is one and only 'web' process on Heroku, it will divide into two Heroku apps: Main and LiveQuery. | |
| // A: Main app - All features except for LiveQuery server | |
| // Step A1. Setup a Parse app on Heroku | |
| // Step A2. Add a Heroku Redis (free plan is enough for testing) | |
| // Step A3. Configure Parse app, add redisURL for liveQuery | |
| var api = new ParseServer({ | |
| ... | |
| liveQuery: { |
This gist is based on the information available at golang/dep, only slightly more terse and annotated with a few notes and links primarily for my own personal benefit. It's public in case this information is helpful to anyone else as well.
I initially advocated Glide for my team and then, more recently, vndr. I've also taken the approach of exerting direct control over what goes into vendor/ in my Dockerfiles, and also work from
isolated GOPATH environments on my system per project to ensure that dependencies are explicitly found under vendor/.
At the end of the day, vendoring (and committing vendor/) is about being in control of your dependencies and being able to achieve reproducible builds. While you can achieve this manually, things that are nice to have in a vendoring tool include:
Kong, Traefik, Caddy, Linkerd, Fabio, Vulcand, and Netflix Zuul seem to be the most common in microservice proxy/gateway solutions. Kubernetes Ingress is often a simple Ngnix, which is difficult to separate the popularity from other things.
This is just a picture of this link from March 2, 2019
Originally, I had included some other solution
| // Import the core angular services. | |
| import { Component } from "@angular/core"; | |
| @Component({ | |
| selector: "my-app", | |
| styleUrls: [ "./app.component.css" ], | |
| template: | |
| ` | |
| <p class="actions"> | |
| <strong>Values:</strong> |