-
Notifications
You must be signed in to change notification settings - Fork 34
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
Document stack #401
Document stack #401
Conversation
Co-authored-by: Adam Hendel <ChuckHend@users.noreply.github.com>
Update yaml name and secretName
…dd-document-stack
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.
Just rename anything "Mongo" to "FerretDB" and name the stack "FerretDB" and I think good to go.
volumes: | ||
- name: ferretdb-data | ||
ephemeral: | ||
volumeClaimTemplate: | ||
spec: | ||
accessModes: | ||
- ReadWriteOnce | ||
resources: | ||
requests: | ||
storage: 1Gi | ||
volumeMounts: | ||
- name: ferretdb-data | ||
mountPath: /state |
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.
it would be nice to not need this (because it would make the container much faster to move across servers) - and I thought we found a way to not include it? In any case, that can be a follow up or maybe it's needed for some reason
@@ -22,6 +22,8 @@ lazy_static! { | |||
serde_yaml::from_str(include_str!("templates/vectordb.yaml")).expect("vectordb.yaml not found"); | |||
pub static ref GEOSPATIAL: Stack = | |||
serde_yaml::from_str(include_str!("templates/gis.yaml")).expect("gis.yaml not found"); | |||
pub static ref MONGO_ADAPTER: Stack = serde_yaml::from_str(include_str!("templates/mongo_adapter.yaml")) |
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.
is it too much trouble to name anything that's "Mongo" to "Ferret" for consistency and trademark concerns. Also I think it should just be called "FERRET_DB" or just "FERRET", not including "ADAPTER"
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.
The functionality provides users a Mongo compatible protocol with Postgres as the backend storage.
No description provided.