Installer script

[chad-ermacora]

Interactive install script for darkstar on Debian, Ubuntu & Raspbian. Only need to enter a username, password and IP to get up and running. The user is used to start the servers and access the SQL database.

[ShelbyZ]

There are some potential problems with what this script will offer:

• We are not providing the ability for a user that already has this installed to update branches or code via a 'friendly' option
• How do we plan on handling dependency changes
• How do we plan on handling SQL changes

Feels like there should be an option for updating the server from GIT and figuring out how those changes would be applied. Code would be easy, SQL would require usage of migration scripts.

[chad-ermacora]

There are some potential problems with what this script will offer:

• We are not providing the ability for a user that already has this installed to update branches or code via a 'friendly' option
• How do we plan on handling dependency changes
• How do we plan on handling SQL changes

Feels like there should be an option for updating the server from GIT and figuring out how those changes would be applied. Code would be easy, SQL would require usage of migration scripts.

I was told to not allow upgrades, due to SQL change issues that are currently not automated. So if install is chosen but it detects it has been built already, it exits the script. Configurations, such as Zone IP and the 3 main configuration files can still be accessed after setup by running the script and choosing edit config option.

Dependency changes will have to be updated in the script by adding or removing it in one of the 2 APT_GET_INSTALL variables near the top. If they are Distro specific, they can be added in the section shown below. Adding other distro's should be relatively easy, as you add in an extra else if statement checking for the lowercase name of the distro.

if [ "${OS}" == "debian" ] || [ "${OS}" == "raspbian" ]; then printf "\nRunning Debian or Raspbian Install\n" apt-get -y install libmariadb-dev-compat ./configure CXXFLAGS=" -pthread" || exit else printf "\nRunning Default Install\n" ./configure || exit fi

If we did have a SQL script in the main repository that would update SQL entries based on whatever has changed, I could link directly to it in the script and download it at runtime. I was thinking as long as the SQL script is updated before pushing to Stable, upgrading between stable releases should be a viable option.

[TeoTwawki]

as long as they can git pull after they can get code changes and then rebuild for themselves.

we can't really get a good way to automate sql changes at this time.

[chad-ermacora]

-Added fix to work on Ubuntu desktop (I was testing on server, which enables required repository by default but desktop does not) -Misc text output improvements.