You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When going through the README instructions, we ran into some file permission errors because containers couldn't write to the data directory. This is likely because our uid on our system was 1000, while the one specified in the .env file as DOCKER_USER was 1100. We actually just ended up making the data and data/elasticsearch directories world-writable, but a more secure fix would probably involve adding a section to the README advising the user to set DOCKER_USER to a value appropriate for their system. Since that would involve editing the version-controlled .env file, however, it might make sense to rename .env to .env.sample and have the user explicitly create their own .env file.
The text was updated successfully, but these errors were encountered:
When going through the README instructions, we ran into some file permission errors because containers couldn't write to the
data
directory. This is likely because our uid on our system was1000
, while the one specified in the.env
file asDOCKER_USER
was 1100. We actually just ended up making thedata
anddata/elasticsearch
directories world-writable, but a more secure fix would probably involve adding a section to the README advising the user to setDOCKER_USER
to a value appropriate for their system. Since that would involve editing the version-controlled.env
file, however, it might make sense to rename.env
to.env.sample
and have the user explicitly create their own.env
file.The text was updated successfully, but these errors were encountered: