Founder here. Self hosting is a thing - just "pip install anvil-app-server"!

https://anvil.works/open-source

To be fair, it has a free tier which gives you most of Anvil's features and lets you build unlimited apps. There's also the open-source app server if you want to host your apps yourself and work around the paid tier's DB limits: https://github.com/anvil-works/anvil-runtime

The runtime is open source: https://github.com/anvil-works/anvil-runtime

https://github.com/anvil-works/anvil-runtime#using-the-stand...

The code is GNU AFFERO GENERAL PUBLIC LICENSE Version 3.

anvil server

Anvil is a platform for building web apps with nothing but Python - no HTML, CSS or JavaScript required. Anvil also comes with lots of built-in features like one-click deployment, databases, user authentication, email and the open-source app server.

anvil.works

Anvil | Software Developer | Cambridge, UK | On-site/Semi-Remote | Full-time or Part-time | https://anvil.works/jobs

Anvil | Junior Software Developer | Cambridge, UK | On-site/Semi-Remote | Full-time or Part-time | https://anvil.works/jobs

Anvil | Developer Advocate | Cambridge, UK | On-site/Semi-Remote | Full-time or Part-time | https://anvil.works/jobs

Help us fix web development at Anvil (https://anvil.works)!

Web development is way too hard – Javascript, HTML, CSS, SQL, and frameworks coming out of your ears. So we built Anvil: a simpler way for anyone to build full-stack web apps, entirely in Python. Anvil is a web framework; it’s an online code editor; it’s a GUI builder; and it’s a hosting platform. And you’ll be helping us with all of it.

We're looking for:

SOFTWARE DEVELOPERS:

Build the platform that's fixing web development for everyone. You’ll be working on the Anvil editor (that’s the development environment, code editor, drag-and-drop designer, version control, and so on) and the Anvil runtime (that’s the Python-to-JS compiler, UI toolkit, database, integrations, and the hosting engine that makes it so easy to deploy).

Our stack is mostly Javascript, Clojure and Python (in descending order of line count). We don’t need you to be an expert in all of these already, and for the junior role we don't need any. Otherwise, we’ll want to see evidence that you can hit the ground running with at least one of them – or that you’re a great all-rounder who won’t have a problem with any of them.

Much (or most) of your work will be open source: https://anvil.works/open-source

DEVELOPER ADVOCATES:

We need developers with great communication skills, to show people how to build awesome things with Anvil. You’ll be writing how-to guides, blog posts and tutorials, building example apps, presenting Anvil at conferences (when those resume), and helping our users – from individual developers to huge tech companies – build their applications. And then you’ll help us work out how to improve Anvil for them.

It's rewarding work – developers love being introduced to Anvil (our stand is always crowded[0] at conferences!). Plus, there are all the advantages of an early-stage startup: lots of autonomy, and huge impact.

We're bootstrapped and profitable, with customers ranging from tiny startups to household names. Find out more: https://anvil.works/jobs

Are you using the `--uplink-key` flag or `--client-uplink-key` flag when running your app with the app server? Anvil App Server - advanced config

import { unstable_noStore as noStore } from "next/cache"; import Link from "next/link"; import { CreatePost } from "~/app/_components/create-post"; import { getServerAuthSession } from "~/server/auth"; import { api } from "~/trpc/server"; export default async function Home() { noStore(); const hello = await api.post.hello.query({ text: "from tRPC" }); const session = await getServerAuthSession(); return (

Create T3span> App h1>

First Steps →h3>

Just the basics - Everything you need to know to set up your database and authentication. div> Link>

Documentation →h3>

Learn more about Create T3 App, the libraries it uses, and how to deploy it.div> Link> div>

{hello ? hello.greeting : "Loading tRPC query..."}p>

{session && Logged in as {session.user?.email}span>} p> {session ? "Sign out" : "Sign in"} Link> div> div> div> main> ); } async function CrudShowcase() { const session = await getServerAuthSession(); if (!session?.user) return null; const latestPost = await api.post.getLatest.query(); return (

{latestPost ? (

Your most recent post: {latestPost.name}p> ) : (

You have no posts yet.p> )} div> ); }

I thought he was making stuff up - "t3 stack vs t4 stack". But about 2 minutes in, I realized that I'd heard of a few things that he's talking about so I looked it up and they're real!

I think it's possible everything he's saying is true, more or less. LOL

t3: https://create.t3.gg

t4: https://t4stack.com

We start with a project that was bootstrapped with create-t3-app. For internationalization we use next-intl and set it up as described in the getting started guide. With this initial project setup we can jump into implementing localized error messages.

I used create-t3-app to scaffold the Next.js app, with TypeScript, Prisma, and "app router" enabled in the options. You can also use create-next-app for the job and install Prisma manually.

I agree that the quantity of publicly available code isn't the most reliable indicator of someone's seniority.

My issue with this individual arises from the discrepancy between his public claims of significant expertise in the content he produces. He positions himself as a highly experienced developer, attracting a large following of junior developers who take his advice at face value.

I am trying to collect data points supporting his claims of seniority. For instance, his website prominently features a statement that he is the creator of the T3 Stack. However, a review of the contributor statistics for the T3 Stack (https://github.com/t3-oss/create-t3-app/graphs/contributors)... minimal contributions from him, which raises questions about the validity of his claims.

I would recommend - https://create.t3.gg/

It uses the following, which as of late are pretty well know and common, so you can punch in your problems to stackoverflow, google, or chatgpt and get some pretty good answers.

It uses:

Nextjs (React), typescript, trpc (typescript rpc), auth, tailwind, and Prisma (ORM)

Though of course these could go out of fashion tomorrow, but I don't think the essential idea behind these libs and frameworks are that wacky, unique or unordinary.

Prisma ORM, is a little opinionated, and you could swap it out for Drizzle, which is basically typescript side sugared SQL.

TRPC might be also be a little sticky because it is tied to typescript, this is the tradeoff for the buttery smooth coupling for the fullstack experience. I think there exists a typed-rest solution out there, but haven't used it.

Personal anecdata, I used this stack for a little hobby project and it was FUN.

Open SaaS was built with Typescript, and because it’s a full-stack app, type safety from the back-end to the front-end can be a real lifesaver. I mean, some opinionated stacks have gotten hugely popular on this basis.

Let's start by creating a Next.js application. We will use the T3 stack (TypeScript, TailwindCSS, and Prisma ORM) for this tutorial to skip installing and configuring all the dependencies which is out of the scope of this article. You can find more information about the T3 stack.

https://github.com/t3-oss/create-t3-app

You still would need to add Stripe but there are so many examples publicly available that it should be straight forward