Installation script defaults

[sdc50]

I'm just finishing up the installation scripts (Linux, Mac, and Windows). Developing things cross platform has made me think about current defaults and whether or not they make sense. Before I commit these scripts and wash my hands, I'm interested in some input from the community.

The primary issue is the location of TETHYS_HOME, or the main directory where everything (e.g. source code, database, Miniconda) is put. In the past the instructions said to make this directory at /usr/lib/tethys. This requires sudo access and has not obvious analogous directories on other platforms. I propose that the default TETHYS_HOME directory now be ~/tethys (or C:\%HOMEPATH%\tethys on Windows). This makes it consistent on all platforms and also makes it so the install scripts can be run without sudo (which could be a major benefit for some organizations). The downside is that (unless we do some fancy shell scripting) the script can't install tethys in a location that requires root access (e.g. /usr/lib/tethys). That seems minor and there are work arounds. If it becomes a major obstacle then we could enhance the install scripts to handle that case.

Other default settings that I have in the install scripts that I'd like some feedback on are the BRANCH (the branch of the repository to checkout). Currently the default is dev, but I probably should change that to master. Thoughts?

The default port for the local Tethys database is set to 5436 so it doesn't conflict with the docker postgis port if it is installed.

Also, the script automatically creates a Tethys Portal super user to be able to login to the web portal. The default credentials are Username: admin, Password: pass. 

Default values for other parameters needed in the installation process are consistent with how they have been, and I don't see any compelling reason to change them.

Note that any of these parameters can be changed with command line options when running the install script, but I would appreciate some feedback particularly on the TETHYS_HOME and BRANCH variables.

[swainn]

First things first, WAHOO! This is going to be big! Here are my thoughts on your thoughts:

TETHYS_HOME: I like your suggestion for a default home path. As you have noted, the original TETHYS_HOME directory was somewhat arbitrary (based on CKAN actually). Is the home path an argument to the install script? Can I override the default?

BRANCH: I think the default should be the master branch so that it pulls the latest release.

Tethys database port = 5436: That should be ok. I don't think that will conflict with anything else. Let's just be sure it is documented.

Default Tethys superuser: works for me. Again as long as it is documented, we're golden. Even better if we can configure this through script args. We probably need to have an extra emphasis in the production docs to change/disable this user so it isn't a security vulnerability.

[Dan Ames]

Anything to simplify installation is good by me. So removing the requirement for sudo access in the TETHYS_HOME folder is a good call. Also, pulling the master branch instead of dev makes a lot of sense. I haven't got an opinion on the port. The default superuser is only a problem if people don't change it and then hackers find it. But I'm not sure how else to handle it...

--
You received this message because you are subscribed to the Google Groups "Tethys Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tethysplatfor...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tethysplatform/3e673557-d841-43b6-975d-19cdc8f8adbb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.