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

feat(other): major improvement of deployment #7925

Draft
wants to merge 9 commits into
base: master
Choose a base branch
from
Draft

Conversation

roschaefer
Copy link
Member

@roschaefer roschaefer commented Oct 8, 2024

Motivation

Kubernetes:

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

@roschaefer roschaefer force-pushed the hetzner branch 3 times, most recently from 22e9342 to 92cf050 Compare October 9, 2024 00:12
@Tirokk Tirokk changed the title feat: first deployment in k3s on hetzner feat(chore): first deployment in k3s on hetzner Oct 9, 2024
@Tirokk Tirokk changed the title feat(chore): first deployment in k3s on hetzner feat(other): first deployment in k3s on hetzner Oct 9, 2024
Copy link
Member

@Tirokk Tirokk left a 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?

Comment on lines 18 to 19
CATEGORIES_ACTIVE:
webapp:
Copy link
Member

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?

Suggested change
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:
Copy link
Member

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 …

Suggested change
NEO4J_dbms_default__database:
NEO4J_dbms_default__database: "neo4j"

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

kustomize with k: interessting

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
@roschaefer roschaefer changed the title feat(other): first deployment in k3s on hetzner feat(other): major improvement of deployment Oct 27, 2024
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In Progress
Development

Successfully merging this pull request may close these issues.

2 participants