postgrest-rs VS markdown-here

Supabase: Build modern apps with a scalable backend.

In the db.ts file we are going to create our database connection, in my case I will occupy (Supabase)[https://supabase.io/], but you can occupy any database you want.

Head over to Supabase and create a new project. Once the project is set up, navigate to the SQL section and create a new table for your todos:

I integrate supabase to my side project. Use the crate postgrest-rs.

Supabase

Since I went out of the dynamic properties, now it doesn’t automatically store my file in a cloud storage provider (Supabase) anymore. So I need to do it manually:

Authentication & Database: Supabase

- they use more cost efficient hardware (e.g. databases running on 3rd gen SSD disks) to run your workloads.

Since these companies are renting raw hardware, on which they run your workloads (and are not using cloud-provider-native services, such as RDS), they need to hire experienced operators able to run and manage those workloads in production. This (for obvious reasons) is not exactly easy, and requires a lot of experienced talent with operational experience.

Hiring those people is very hard, as these experts are not usually available on the market.

This leaves us with with the obvious problem:

Are the operators of the given PaaS provider really able to run your production workloads? Are they able to to withstand all the issues that may arise?

Don't get me wrong. There definitely are companies (the most succesful) able to hire very capable talent (such as https://supabase.io), but this definitely isn't the case for all of those PaaS providers.

And I believe that these companies will need to increase their prices (and be less lucrative for their customers) or changes their business model.

This is something that we at stacktape.com built our business case on. We took a different path. We just wanted to make the existing (AWS) offerings 2 orders of magnitue easier to use, so that any developer (withou Cloud or DevOps experience) can use them productively.

We're not running your workloads for you. We are just making AWS services (run by experienced operators) significantly easier to consume (97% less difficult, so that any developer can do the job). For that, we're charging 30%->20% of the AWS infrastructure costs managed by us premium. This also means that you are not restricted to our platform, but can easily extend your infrastructure by any AWS service (using AWS CloufFormation or AWS CDK).

AWS offers areasonably generous free tier, and Stacktape won't charge you for any resources withing the free tier.

We're launching our v2 soon (~1-2 weeks), and if the offering we have sounds interesting, we'll be very happy to hear your thoughts.

You can there is a client library for Postgres for rust. There aren't all the other clients, but perhaps you can help the community build them.

Markdown Cheat Sheet: Markdown syntax guide for creating rich text formatting.

# Heading 1 ## Heading 2 ### Heading 3 Emphasis, aka italics, with *asterisks* or _underscores_. Strong emphasis, aka bold, with **asterisks** or __underscores__. Combined emphasis with **asterisks and _underscores_**. 1. First ordered list item 2. Another item ⋅⋅* Unordered sub-list. 1. Actual numbers don't matter, just that it's a number ⋅⋅1. Ordered sub-list 4. And another item. [I'm an inline-style link](https://www.google.com) [I'm an inline-style link with title](https://www.google.com "Google's Homepage") 

It's definitely a workaround, but I use a Chrome extension to work around this a bit. I use "Markdown Here" to add a "turn Markdown text to formatted text" button to my Chrome bar:

https://markdown-here.com/

And then I use it on plain Markdown text in a GMail compose window. The rich formatted output it produces can then be pasted into a Google Doc, and it comes out really nicely, including support for headers, sub-headers, links, code blocks, and the rest. The main issue is that this is a one-way process, but so long as you keep the .md source somewhere else, lets you share a richly-formatted doc with others for final commenting/editing/etc.

Here is a reference guide for the basic syntax of Markdown. Experiment and enjoy!

Means I made changes to the post formatting using Markdown https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet

markdown syntax Can be used to format your read me.

Proper formatting is key to ensure that your post is readable, helpful, and polished. Our post editor uses Markdown and Jekyll Front Matter to format posts.

You can also use more complex Markdown features like lists and tables. Check out the [Markdown Cheatsheet](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet) from Adam Pritchard for more information. ### Other JSDoc tags 📚 There are a few other JSDoc tags that you may find useful: - `@function` or `@func`: Documents a function or method. - `@class`: Documents a class constructor. - `@constructor`: Indicates that a function is a constructor for a class. - `@extends` or `@augments`: Indicates that a class or type extends another class or type. - `@implements`: Indicates that a class or type implements an interface. - `@namespace`: Groups related items, such as functions, classes, or types, under a common namespace. - `@memberof`: Specifies that an item belongs to a class, namespace, or module. - `@ignore`: Tells JSDoc to exclude an item from the generated documentation. - `@deprecated`: Marks a function, class, or property as deprecated, indicating it should no longer be used. - `@since`: Documents the version when an item was introduced. And many more. You can find a full list of JSDoc tags [here](https://jsdoc.app/). Ok ok, enough of the theory. Let's see how we can use JSDoc in practice.  ## Using JSDoc in practice 🏄‍♂️ There are a few challenges when starting to use JSDoc in your project. So this section will focus on these challenges and how you can overcome them. ### How to get the most out of JSDoc In this post I'm going to stick with VSCode. If you're using another editor, you can still follow along, but you might have to look up how to configure things in your editor. VSCode has built-in support for JSDoc. This means that you can get a lot of the JSDoc benefits without having to install any additional extensions. But there are a few things that you can do to get even more out of JSDoc. Enabling the checkJs option in your `jsconfig.json` file will make the editor display errors for type mismatches, even in JavaScript files. Place it in the root of your project or in the folder where you want to enable type checking. This file can look like this: ```json { "compilerOptions": { "checkJs": true, } }

Reddit uses Markdown, it's a pretty ubiquitous markup for formatting text online. You'll find it's used in a lot of places. https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet