Skip to content

Commit

Permalink
Remove the ability to start with internal database
Browse files Browse the repository at this point in the history
  • Loading branch information
fredclausen committed Nov 2, 2023
1 parent 970915b commit 3825241
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 0 deletions.
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,8 @@ With regards to settings - where one exists, you should use an environment varia

**NOTE**: The Docker command provided in this quick start is given as an example and parameters should be adjusted to suit your needs.

**_NOTE:_**: This provided configuration doesn't work. You have to use the external database configuration. This is a known issue, and the config is being left in the README for reference and consideration as we decide what to do about this.

An example `docker-compose.yml` file is as follows:

```yaml
Expand Down
2 changes: 2 additions & 0 deletions rootfs/etc/s6-overlay/scripts/01-sanitycheck
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,8 @@ fi
# Make sure database hostname/password have been set OK
if [ -z "${MYSQLHOSTNAME}" ]; then
echo -e "${LIGHTBLUE}INFO: MYSQLHOSTNAME not set, using local database${NOCOLOR}"
echo -e "${LIGHTRED}ERROR: local data base is not supported. Please set up an external mariadb instance for use.${NOCOLOR}"
EXITCODE=1
else
if [ -z "${MYSQLPASSWORD}" ]; then
echo -e "${LIGHTRED}ERROR: MYSQLHOSTNAME set, however MYSQLPASSWORD not set${NOCOLOR}"
Expand Down

0 comments on commit 3825241

Please sign in to comment.