Running Baserow locally with Helm

Technical Help
, ,
1

Please fill in the questionnaire below.

Technical Help Questionnaire

Have you read and followed the instructions at: *READ ME FIRST* Technical Help FAQs - #2 by nigel ?

Answer: Yes

Self-Hosted Installation and Setup Questions

Delete this section if you are using Baserow.io.

How have you self-hosted Baserow.

Running Helm charts with minikube on local machine

What are the specs of the service or server you are using to host Baserow.

Local macbook machine, M1

Which version of Baserow are you using.

Latest

How have you configured your self-hosted installation?

I’m using all in one version, the only changes are to the config.yaml file
global:
baserow:
domain: “localhost”
backendDomain: “api.localhost”
objectsDomain: “objects.localhost”

What commands if any did you use to start your Baserow server?

Commands given in the official guidelines for Helm.

Describe the problem

Describe, step by step, how to reproduce the error or problem you are encountering.

The problem is that I can’t access the baserow in local.
The setup you have from above, and using tool called Lens I’m doing port forwarding in order to access the frontend/backend api. However, I can’t rely on port forwarding in order to access it.
So, how do I access Baserow out of the box, without port forwarding?
I have also to connect backend api and other Java app, but I can’t since the connection can’t be established.

Provide screenshots or include share links showing:

How many rows in total do you have in your Baserow tables?

None, freshly installed instance is running

Please attach full logs from all of Baserow’s services

No errors in the log

2

Hi Vukey,

Could you try adding the following to your values.yaml file?

ingress:
  annotations:
    kubernetes.io/ingress.class: nginx
caddy:
  enabled: false

Assuming that you enabled the nginx ingress on your minikube, you should then be able to access Baserow via nginx.

Please let me know if that works for you!

3

Hey Joeri, thank you so much for assistance.
Unfortunately, it didn’t make a difference, yeah ingress is enabled.
Also, I’ve mapped the locfront.com to 127.0.0.1 in etc/hosts/.
This is the ingress config

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: baserow-ingress
  namespace: baserow
  annotations:
    # Add your specific annotations here, like cert-manager, rewrite-target, etc.
    nginx.ingress.kubernetes.io/rewrite-target: /
spec:
  rules:
  - host: locback.com  # Replace with your domain
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: wolfrow-baserow-backend-asgi # Replace with your service name
            port:
              number: 8000    
  - host: locfront.com 
    http:
      paths:
      - path: /         
        pathType: Prefix
        backend:
          service:
            name: wolfrow-baserow-frontend  # Replace with your service name
            port:
              number: 3000

This is config.yaml

global:
  baserow:
    domain: "localhost"
    backendDomain: "api.localhost"
    objectsDomain: "objects.localhost"

ingress:
  annotations:
    kubernetes.io/ingress.class: nginx
caddy:
  enabled: false
4

Hi Vukey,
I got it to work with by mapping the domain to the minikube ip.

minikube ip

I added the ip to the /etc/hosts file.

sudo echo "$(minikube ip) [myapp.com](http://myapp.com/)" >> /etc/hosts

Then you can access the app at myapp.com.Another way to access it is by using the minikube tunnel command, which will create a tunnel to the cluster and expose the services.

minikube tunnel

Could you give that a try?

5

Hi Joeri,

This seems to move it forward, however it’s timing out. The hosts are updated, but when tried to access the myapp.com, it times out. Can you share your config.yaml, so I can replicate it 1on1?