Migrations fail and app does not exit
If migrations fail, your app should exit. Especially when logging a "fatal" error.
3 Replies
I was here evaluating this app for an org, and have decided against using twenty.
Basically, it boils down to:
- no openid connect support
- this migration bug (very poor code quality if you did not catch this immediately)
- the poor documentation.
- seemingly not allowing seeding the initial user
@charles
As someone who is constantly overloaded with the amount of hats I have to wear - sysadmin, helpdesk, web developer. I am very much frustrated that a full team working on this as their day job is hyping up this project as the best thing since sliced bread, and utterly unable to deliver.
Do better. Orgs want to use you.
Thanks for the feedback, I think you are expecting a production ready software where we know we are far from there at the moment (we are about to release v0.12...). Building a CRM is quite complex and our strategy is to iterate as fast as possible to understand how things should be built
Twenty is not ready for self-hosting if you want a seamless experience at the moment, it will be at some point when we feel ready for a v1.0
Regarding the migration issue:
- right now the migration is run by the main app (so it loads everything, which I don't consider being a big issue as you'll likely run Twenty on the same machine anyway). To run Twenty, the server needs a bit more than 2GB at the moment, my guess is that we can optimize it below 2GB without too many issues but it's not a trivial task
- the script says it has been successfully executed while it was not ; this is a problem, we will investigate it tomorrow
@Lehransmedallion Hey! Are you looking for more custom CRM solution for the org or you found another way?