app-engine-cloud-run-
node-pg-migrate
Our great sponsors
app-engine-cloud-run- | node-pg-migrate | |
---|---|---|
1 | 4 | |
- | 1,229 | |
- | 1.7% | |
- | 9.4 | |
- | 4 days ago | |
TypeScript | ||
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
app-engine-cloud-run-
-
The Architecture of a One-Man SaaS
If you haven't checked out App Engine in a while, you really should. Especially check out the App Engine "Flexible" editions, which make it really easy to run on App Engine withOUT getting locked in.
I run a NodeJS GraphQL server in App Engine Flexible, and it is basically just like running it in a Docker container. It's also pretty trivial to run in Google Cloud Run if I so desired, there is even a tool to assist: https://github.com/GoogleCloudPlatform/app-engine-cloud-run-...
node-pg-migrate
-
Fully featured Repository Pattern with Typescript and native PostgreSQL driver
Why PG? For the clarity of the article to a large circle of developers, the entire explanation will be built by PostgreSQL and PG package. And in a real project, the database schema will change over time, and in order to be able to perform migrations, we will use Node PG migrate.
-
New to PostgreSQL - Best way to use it?
b) How you will manage schema migrations: every time you change tables, columns, foreign keys, every time you create or modify stored procedures, and so on, you need to do this through a migration. Here I'm at loss to recommend anything specific, but if you went with Prisma, I would read their docs and use whatever they are recommending you (if they actually recommend something). If you want something more neutral but still in the node ecosystem, node-pg-migrate might be the winner here? I'm not sure.
-
Postgres: What is the development process?
You’ll probably want something like this too: https://github.com/salsita/node-pg-migrate
-
The Architecture of a One-Man SaaS
You can use any normal DB migration tool. For k8s, I put the app's readiness probe to false, run the migrations and then toggle the probe back to true.
Here are some migration libraries:
Go - https://github.com/golang-migrate/migrate
Node - https://github.com/salsita/node-pg-migrate
What are some alternatives?
LetsShip - Let's learn devops by shipping a final product in .NET 5
sql-lint - An SQL linter
realworld - "The mother of all demo apps" — Exemplary fullstack Medium.com clone powered by React, Angular, Node, Django, and many more
graphjin - GraphJin - Build NodeJS / GO APIs in 5 minutes not weeks
prawn-stack - A pageview counter using the AWS free tier, Postgres, Node and React
logpaste - A simple web service for storing text log files
diagrams - :art: Diagram as Code for prototyping cloud system architectures
migrate-from-app-engine-to-cloud-run - Helper library and webpage to migrate from App Engine to Cloud Run
flan - A tasty tool that lets you save, load and share postgres snapshots with ease
migrate - Database migrations. CLI and Golang library.