Chris Burns

So, as far as I'm aware this was because of the following bits of code in the Dockerfile that you can see on the [backstage docs](https://backstage.io/docs/deployment/docker#host-build): ```dockerfile # install sqlite3...

To be honest, I don't even think it's worth mentioning. The backstage docs themselves say that `sqlite` are for local setups and local testing and that users should focus on...

I agree! I've pushed up the newest changes on the weekend, let me know if all looks well :+1:

Which ever one is best is good for me. I only said `helm-docs` as I've used it on another Chart. This issue was moreso around getting automatic documentation generation as...

Closing as this has repo has been deprecated in favour of https://github.com/backstage/charts

@cmoulliard Yep, this sounds good. At the moment, I use Istio Gateway with Cert Manager and Let's Encrypt, so we don't really use the Ingress resource in the Chart. However...

@vinzscam @cmoulliard Welcome your thoughts on the above. It currently doesn't run any Linting because it hasn't detected a change with the Charts.

Closing as this repo has been deprecated in favour of https://github.com/backstage/charts

What is the status with this, we have realised we want to use this on our projects @Stanislav2017 @janwillies Additionally, is the `gitlab_deploy_key_enable` something that can be done also? Otherwise...

Having this problem also with the following # ElasticSearch Deployment via Operator ```yaml apiVersion: elasticsearch.k8s.elastic.co/v1 kind: Elasticsearch metadata: name: elasticsearch namespace: elastic-system spec: version: 8.0.0 nodeSets: - name: default config:...