Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhanced sqlite docu for how to use in production #535

Closed
wants to merge 1 commit into from

Conversation

schiwekM
Copy link
Contributor

Hi Rene,

I've added a block about running sqlite in production to the docu to improve guidance in valid use cases like running CAP as a proxy for S4.

BR,
Marten

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
@renejeglinsky
Copy link
Contributor

Hi Marten,

Thanks a lot! I'll discuss this and get back to you. :)

@renejeglinsky
Copy link
Contributor

Hi Marten,
could you enhance the description of the scenario and the boundary conditions, like losing data when the corresponding container is dropped and restarted? The technical configuration is the easier part compared to judging and identifying if one would really want to SQLite in prod.

@schiwekM
Copy link
Contributor Author

Hi Rene,

I encounter the issue with a partner in an S4 transformation. Basically they use their CAP app as a proxy for the S4 API and have no entities to persist. However when trying to start without any database, the server always crashed when trying to do cds.connect.to upon the request. The workaround was to just to add the sqlite db in prod as the requests are anyways forwarded to S4.

@johannes-vogel
Copy link
Contributor

4 transformation. Basically they use their CAP app as a proxy for the S4 API and have no entities to persist. However when trying to start without any database, the server always crashed when trying to do cds.connect.to upon the request. The workaround was to just to add the sqlite db in prod as the requests are anyways forwarded to S4.

I rather think that this is a configuration issue on the customer side. If you do not have any database, do not set a cds.requires.db entry in the package.json.

@schiwekM
Copy link
Contributor Author

schiwekM commented Dec 1, 2023

4 transformation. Basically they use their CAP app as a proxy for the S4 API and have no entities to persist. However when trying to start without any database, the server always crashed when trying to do cds.connect.to upon the request. The workaround was to just to add the sqlite db in prod as the requests are anyways forwarded to S4.

I rather think that this is a configuration issue on the customer side. If you do not have any database, do not set a cds.requires.db entry in the package.json.

Strangely when they did not, it crashed upon requests.

@johannes-vogel
Copy link
Contributor

@schiwekM Do you by any chance have a pointer for me look at the config?

@schiwekM
Copy link
Contributor Author

schiwekM commented Dec 4, 2023

@schiwekM Do you by any chance have a pointer for me look at the config?

Send an email with contact details

@johannes-vogel
Copy link
Contributor

@schiwekM I'd propose to close this PR.
I did not hear back and I'm rather sure that this is not required, if you do not have the need for a database.

@schiwekM schiwekM closed this Jan 26, 2024
@chgeo chgeo deleted the addition-to-sqlite-in-prod branch February 4, 2025 11:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants