Extend documentation (fixes #449)

[hartwork]

CC @floari

[floari]

Envs are perfect now, thanks.
But still there should be some words about the cron container:

cron:
image: ${COMPOSE_PROJECT_NAME:-jawanndenn}_jawanndenn
command: ["sh", "-c", "supercronic -sentry-dsn "${JAWANNDENN_SENTRY_DSN}" ~/crontab"]

I personally never used sentry or supersonic, maybe the documentation can explain if this part is needed or how to deploy it in a more general way?

[hartwork]

Envs are perfect now, thanks.

@floari cool!

But still there should be some words about the cron container:

cron: image: ${COMPOSE_PROJECT_NAME:-jawanndenn}_jawanndenn command: ["sh", "-c", "supercronic -sentry-dsn "${JAWANNDENN_SENTRY_DSN}" ~/crontab"]

I personally never used sentry or supersonic, maybe the documentation can explain if this part is needed or how to deploy it in a more general way?

Sentry is completely optional and passing an empty value there should work fine. Sentry is to collect backtraces and to send alerts for server side failures.
Without the cron container, polls that were created to live for say a week will live forever and hence there is a risk of e.g. the database growing too large and for unwanted content to be served for longer. Are you familiar with the general concept of cron and a crontab file?
Please let me know if anything else about the cron container remains unclear.

[hartwork]

@floari PS: Please relaborate on "how to deploy it in a more general way", I'm not sure I get that part, yet.

[floari]

No problems - maybe wrong phrasing from my side. I meant without using some of the tools you are using (sentry, supercron). With sentry optional this leaves us only with the cron. I did some reading on supercron and of course i know a cron ;)
If I dont want to use supercron, maybe we can just setup the crontab file in the container within the docker-compose? I guess the file which needs to run is: prune_expired_polls.py ?

[hartwork]

No problems - maybe wrong phrasing from my side. I meant without using some of the tools you are using (sentry, supercron). With sentry optional this leaves us only with the cron. I did some reading on supercron and of course i know a cron ;) If I dont want to use supercron, maybe we can just setup the crontab file in the container within the docker-compose? I guess the file which needs to run is: prune_expired_polls.py ?

Why would you want to avoid supercronic, what issue with the current setup are you trying to solve? That's the job, yes, see crontab entry

jawanndenn/crontab

Line 2 in a37789b

@hourly python3 -m django prune_expired_polls

[floari]

To be honest I just have no idea how supercron works - and I have to have it installed beforehand right?

Sorry for my stupid questions, I am currently learning the docker stuff ;)

[hartwork]

To be honest I just have no idea how supercron works - and I have to have it installed beforehand right?

No, it's running inside the container. And it should work out of the box.

Sorry for my stupid questions, I am currently learning the docker stuff ;)

No worries.

[hartwork]

@floari PS: Supercronis is installed into the image at

jawanndenn/Dockerfile

Line 14 in a37789b

supercronic@edge-community

[hartwork]

@floari I'll merge this pull request now. Please don't understand that as ending this discussion: We can talk and fix more. Merging now...