* Creating SSL certificates now works
* Work with single domain
* Move certificate generation into install script
* Download templates from master branch, not release
* 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)
* Adds the `APPSMITH_MAIL_ENABLED` flag on client
* Shows warning if email service not configured for inviting users in an org
* Shows warning if email service not configured for password reset
* Exit if running with sudo on macOS
* Fix port checking failing if 8080 is occupied
Also, ports on Linux (especially Ubuntu) are reported as
`:80`, and macOS reports as `.80`, so we have to handle
them both.
* Move goodbye message to a function
* Fix installation fail when path contains space
* Fix script exits after `up` if already running
If there's a project by the name `appsmith` already running
in the docker namespace, then the command `docker-compose up`
is exiting with a non-zero status. This causes the script to
exit because it looks like an error.
* Timeout display now shows a decreasing timer in the message
* Fix docker service not being started correctly on Linux
* Show custom domain in final message, if available
Fixes#318
The issue occurred because code assumes that if docker is already installed, docker-compose would have been installed too. This PR is an attempt to fix it.
Add a default help menu with
* Report a Github issues link
* Documentation link
* Github discussions link
* Intercom link support
* App version id support
* Enforcing non-empty credentials for Mongo when we spin up a Mongo container during installation
* Adding a check for server startup before completing the installation
* Added information to setup domain
* Fixed incorrect var reference
* Updated documentation message
* Updated env template
* updated template
* removed debug echo
* Updated Script
* Updated Text
* Removed option to connect to external mongo for fresh installs
Exit script of docker desktop is not installed
* Updated docker installation explanation
* added a question to skip custom domain if user is installing locally
* Inverted script question and
* Removed question to determine local installation
* Updated Popup CTA to Modal
Updated query templates to contain bindings
Added a message to display on API / Query errors
* updated styles for evaluated value
updated styles for auto complete
* added spaces to questions
* grouped data tree functions together in autocomplete
* Updated autocomplete styles
* Updated property pane styles to become more dense
* Fixed lightning menu styling
* fixed tests
* Fixed Cypress test
Co-authored-by: Nikhil Nandagopal <nikhil@appsmith.com>
* Added information to setup domain
* Fixed incorrect var reference
* Updated documentation message
* Updated env template
* updated template
* removed debug echo
* Updated Script
* Updated Text
* Removed option to connect to external mongo for fresh installs
Exit script of docker desktop is not installed
* Updated docker installation explanation
* added a question to skip custom domain if user is installing locally
* Inverted script question and
* Removed question to determine local installation
* Updated Popup CTA to Modal
Updated query templates to contain bindings
Added a message to display on API / Query errors
* updated styles for evaluated value
updated styles for auto complete
* added spaces to questions
Co-authored-by: Nikhil Nandagopal <nikhil@appsmith.com>
* Modifying the docker-compose templates to only expose required ports from Nginx
* Also, adding function to check if the required ports are open & available for use by Appsmith
* Added information to setup domain
* Fixed incorrect var reference
* Updated documentation message
* Updated env template
* updated template
* removed debug echo
* Updated Script
* Updated Text
* Removed option to connect to external mongo for fresh installs
Exit script of docker desktop is not installed
* Updated docker installation explanation
* added a question to skip custom domain if user is installing locally
* Inverted script question and
* Removed question to determine local installation
Co-authored-by: Nikhil Nandagopal <nikhil@appsmith.com>
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.
The MAIL_FROM & REPLY_TO addresses default to appsmith@localhost. This should be changed in the generated docker.env file during deployment to actual values.
Most email providers will not send emails unless they originate from a valid sender ID.
* 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.
TODO: Need to add checks for MacOS machines as well.
Co-authored-by: Nikhil Nandagopal <nikhil@appsmith.com>
Co-authored-by: Shrikant Sharat Kandula <shrikant@appsmith.com>