-
Notifications
You must be signed in to change notification settings - Fork 110
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
Separate the global location of files per OS & create a configuration trait to read them #171
Conversation
John, I would love to get this in soon. Or some other solution. Right now eg. |
@@ -15,6 +16,13 @@ cargo build -p spacetimedb-standalone | |||
export STDB_PATH="${STDB_PATH:-$(mktemp -d)}" | |||
mkdir -p "$STDB_PATH/logs" | |||
|
|||
function cleanup { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gefjon was this related (i.e., cleaning up the same stuff) that you were talking about earlier today as an ever growing pile of stuff in the temp dir?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, this appears to be unrelated.
Piotr, this is the PR that was just mentioned that we want to make sure is ok for cloud. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Semantics look good; here are some minor stuff to fix.
Co-authored-by: Mazdak Farrokhzad <twingoow@gmail.com> Signed-off-by: Mario Montoya <mamcx@elmalabarista.com>
Description of Changes
Was hardcoded in the location of
\stdb
as the global database path.Here instead it use an adequate location per-OS and a configuration trait to read the location of the files, also for test.
API
If the API is breaking, please state below what will break