Not so easy

Hey @josedandrade, I'm not sure what issue you're currently facing. You don't need to configure a third-party database anymore. I've updated the template. All you need to do is configure the API key of the provider you want to use. Thanks!

I need documentation. It is scarce and confusing. Also, is it using Supabase?

All you need to do is configure the API key of the provider you want to use.

No, it now uses pgvector.

I need documentation. It is scarce and confusing. Also, is it using Supabase?

Hey @josedandrade, sorry about it. Just to clarify, Dialoqbase is a side project, and I'm unsure if it's production-ready

Dialoqbase railway docs:
https://dialoqbase.n4ze3m.com/guide/self-hosting-railway.html

You no longer need Supabase; simply configure the API key of the provider you wish to use. For any issues, feel free to mention them here or on the Dialoqbase GitHub repository: github.com/n4ze3m/dialoqbase/issues

Thanks!

Thanks. I am testing it already. It looks quite alright. I will share my experience. As soon as I get very familiar with it I will put in production for a while, just to see how it goes. I do, would like to see how and what is being saved to the database. If there is anything I should know about, please let me know.

Congrats to the people that have worked on this. Looks solid so far.

Sporadic crashes. Moved to a hobby account just now to hace more power.

Any of you have some recommended minimum setup?

The hobby plan doesn't have more power per se, it's the same hardware, just more of it.

What was the reason for the crashes?

I have not found the reason, but seems to be when I integrate Telegram.

Have you checked the deployment logs for errors?

I have not found the reason, but seems to be when I integrate Telegram.

Hey @josedandrade, if possible, could you please share the logs?

Thanks for the follow up. I find this app to be truly useful.

It has been working today. Only difference is I have not used custom domain.

Will report later, if it crashes, once I set custom domain.

In case you encounter any issues with Dialoqbase, feel free to open an issue on GitHub at https://github.com/n4ze3m/dialoqbase/issues/new. Thanks!

For the DB_SECRET_KEY variable on the Dialoqbase service, instead of hardcoding the value to super-secret-key and asking the user to change it, you can use ${{secret(32)}} and it'll generate a secret for the user.

Reference: https://docs.railway.app/guides/create#template-variable-functions

Updated! Thanks for the suggestion :)

Thanks! Could you also update your template to a v2 template? If you visit your account templates page, you should see an option to edit your template in the composer. Hit that and then update it and it should become a v2 template! :)

Done :)

Hey, so I think the conversion might have broken the template as database URLs aren't automatically injected into all services automatically. You should be able to fix this by specifying the REDIS_URL variable on the Dialoqbase service similar to how you've specified the DATABASE_URL.

fixed :)

I am satisfied with what I have been able to achieve so far. But, in case of questions, where is the proper site to submit questions, issues, etc? Here or Github?

Hey, in case of any issues, you can report them on Dialoqbase's GitHub at https://github.com/n4ze3m/dialoqbase/issues.