Video 1: Install and Start Video
LedgLive Video 1: Starting with LedgLive sample database
LedgLive Video 1: Demonstration of getting LedgLive to work from scratch with sample database. Unlike with Videos 2 ,3 and 4, drop down windows and right click windows are visible in this video by recording a remote desktop connection.
Videos 2, 3 and 4 show LedgLive working practically.
1. Starting with LedgLive sample database
Visit https://ledglive.io, click on ‘Introduction’, ‘Downloads’, ‘x64 Windows download’. Right click on ‘ledglive-window.zip’ file, ‘Extract All’, Extract.
Right click in directory, click on ‘Open in Windows Terminal’. Open up a browser tab in ‘http://localhost:8652’ or in ‘https://localhost:8653’. The tools view in the browser on the right is opened or closed with F12 or ‘Ctrl + Shift + I’. It is not part of LedgLive and should not be used in practice. The ‘Local Storage’ view in the ‘Application’ view is shown. Start up LedgLive with command in terminal, ‘ledglive sr -v’. Accept allow through firewall, if asked.
LedgLive requires a default account for ‘Row+’ (or journal add) is selected and this is stored in browser local storage. Click on ‘Reload’ to show LedgLive. Note that ‘Row+’ is inactive. Select any account (with Enter TWICE) to choose a default account used by ‘Row+’. Note local storage has been updated with a default entity and account. You now don’t need this step again, unless local storage is absent or is inconsistent with the database.
We now add ‘Date Begin’, ‘Date End’ and ‘Date New’ to local storage by clicking on them. First change ‘Date Begin’ to to 1 September 2021 in order to view ledger and journal entries for the sample opaltrader ledglive_opaltrader.db database. Observe entries going into local storage.
From the point of view of Opal Trader, we will now ‘corrupt’ local storage by changing the default entity and account, to an account that does not exist in Opal Trader. Change local storage as shown and refresh to get back to same report as when local storage was empty. Adjustment is same as when starting off to allow Row+ (add journal entry) to work. This scheme may change in the future, such as using the database to store such information
If there is no .env file in the directory then various defaults, such as the database used, are the same as in the .env.opaltrader file. To alter a default, copy over .env.opaltrader to .env and make changes. For example change DB_SQLITE variable to use a different database or override with command line.