-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Download cachet to /usr/src #161
Comments
I am wondering if we even need |
The volume has been removed in master per #165 . |
Volume is used to store |
Thanks @csandanov I forgot about that piece. Going to try to get some tests in place and find a better way to detect that a instance is already configured. |
I guess having a whole volume only for this file is not reasonable. My suggestion would be to check if session table exists. Because that's the first table it tries to create and fails when tries to initialize with already initialized database. |
#166 addressed this issue and a few other things |
Currently, cachet being downloaded to the volume directory and it works ok as long as you specify only container path in the volume (
--volume=/var/www
). However, it's not obvious that it won't work if you specify a host path (e.g./var/www/html:/var/www
and some tools like kubernetes do not support volumes without specifying the host path.I suggest to download cachet to
/usr/src
(like wordpress guys do) and move it to /var/www in entrypoint if there's no codebase already.The text was updated successfully, but these errors were encountered: