Feature: Add support for customized synth URL from env variable

[Evlos]

Usage:

---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: maybe
spec:
  template:
    spec:
      containers:
      - name: maybe
        image: evlos/maybe:latest
        env:
        - name: SYNTH_URL
          value: http://192.168.233.107:30800

[zachgoll]

Hey @Evlos, can you explain this change a bit further? I'm guessing your use case here involves some sort of incoming traffic proxy?

Typically, we only accept contributions that would apply to a broad range of users but want to make sure I understand this better first.

[Evlos]

Hello @zachgoll, yes, this is related to the incoming traffic proxy.

I find that maybe needs to frequently access online resources. I live in a remote mountainous area where the cellular signal is often unstable, so the maybe page can’t load at times, which is quite frustrating for me. I believe there are many people in the world living in areas with poor network conditions. Using an incoming traffic proxy to cache data and read from the cache when the network has issues, instead of waiting endlessly for the network to recover, would allow me to use the self-hosted maybe service.

Additionally, this approach can also save server resources for synthfinance.com.

You are doing a great job. I hope the above meets your requirements for accepting contributions.

[zachgoll]

@Evlos thanks for the explanation! That makes sense. We definitely want to provide support for various regions like this.