281d5f6ebf
This commit introduces several significant changes to improve the security and configuration management of the application.
Encryption of Sensitive Data: We've introduced encryption for sensitive data such as database passwords. This is done using the Blowfish algorithm. The encryption and decryption methods are added to the Utilities module. The encryption is applied when the user enters their database password during the first run setup. The encrypted password is then stored in the .env file. When the application needs to use the password, it is decrypted using the key that was generated during encryption.
Switch from YAML to .env for Configuration Storage: The application now uses a .env file for storing configuration data instead of a YAML file. This change was made to take advantage of the .env file's ability to store environment variables, which can be easily accessed by the application. The .env file stores the database username, encrypted password, encryption key, and database name.
First Run Setup Changes: The FirstRunInit class has been updated to ask the user for their database details, encrypt the password, and store these details in the .env file. It also checks if any of the necessary details are missing and runs the first run setup if they are.
Database Connection Testing: The DatabaseManager class now decrypts the password before using it to test the database connection. It also checks if the password or key are nil before attempting to decrypt the password.
Logging: A new LoggMan class has been added to handle logging. This class provides a simple method for logging messages, which can be used throughout the application to log errors or other important information.
Bug Fixes and Error Handling: Several bugs were fixed and error handling was improved. For example, a bug that caused the application to crash if the .env file was missing has been fixed. Also, the application now checks if the .env file exists and creates it if it doesn't.
These changes significantly improve the security, reliability, and usability of the application.
62 lines
1.2 KiB
Plaintext
62 lines
1.2 KiB
Plaintext
*.gem
|
|
*.rbc
|
|
/.config
|
|
/coverage/
|
|
/InstalledFiles
|
|
/pkg/
|
|
/spec/reports/
|
|
/spec/examples.txt
|
|
/test/tmp/
|
|
/test/version_tmp/
|
|
/tmp/
|
|
/.vscode/
|
|
/.rubocop.yml
|
|
.env
|
|
|
|
# Used by dotenv library to load environment variables.
|
|
# .env
|
|
|
|
# Ignore Byebug command history file.
|
|
.byebug_history
|
|
|
|
## Specific to RubyMotion:
|
|
.dat*
|
|
.repl_history
|
|
build/
|
|
*.bridgesupport
|
|
build-iPhoneOS/
|
|
build-iPhoneSimulator/
|
|
|
|
## Specific to RubyMotion (use of CocoaPods):
|
|
#
|
|
# We recommend against adding the Pods directory to your .gitignore. However
|
|
# you should judge for yourself, the pros and cons are mentioned at:
|
|
# https://guides.cocoapods.org/using/using-cocoapods.html#should-i-check-the-pods-directory-into-source-control
|
|
#
|
|
# vendor/Pods/
|
|
|
|
## Documentation cache and generated files:
|
|
/.yardoc/
|
|
/_yardoc/
|
|
/doc/
|
|
/rdoc/
|
|
|
|
## Environment normalization:
|
|
/.bundle/
|
|
/vendor/bundle
|
|
/lib/bundler/man/
|
|
|
|
# for a library or gem, you might want to ignore these files since the code is
|
|
# intended to run in multiple environments; otherwise, check them in:
|
|
# Gemfile.lock
|
|
# .ruby-version
|
|
# .ruby-gemset
|
|
|
|
# unless supporting rvm < 1.11.0 or doing something fancy, ignore this:
|
|
.rvmrc
|
|
|
|
# Used by RuboCop. Remote config files pulled in from inherit_from directive.
|
|
# .rubocop-https?--*
|
|
bin/config.yml
|
|
lib/netrave.log
|