1 TMUX Screens
To create the EXODUS maintenance/programming environment
SCREEN NAME STANDARD PATH PURPOSE #ex1_root - /root - general usage #exodus - /root/exodus - #exodus src - /root/exodus/exodus/libexodus/exodus - LibExodus is the core EXODUS library source files (emulating AREV CRUD) #exo cli - /root/exodus/cli/src - Core EXODUS program which can be executed from bash (clearfile, edir, edic, compile) #service - /root/exodus/service - Default working environment for EXODUS only service, including EXODUS core www and data directories. Also used to keep NEOSYS database installation scripts. #ser src - /root/exodus/service/src - #neosys - /root/neosys - ./doall #neo src - /root/neosys/src - #hosts - /root/hosts - #test src - /root/exodus/test/src - #t10 - ~/ - #t11 - ~/ - #t12 - ~/ -
1.1 Object Code/Libraries
LIVE and TEST processes use different sets of object code. TEST processes use libraries in ~/lib/, whereas LIVE processes use object code in ~/neo/lib
This means development & testing can be done stress free on TEST database, as opposed to testing on production databases.
When compiling using edic, the TEST object code is updated if the compilation is successful. (~/lib) In order to apply a tested patch to LIVE see Update LIVE programs.
Dictionaries, the files used to describe the fields of a file's record. Unlike in AREV, there is a copy of all dictionaries in each pgsql database (In AREV, updating a dictionary would affect all the databases).
The TEST process for all database use the same object code stored in /root/lib, whereas all LIVE process use the object code in /root/neo/.
Connect into postgres shell:
sudo -u postgres psql
List databases once in postgres shell:
Delete a database:
sudo -u postgres dropdb <dbcode>
Screen 6: ./doall script contains all the necessary information(codes) to setup an installation. It includes scripts to backup, restore, create an Apache site, create/start/stop/status a service, import an AREV database into postgres and more.
- Does a backup & restore of a LIVE database into the corresponding TEST database.
- Backup <dbcode>.sql file is written to /root/backups/sql; which is rsynced to nl19:/backups/current/exodus/
- Unlike AREV, postgres can perform a "backup" of a database whilst the system is in use.