backend

README

Envelope Zero backend

Envelope Zero is fundamentally rooted in two ideas:

• Using the envelope method to budget expenses into envelopes.
• Zero Based Budeting, meaning that you assign all your money to an envelope. Saving for a vacation? Create an envelope and archive it after your vacation. Rent? Create an envelope that gets a fixed amount of money added every month.

Features

For a high level view of planned complex features, check the milestones.

To see all planned features, check the list of issues with the enhancement label.

Usage

The recommended and only supported way for production deployments is to run the backend with the OCI image.

Configuration

⚠ If you do not configure a postgresql database, sqlite will automatically be used. Mount a persistent volume to the /data directory - this is where the sqlite database is stored. If you do not do this, you will lose all data every time the container is deleted.

The backend can be configured with the following environment variables. None are required.

Name	Type	Default	Description
GIN_MODE	One of release, debug	release	The mode that gin runs in. Only set this to debug on your development environment!
LOG_FORMAT	One of json, human	json if GIN_MODE is release, otherwise human	If log output is written human readable or as JSON.
DB_HOST	string		hostname or address of postgresql
DB_USER	string		username for the postgresql connection
DB_PASSWORD	string		password for DB_USER
DB_NAME	string		name of the database to use

Deployment methods

If you want to deploy with a method not listed here, you are welcome to open a discussion to ask any questions needed so that this documentation can be improved.

On Kubernetes

You can run the backend on any Kubernetes cluster with a supported version using the morremeyer/generic helm chart with the following values:

image:
  repository: ghcr.io/envelope-zero/backend
  tag: v0.2.1

# Only set this when you want to use sqlite as database backend.
# In this case, you need to make sure the database is regularly backed up!
persistence:
  enabled: true
  mountPath: /app/data

ports:
  - name: http
    containerPort: 8080
    protocol: TCP

ingress:
  enabled: true
  hosts:
    - host: envelope-zero.example.com
      paths:
        - path: /api
  tls:
    - hosts:
        - envelope-zero.example.com

If you do not use the root path /, but a prefix, make sure your reverse proxy writes the used prefix in the x-forwarded-prefix header. That header is used by the backend to generate the correct URLs for resources.

Supported Versions

This project is under heavy development. Therefore, only the latest release is supported.

Please check the releases page for the latest release.

Contributing

Please see the contribution guidelines.