-
Notifications
You must be signed in to change notification settings - Fork 38
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
feat(other): major improvement of deployment #7925
base: master
Are you sure you want to change the base?
Conversation
22e9342
to
92cf050
Compare
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.
Hey, very nice as far I can understand. 🥰
Only little hints or suggestions.
Shouldn't be the place for the hetzner
folder inside the deployment folder?
Would be nice to have an explanation pairing. Or?
CATEGORIES_ACTIVE: | ||
webapp: |
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.
Have an empty line here?
CATEGORIES_ACTIVE: | |
webapp: | |
CATEGORIES_ACTIVE: | |
webapp: |
NEO4J_dbms_memory_heap_max__size: "" | ||
NEO4J_dbms_memory_pagecache_size: "" | ||
NEO4J_dbms_security_procedures_unrestricted: "algo.*,apoc.*" | ||
NEO4J_dbms_default__database: |
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.
Should we just set the default name here?
Because then it's clarified what it is …
NEO4J_dbms_default__database: | |
NEO4J_dbms_default__database: "neo4j" |
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.
kustomize
with k
: interessting
d146e16
to
c3b5f96
Compare
2f9bfce
to
9a268cd
Compare
Motivation ---------- Kubernetes: * backend becomes a statefulset (exclusive volume mount) See: https://spacelift.io/blog/statefulset-vs-deployment * implement neo4j backup with job Docker: * consistent targets across all dockerfiles * remove redundant labels * remove unnecessary build args * remove obsolete networks * remove development dependencies for production Rebranding: * add image tags for local tagging and pulling * use Github's docker build workflows * use Github container registry * ONBUILD to simplify caller Dockerfiles * docker compose for branding Tooling: * same node --version as in dockerfile Docs: * missing step in README.md
It's better to keep them all in a separate repository
* better image tag defaults * split neo4j into its own chart (for re-use) * use application defaults where possible
and add labels for neo4j enterprise
Motivation
Kubernetes:
See: https://spacelift.io/blog/statefulset-vs-deployment
Docker:
Rebranding:
Tooling:
Docs: