CodebaseUp

@rogeroba Thanks, Roger! 🤓 Q1: Does it currently support payments? The Stripe integration is currently in progress, and I plan to have it delivered this Friday. I've just fixed the inconsistency on the pricing page – thanks for bringing it to my attention. Q2: Hosting? I recommend using Vercel (and therefore serverless) for a seamless experience. The main app is built with Next.js (v14, App Router), and it can also be deployed outside Vercel, like on Render, if that's your preference. Q3: Does it automate infrastructure creation, configuration, and deployment? Does it include CI/CD automation? Yes, it certainly does. It has been tested on Vercel. You can simply run 'git push' and it will be deployed. Each separate branch comes with its own preview deployments. To ensure reliability, all tests (currently Typescript/ESLint) must pass; otherwise, the deployment gets canceled, keeping you safe. Q4: Do we get updates over time? Absolutely! I'm building it in public on Twitter/X, and there's a member-only project roadmap on GitHub. Even though I'm the sole developer, I create Pull Requests for everything, so members can see and contribute to the progress. Q5: Any plans to support other tech stacks besides Next.js? Yes, I'm also a fan of Remix and Python/Django, which are part of my stack. What would you like me to consider? Q6: Can I host using my custom domain? Yes, you can. Just deploy the codebase to Vercel and add your custom domain in a few clicks. Q7: Does it set up DNS? For example, my custom domain for the landing page, e.g., app.example.com for my app, blog.example.com for my blog, etc...? Absolutely, one of the advantages of the built-in Turborepo modularity is that it allows you to separate packages and apps. This means apps can be deployed separately on their own domains or subdomains.

@jhavej thanks for the thorough answers! Everything is clear now, thanks! As for the diff tech stacks, I'm a fan of Ruby on Rails + Next.js combo, would you consider that? What do you mean with built-in turborepo modularity, btw? Would I configure it directly on Vercel, like "folder 'blog' in my monorepo should be deployed to 'blog.example.com'"? Lastly, does it have built-in support to multiple envs (e.g. dev and prod — dev.example.com VS example.com)? Or would I have to configure that on my own?

@rogeroba Let's consider a scenario where you have three apps within the monorepo (app/web, app/blog, app/docs). All these apps utilize functionalities from shared packages, such as packages/database and packages/ui. When using Vercel, you can create separate projects for each app, all linked to the same repository. You only need to specify a root path (e.g., app/web, app/blog, etc.). Vercel is fully compatible with Turborepo, so deployments work seamlessly out of the box. Each Vercel project offers independent configuration, allowing you to set custom (sub)domains and environment variables for various environments (production, preview, and development). In a nutshell, you set up your environment variables and go live. If purchasing CodebaseUp Pro isn't the right fit for you, consider trying CodebaseUp Core. It's a public repository that includes a subset of Pro modules, and it's still highly capable. https://github.com/jhavej/codeba... Regarding your tech stack, it seems you use RoR for API endpoints and the database, along with Next.js for the frontend, right? Have you ever thought about transitioning entirely to Next.js? Thanks, Roger, I appreciate your feedback.

@jhavej got it, that sounds awesome! Thanks for linking me to a free version of the Pro package, I'll check it out 😊 That's right, RoR for API and Next.js for FE. I have considered going full Next.js, but the thing is that I already have a BE in RoR, so it would require a full migration, and on top of that I'm already quite comfortable (read: productive) with RoR and its stack, so those were the two main reasons I haven't made the switch. But I'll reconsider it 😅 Thanks for taking the time to share your knowledge and explaining the product better 🙏 best of luck on your sales! Keep shipping! 🚀

@rogeroba You're most welcome, Roger. You gave me plenty of ideas on what I should include in the documentation for CodebaseUp, thanks. I used to develop SW the same way - Django for BE, and pure React.js for FE. Then I discovered Next.js & Vercel and its convenience... I truly value the easy way to end-to-end type safety and the automated CI/CD. Thanks and let's ship things fast! 🚀

@diego_medina7 Thanks, Diego! 🤩 Remember to schedule our 1-on-1 coding session, I'll be happy to help

@porta7511 Thank you, Hrvoje! I also think CodebaseUp might be the solution for "wannapreneurs" — those aspiring to dive into online projects but finding themselves daunted by the complexities of coding. I'm thrilled by the prospect of helping them break down this barrier.

@ondrejsedlacek Hi Ondrej, thank you for your interest! The design system in CodebaseUp is built using Radix UI and Tailwind CSS, wrapped as popular shadcn/ui. Radix UI provides an unstyled and accessible library of building blocks, while Tailwind CSS allows you to style these blocks as you like. The shadcn/ui brings it all together, offering a starting point for further customization. There is no need for hacking, you own the code so you can tweak it yourself. This approach allowed me to create the ready-to-use landing page components. If you like the design, you can easily copy and paste the code to use them as you see fit. Or you can use them for your own modifications. Check it out here: https://www.codebaseup.com/en/do...

@mfts0 Thanks Marc, happy to help. It also helped me to validate that even though CodebaseUp is primarily a starter kit it can be merged into existing projects like Papermark in a few hours... okay, that PR review will likely take longer than the coding itself 😀

@manmohit Thank you so much, Manmohit! 🚀 While it's just me, a solo maker behind CodebaseUp, your support means the world! 🙌