ledger-web | A web UI and HTTP API for Ledger CLI
kandi X-RAY | ledger-web Summary
kandi X-RAY | ledger-web Summary
ledger-web is a Python library. ledger-web has no vulnerabilities, it has build file available, it has a Strong Copyleft License and it has low support. However ledger-web has 10 bugs. You can download it from GitHub.
Ledger Web was initially created to bridge the gap between a smartphone and Ledger CLI by exposing a HTTP API. Since then it evolved into a more general web UI for Ledger.
Ledger Web was initially created to bridge the gap between a smartphone and Ledger CLI by exposing a HTTP API. Since then it evolved into a more general web UI for Ledger.
Support
Quality
Security
License
Reuse
Support
ledger-web has a low active ecosystem.
It has 54 star(s) with 12 fork(s). There are 8 watchers for this library.
It had no major release in the last 6 months.
There are 1 open issues and 3 have been closed. On average issues are closed in 275 days. There are 1 open pull requests and 0 closed requests.
It has a neutral sentiment in the developer community.
The latest version of ledger-web is current.
Quality
ledger-web has 10 bugs (0 blocker, 0 critical, 1 major, 9 minor) and 20 code smells.
Security
ledger-web has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
ledger-web code analysis shows 0 unresolved vulnerabilities.
There are 19 security hotspots that need review.
License
ledger-web is licensed under the AGPL-3.0 License. This license is Strong Copyleft.
Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.
Reuse
ledger-web releases are not available. You will need to build from source code and install.
Build file is available. You can build the component from source.
Installation instructions, examples and code snippets are available.
It has 4272 lines of code, 71 functions and 85 files.
It has low code complexity. Code complexity directly impacts maintainability of the code.
Top functions reviewed by kandi - BETA
kandi has reviewed ledger-web and discovered the below as its top functions. This is intended to give you an instant insight into ledger-web implemented functionality, and help decide if they suit your requirements.
- Render ledger as JSON
- Apply ledger rules to ledger data
- Normalize ledger data
- Apply replacement rules to ledger data
- Check ledger rule
- View for a ledger entry
- Revert the journal
- Append an entry to the ledger
- Call Ledger
- View the ledger
- Determines if this file can be reverted
- Returns a JSON representation of a ledger entry
- Create a ledger entry
- Register ledger
- Show ledger charts
- Show balance
- List all transactions
- Checks to see if the rule is unique
- Returns the kwargs for the form
Get all kandi verified functions for this library.
ledger-web Key Features
No Key Features are available at this moment for ledger-web.
ledger-web Examples and Code Snippets
No Code Snippets are available at this moment for ledger-web.
Community Discussions
No Community Discussions are available at this moment for ledger-web.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install ledger-web
Ledger Web is designed to be constantly running on a server so it's easily accessible from mobile devices. That being said, it's possible to run it on demand locally for example just to analyze the charts. The instructions below assume the former case though.
Clone the repository and install the dependencies:. Set up the database. SQLite is used by default, it can be changed in ledger/settings.py.
Clone the repository and install the dependencies: git clone https://github.com/vifon/ledger-web cd ledger-web virtualenv .venv . .venv/bin/activate pip install -r requirements.txt
Set up the database. SQLite is used by default, it can be changed in ledger/settings.py. ./manage.py makemigrations ./manage.py migrate
Set the access credentials: ./manage.py createsuperuser ./manage.py runserver Follow the instructions on screen and the enter http://localhost:8000/admin Add a new entry in the Ledger paths table for your user, pointing it to your Ledger file. If you want to use the HTTP API, add an access token too. A token should be between 32 and 256 characters long. You'll need to generate it yourself, for example with pwgen 256 1.
Customize ledger/settings.py, specifically you may be interested in the options starting with LEDGER_ at the end of this file.
Check that everything works at http://localhost:8000/
Enable the production mode in ledger/settings.py. Either run make prod (see the output of make for the optional arguments) or follow these steps: Set DEBUG = False. Generate a new SECRET_KEY, for example with this snippet. Enter your domain and possibly a localhost in ALLOWED_HOSTS. Set STATIC_ROOT, for example '/var/www/ledger' + STATIC_URL and run ./manage.py collectstatic.
Set up a WSGI server (for example Gunicorn): pip install gunicorn gunicorn -w 4 -b 127.0.0.1:1234 ledger.wsgi
Set up a reverse proxy in a HTTP server, for example Nginx, a config file included in examples/ledger.nginx.conf.
Clone the repository and install the dependencies:. Set up the database. SQLite is used by default, it can be changed in ledger/settings.py.
Clone the repository and install the dependencies: git clone https://github.com/vifon/ledger-web cd ledger-web virtualenv .venv . .venv/bin/activate pip install -r requirements.txt
Set up the database. SQLite is used by default, it can be changed in ledger/settings.py. ./manage.py makemigrations ./manage.py migrate
Set the access credentials: ./manage.py createsuperuser ./manage.py runserver Follow the instructions on screen and the enter http://localhost:8000/admin Add a new entry in the Ledger paths table for your user, pointing it to your Ledger file. If you want to use the HTTP API, add an access token too. A token should be between 32 and 256 characters long. You'll need to generate it yourself, for example with pwgen 256 1.
Customize ledger/settings.py, specifically you may be interested in the options starting with LEDGER_ at the end of this file.
Check that everything works at http://localhost:8000/
Enable the production mode in ledger/settings.py. Either run make prod (see the output of make for the optional arguments) or follow these steps: Set DEBUG = False. Generate a new SECRET_KEY, for example with this snippet. Enter your domain and possibly a localhost in ALLOWED_HOSTS. Set STATIC_ROOT, for example '/var/www/ledger' + STATIC_URL and run ./manage.py collectstatic.
Set up a WSGI server (for example Gunicorn): pip install gunicorn gunicorn -w 4 -b 127.0.0.1:1234 ledger.wsgi
Set up a reverse proxy in a HTTP server, for example Nginx, a config file included in examples/ledger.nginx.conf.
Support
The journal view works correctly only if the Ledger journal uses the YYYY-MM-DD or YYYY/MM/DD date format (possibly with DD and MM switched).
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
