flyctl VS lit

Fly.io is a platform that enables developers to deploy and run their applications close to their users. It leverages a global network of servers to provide low-latency, high-performance hosting solutions. It simplifies the deployment process by offering a powerful CLI and automated workflows, making it easy to deploy applications with minimal hassle. Additionally, Fly.io supports various programming languages and frameworks, including Next.js, making it a versatile choice for modern web development.

With the Wasp CLI, you can deploy the React frontend, Node.js backend (server), and PostgreSQL database generated by the Wasp compiler to Fly.io with a single command.

This is a MVP for Serverless Postgres.

1/ It uses Fly.io[0], which can automatically pause your database after all connections are released (and start it again when new connections join).

2/ It uses Oriole[1], a Postgres extension with experimental support for S3 / Decoupled Storage[2].

3/ It uses Tigris[3], Globally Distributed S3-Compatible Object Storage. Oriole will automatically backup the data to Tigris using background workers.

I wouldn't recommend using this in production, but I think it's in a good spot to provoke some discussion and ideas. You can get it running on your own machine with the steps provided - connecting to a remote Tigris bucket (can also be an AWS S3 bucket).

[0] https://fly.io

[1] https://www.orioledb.com/

[2] Oriole Experiemental s3: https://www.orioledb.com/docs/usage/decoupled-storage

[3] Tigris: https://www.tigrisdata.com/

Fly.io - Very similar to Heroku too, easy to use and support for multiple stacks/languages.

Fly.io is a cloud platform that allows developers to easily deploy scalable applications. In this article, we will introduce how to manage databases effectively in an application using Remix, Prisma, and LiteFS on Fly.io.

Deploying applications can be a complex and time-consuming process. App deployment tools, such as Fly.io, aim to simplify this process by providing a platform for easily deploying and managing applications.

To begin with, you could go with a Platform-as-a-Service (PaaS) provider like Heroku, or Fly for a more seamless experience. You can also do a bit of DevOps: set up a Docker installation on a VPS and deploy your app there.

To begin visit fly.io to create an account. Next install flyctl a command line tool for creating and deploying fly apps. macOS

For frontend deployment, I used Netlify (for the generous free package) and the recommended fly.io for server + database (also cheap package).

Create an account on Fly.io.

uses lit and @lit/task which must be imported into your HTML file. You can include dependencies with an importmap, pulling them from a CDN:

Lit and Rimmel are some relatively similar libraries as they both make use of tagged templates.

This course focused on Web Components via Lit. I think we spent a single week (two classes) learning the foundations of web development. Never taught us a single line of HTML, told us to google CSS, and spent that first week showing us what JavaScript does. Personally wish we spent some more time understanding the foundations, but even if I don't know exactly what I am doing... I have been able to accomplish some great stuff.

That is the reason why I experiment with the TiniJS framework for a while. It is a collection of tools for developing web/desktop/mobile apps using the native Web Component technology, based on the Lit library. Thank you the Lit team for creating a great tool assists us working with standard Web Component easier.

https://github.com/lit/lit/tree/main/packages/labs/virtualiz...

actually, looking at it (https://lit.dev/), i do exactly that.

I also define a `render()` and extend my own parent, which does a `replaceChildren()` with the render. And, strangely, I also call the processor `html`

I'll still stick with mine however, my 'framework' is half-page of code. I dislike dependencies greatly. I'd need to be saving thousand+ lines at least.

Here, I don't want a build system to make a website; that's mad. So I don't want lit. I want the 5 lines it takes to invoke a dom parser, and the 5 lines it takes do define a webcomp parent.

I rather like https://lit.dev/ for web components so far.

For the reactivity stuff, you might want to read https://frontendmasters.com/blog/vanilla-javascript-reactivi... - it shows a bunch of no-library-required patterns that, while in a number of cases I'd much rather use a library myself, all seems at least -basically- reasonable to me and will probably be far more comprehensible to you than whatever I'd reach for, and frameworks are always much more pleasant to approach after you've already done a bunch of stuff by banging rocks together first.

I work on Lit, which I would hesitate to call a framework, but gives a framework-like DX for building web components, while trying to keep opinions to a minimum and lock-in as low as possible.

It's got reactivity, declarative templates, great performance, SSR, TypeScript support, native CSS encapsulation, context, tasks, and more.

It's used to build Material Design, settings and devtools UIs for Chrome, some UI for Firefox, Reddit, Photoshop Web...

https://lit.dev if you're interested.