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

Persist data on docker-volume #12

Open
copolycube opened this issue Jun 24, 2021 · 3 comments
Open

Persist data on docker-volume #12

copolycube opened this issue Jun 24, 2021 · 3 comments

Comments

@copolycube
Copy link

Hello @GregYankovoy , I am using your bundle of goaccess and it was a great way to start using this cool project, thanks a lot !

As suggested in the #11 I am using it in docker-compose.

I was wondering how it would be possible to add a docker named volume so that we keep persist the data when restarting, and how that would integrate with your bundle ?

Thanks in advance for your help

@copolycube copolycube changed the title Persist data Persist data on docker-volume Jun 24, 2021
@GregYankovoy
Copy link
Owner

Hi @copolycube . This has come up before and I believe goaccess has some built in features for storage persistence. Last time this came up, there was no solution available:
#2

However, reading through the nested goaccess issue thread again, looks like 1.4 may have created some less complex disk persistence:
allinurl/goaccess#708

A quick google search returns this informative article:
https://arnaudr.io/2020/08/10/goaccess-14-a-detailed-tutorial/

Seems like --persist and --restore may be helpful for the use case you are describing. Are you able to do any testing with those flags within the container? If we can verify these give us the desired behavior, I can add persistence as an optional environment variable on the container.

@copolycube
Copy link
Author

Hello @GregYankovoy ,
I'm not sure how I could test this with your image :-/

@copolycube
Copy link
Author

Hello @GregYankovoy
I submitted the #16 that contains this feature (among others).

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