A personal cloud-style accounting application. 
This application solves two issues, which are already solved in other existing personal accounting apps separately: desktop applications are truly personal, but you can access them only from your desktop, where they are running. Cloud based personal accounting solutions are available from anywhere, but using it you practically share your financional state and history with service owners.
MDG (acronym of Moi.Den.Gi, that means "my money" in Russian) is a truly personal tool that can be deployed anywhere on your personal server (in the internet) and will be available from any point, from which that server is accesible, so making it cloud like.
This is a recommended way to deploy MDG for actual use. VM image contains Atomic OS image with MDG preinstalled and backup system preconfigured.
Appliances are available since version 0.5.0 and are built for each release. If you would like to use development versions, you have to manually deploy with ansible
Just grab the VM package from github and import it
into you virtualization system as a new VM. Boot up the VM and try to access MDG in VM's port 80. Default VM credentials for remote access are mdg/mdg.
Console access is passwordless.
Appliance is shipped with preconfigured backup service with timer set to 21:21 local time, that will make a full dump of your MDG database and publish it for Duplicati backup.
Duplicati web interface is available at http://VM.ip:8200/ and needs to be configured manually, to backup that database dump file somewhere else. Backup file will be available under '/source/dump_mdg.sql' file in the Duplicati container.
MDG database can be restored from the dump by running following commands:
docker-compose -f /opt/mdg/docker-compose.yml stop mdg
docker run -i --rm --network mdg_backend --link mdg-postgres-1:postgres -ePGPASSWORD=mdg postgres:14.3 psql -h postgres -U mdg -d postgres < dump_mdg.sql
systemctl restart mdg
It is your duty to upload MDG database dump to the system.
To upgrade your MDG appliance make a backup, move it out of the VM, delete VM, redeploy with the new image and restore database
Appliance is based on the CoreOS distribution,a minimal operating system for running containerized workloads. VM for Appliance is a 1 CPU/4GB virtual machine with 20GB of available space. The minimum requirement is about 10GB of disk space, rest is used for your data.
Appliance is configured with Butane script at mdg.bu, which can be adjusted to meet your need. That script downloads MDG files, configures execution
environment and prepares the appliance. Script needs to be converted to the Ignition file using Butane tool:
butane --pretty --strict mdg.bu > mdg.ignHaving ingition file ready, download latest CoreOS OVA image for Virtual box, import it and apply the configuration
VBoxManage import --vsys 0 --vmname "MDG" --cpus 1 --memory 1G fedora-coreos-36.20220618.3.1-virtualbox.x86_64.ova
VBoxManage modifymedium disk /path/to/disk.vdi --resize 20G
VBoxManage guestproperty set MDG /Ignition/Config "$(cat mdg.ign)"Another way of deployment is via docker compose.
You need to install docker engine and docker compose before deployment, using appropriate procedure for your operating system.
The version is configured by .env file specifying two tags:
MDG_TAG=master
UI_TAG=masterYou'll need to create that file and after that you have to download docker compose descriptor and start MDG:
wget https://github.com/akashihi/mdg/raw/master/docker-compose.yml
sudo docker-compose up
MDG should start in several seconds, depending on your hardware and internet connection and web interface will be available at http://yourip/
Deployment from the source code is the most complex, but may be useful in case you do not like docker or would like to improve MDG.
Building:
Other (and newer) versions should work too.
Deployment:
MDG consists of java based backend application and React frontend, with source code in a single repository at Github:
git clone https://github.com/akashihi/mdg.git
To build MDG backend you'll have to use bundled Maven:
cd mdg/backend
mvnw clean package spring-boot:repackage
This will produce file target/mdg.jar.
The web ui requires one more step:
cd mdg/frontend
npm install
npm run build
This will produce a dist.tar.gz archive.
Start postgresql and create a database owned by some user. By default database mdg with user mdg and password mdg is expected. You can
adjust database credentials in the application-local.properties file.
Put provided hunspell dictionaries to the elastic configuration directory, then start elastic. Configure nginx to serve web ui files and proxy mdg server. Sample server configuration is below:
server {
listen 80;
server_name localhost;
location / {
root /opt/mdg-web-ui;
index index.html index.htm;
}
location /api {
proxy_pass http://localhost:8080/;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Port $server_port;
}
error_page 404 =200 /index.html;
}
- You can run
mdg.jaras usual withjava -jar mdg.jar. This will start server and create database structure. - Unpack web ui archive with
tar zxvf dist.tar.gzto the path, specified in nginx config (/opt/mdg-web/uifor example) and start nginx.
Check that everything works by accessing web user interface.
TBD
We are using GitHub flow for development.
TBD
We use SemVer for versioning. For the versions available, see the tags on this repository.
- Denis Chaplygin - Initial work - akashihi
This project is licensed under the GPLv3 License - see the LICENSE file for details.