Skip to content
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

Closed
csandanov opened this issue Mar 7, 2017 · 6 comments
Closed

Download cachet to /usr/src #161

csandanov opened this issue Mar 7, 2017 · 6 comments

Comments

@csandanov
Copy link

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.

@djdefi
Copy link
Contributor

djdefi commented Mar 8, 2017

I am wondering if we even need VOLUME /var/www in the Dockerfile anymore. It was added to address an issue (#55) with older versions where there was a separate nginx container.

djdefi added a commit that referenced this issue Mar 9, 2017
@djdefi
Copy link
Contributor

djdefi commented Mar 9, 2017

The volume has been removed in master per #165 .

@djdefi djdefi closed this as completed Mar 9, 2017
@csandanov
Copy link
Author

Volume is used to store .cachet-installed file so if you restart container it won't try to initialize again.

@djdefi djdefi reopened this Mar 9, 2017
@djdefi
Copy link
Contributor

djdefi commented Mar 9, 2017

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.

@csandanov
Copy link
Author

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.

@djdefi
Copy link
Contributor

djdefi commented Mar 14, 2017

#166 addressed this issue and a few other things

@djdefi djdefi closed this as completed Mar 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants