Age | Commit message (Collapse) | Author | Files | Lines |
|
We should really regenerate the configs, run migrations and hooks during
each container startup. Otherwise you really can't update anything at
all.
The only thing that we do not do multiple times is adding the admin
user, but the add_user method already checks for that and simply
displayed an error. Hiding that error is probably not worth the effort
so we just add a quick explanatory comment before the potential error.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
The following error was shown during initial startup of the container
and the database was obviously not initialized because of this. I'm not
sure why it happens, but setting the database name in the config (in
addition to the name in the PDO connection string) fixes the problem.
> Database error: A Database Error Occurred
>
> Error Number: 42000/1102
> Incorrect database name ''
> SHOW TABLES FROM ``
> Filename: libraries/Migration.php
> Line Number: 167
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
|
|
Fixes #28
SQLSTATE[HY000] [2054] The server requested authentication method unknown to the client
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
To send mails in the docker container we need to configure php to use
a smtp client and provide smtp credentials to the docker container
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
|
|
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
This is necessary for future use of docker-compose
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
|