71–80 of 108 posts
Earlier quoted context omitted.
Sorry to hear that. We will make sure to check the logs. As for the login, we ask for a GitHub sign since we thought it would be most convenient and cost affective at this stage since all users are developers. Also, we use it to send the generated code to your GitHub repo.
Can you just make some page that doesn't save anything so we can see what you mean by "visual"? Or embed a youtube preview?
Earlier quoted context omitted.
Postgraphile is a great tool. The main difference is that we generate code that you can use any way you like and deploy anywhere you want. If you are a Node.js developer you get a boost that helps you focus on your business logic without giving up on the flexibility of code. Also, on our roadmap, we want to provide developers with a full set of features to make development easier, e.g. integration, connecting to diff…
Very cool. What DB is the tool currently using?
Built on top of immature overhyped tech (nestjs, prisma, etc...) with lots of issues. Something very common in the JS/NPM that always gives you headaches down the road. There's an arms race to sell hosting through immature buggy magical frameworks in the JS world, so this is to be expected. I'll take the one/two days to set up node, express, postgres with libs for now. What takes up the majority of the time is domain…
Here's a great example of why: I do a bunch of research before I started my project (https://listifi.app - for anyone curious) and decided to go with prisma.js. It looked like it was exactly what I wanted for a REST API built with koa.
I've dumped probably a month fulltime on the project and now that I have enough experience using prisma, I realized it really doesn't do what I want it to do and is actually making my life more difficult as a result.
So now I'm in the process of switching from prisma to knex. Having the glue hidden from me would really affect my willingness to switch technologies and increase my frustrations with any platform.
For any reasonably complex application, you will eventually need to eject.
I want to see how everything is pieced together. Even these js builders like parcel that "do everything for you" eventually don't work.
I'll take a couple of days to set things up the way I want them to over something that tries to do it all for me while only accommodating the happy path.
Again I want to say that this is my personal preference when building any project. I pick a few barebones libraries to help me build what I want and get out of my way.
That should be obvious when you look at my tech stack: https://listifi.app/u/erock/listifi-tech-stack
I'm curious - is there a tool handles solely the "frontend codebase generation" part of this? This looks great, but we already have a well-defined backend and REST API built using Python+FastAPI, with SQLAlchemy as an ORM and Postgres backing it. I am not a good UI/UX designer, but I understand and have built React applications, so really find myself looking for something that can take an OpenAPI.json spec and produc…
I'm curious - is there a tool handles solely the "frontend codebase generation" part of this? This looks great, but we already have a well-defined backend and REST API built using Python+FastAPI, with SQLAlchemy as an ORM and Postgres backing it. I am not a good UI/UX designer, but I understand and have built React applications, so really find myself looking for something that can take an OpenAPI.json spec and produc…
Are you using SQLAlchemy in a blocking way w/ FastAPI?
[0] https://fastapi.tiangolo.com/tutorial/sql-databases/ [1] https://fastapi.tiangolo.com/advanced/async-sql-databases/
Really cool, super intuitive UI. I won't really be able to use it though until it supports more data types, hopefully with specific DB's in mind.
Thanks. Can you please share what data types you have in mind?
Built on top of immature overhyped tech (nestjs, prisma, etc...) with lots of issues. Something very common in the JS/NPM that always gives you headaches down the road. There's an arms race to sell hosting through immature buggy magical frameworks in the JS world, so this is to be expected. I'll take the one/two days to set up node, express, postgres with libs for now. What takes up the majority of the time is domain…
I've been developing web apps in Node for a couple years and I'm done with it - I'm all in on Django + DRF now. I only made the switch a couple months ago and it's amazing how cozy I am with it: everything feels mature, stable and reliable. I reach out for 3rd party packages as needed but it doesn't feel like I'm gluing a Frankenstein together, or that I'm rolling out a bunch of code I don't want to own, or that I'm…
Now if only it came with all batteries included, and the DI wouldn’t be so funky, it would be even better, but it’s still lightyears ahead of express for building a comolicated application.
Built on top of immature overhyped tech (nestjs, prisma, etc...) with lots of issues. Something very common in the JS/NPM that always gives you headaches down the road. There's an arms race to sell hosting through immature buggy magical frameworks in the JS world, so this is to be expected. I'll take the one/two days to set up node, express, postgres with libs for now. What takes up the majority of the time is domain…
I'm inclined to agree. This is nothing against the OP but I never reach for boilerplate generators, even ones like `create-react-app`. Here's a great example of why: I do a bunch of research before I started my project ( https://listifi.app - for anyone curious) and decided to go with prisma.js. It looked like it was exactly what I wanted for a REST API built with koa. I've dumped probably a month fulltime on the pro…