* Trying to move horizontal rules into separate function
* Delete install_dir if exists already, after confirmation
* Add confirm function to take user conformations
* Resolve warnings on read command without -r option
* Use temporary directory for downloaded templates
* Fix inverted calls to confirm
* nginx template doesn't use global variables now
* docker compose template doesn't depend on global vars now
* Fix port checking for CentOS
* Fix encryption.env to not use global variables
* Fix mongo-init to not use global variables
* Fix docker.env file to not use any global variables
* Fix letsencrypt script to not use any global variables
* Set mongo_database in the docker-compose file
Spotted this after global variables were reduced. The `mongo_database`
was not being used anywhere.
* Move password generation into a function
* Attempt to add watchtower
* Fix port checking in install script for CentOS
* Don't offer to delete install dir if it already exists
* Remove vagrant source for templates (it's a dev-time thing only)
Adding the following files in order to create the AWS AMI
* boot.sh
* base-install.sh
* configure-ssl.sh file to run to modify app.conf file of nginx and to run init-letsencrypt.sh which generate SSL certificate.
Co-authored-by: Shrikant Sharat Kandula <shrikant@appsmith.com>
Co-authored-by: Arpit Mohan <arpit@appsmith.com>
* Getting the script to work on Mac OS X Bash Version 3
* Correcting the nginx template configuration and Dockerfile for the appsmith-editor. Now any replaced environment variables will be replaced when the Nginx Docker container restarts.
* Encrypting the password stored in AuthenticationDTO for every db.
* Adding comment to the properties file to denote that adding encryption salt and password are mandatory to the server coming up.
* Added the encryption salt and password to server.yml to allow the github actions to succeed.
* Adding database migration to encrypt the existing passwords for authentication object (used for storing db connection username/password)
Changes to the installation script install.sh:
1. Instead of overwriting the existing encryption password or salt, giving the user an option to conserve the previous encryption credentials to ensure that the developer users do not lose access to their database configurations (passwords).
2. Added another file for writing encryption credentials (encryption.env) to ensure that we dont delete the encryption password and salt by mistake.
