31–39 of 39 posts
Oh dang I love this. I also wish someone would take something like this and go full Phoenix with it.
Would it have to be manual deployments? Since the infrastructure for other approaches usually assumes that there isn’t any critical data on a single instance.
The .sqlite file would have to be persisted somehow?
Something feels wrong to use Current.account in models.
VM with 1GB ram and some swap file can easily run rail app, Postgres and redis. With that you don’t have to limit yourself to not able to scale later. I never used sqlite, can it be used by multiple process simultaneously? Eg rails server and rails console
What would be the deployment strategy here? Would it have to be manual deployments? Since the infrastructure for other approaches usually assumes that there isn’t any critical data on a single instance. The .sqlite file would have to be persisted somehow?
This doesn’t mean that you have to have manual deployments tho. You simply need a file system and some persisted storage, which you should already have as most deployment setups don’t want to nuke and pave every static asset on every deployment.
The article is actually a great introduction to interfacing a Rails app to Replicate AI!
I agree. I didn't learn anything about using LiteStack in a Rails App, but I did enjoy the article and learned of a few new gems and services. The article is the first part of a series and so hopefully in the next part they get into the integration of LiteStack with the app.
Earlier quoted context omitted.
Or you could give it up and move to Phoenix; I've never looked back.
Link?