linen.dev VS taxonomy

I believe this is the Elixir server they blogged about: https://github.com/Linen-dev/linen.dev/tree/main/apps/push_s...

The code is here: https://github.com/linen-dev/linen.dev It is actually kind of tricky to self host since there are quite a few services that needs set up and we could use quite a bit of work in our documentation.

I'm hoping this concept takes off. This is the most prominent project in this space, Linen Think discord, but open source, indexable and not closed off unless otherwise specified by the people running the instance. Can even anonymize users if you so choose but the messages themselves can be searchable by the public. I think discord like communities already are the next thing in many ways, but its closed nature keeps it from getting as much regular viewership as say a subreddit, which is also indexable by the public web. I think it's the next thing because it takes what's good about reddit and discord and does away with a lot of their downsides. Oh it's open source too!

Open source https://github.com/linen-dev/linen.dev but not federated

I was reading through https://github.com/Linen-dev/linen.dev/blob/main/docs/nextjs... and https://github.com/Linen-dev/linen.dev/blob/main/apps/web/.e...

Do I really need all these API keys for s3, sentry, push service, ngrok, etc to run a web app on a home network?

This reminds me slightly of: https://github.com/Linen-dev/linen.dev

This is one of the reasons I created Linen.dev(A Google searchable Slack/Discord alternative) I had a decent size Slack and Discord community for my previous project and it became a blackhole of information.

You can check it out the repo here: https://github.com/linen-dev/linen.dev

Linen.dev/s/cypress

I am building this app with inspiration from Taxonomy and Acme corp so a lot of the design comes from there.

View on GitHub

Now, I must confess that I'm primarily a back-end engineer, and crafting a beautiful front-end was, well, a bit of an adventure. To keep things straightforward, I opted for simplicity. I figured I could enhance it as my customer base grew, as the real value, of course, lies in the robustness of the API and its backend. Looking back, I might consider using a template like https://tx.shadcn.com/ if I were to start all over again. It appears to be a great starting point for any SaaS, but the setup might pose some challenges.

Check out these two GitHub repositories: https://github.com/sadmann7/skateshop/ and https://github.com/shadcn/taxonomy/. They both use Next.js 13 and have well-structured folders and well-written code. Next.js provides performance optimization. To improve it further, avoid loading unnecessary items and use a CDN for fast content delivery. Both not loading unnecessary content & lazy loading) and CDN is 2 individual topics to dive into.

I've also been inspired by this repo, but the Vercel template seems more achievable for me at this point.

In addition to the repository I mentioned in my original post, I've also been inspired by another repository (Taxonomy Repo) which has implemented a similar Stripe integration. However, this one is a bit more complex and I'm finding the Vercel template to be more achievable for my current skill level.

I'm currently working on a Next.js project where I'm trying to integrate Stripe for payments and webhooks. I've been following the Taxonomy GitHub repo for guidance, particularly for setting up the app router and the lib files.