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

Saving a backup of the crontab config from the i18n-dev server #35436

Merged
merged 1 commit into from Jun 23, 2020

Conversation

daynew
Copy link
Member

@daynew daynew commented Jun 23, 2020

We are using crontab on the one-off i18n-dev server. If this server dies, then we will lose the configuration. This PR addresses that by temporarily backing it up into the code-dot-org git repo.

Links

Testing story

  • Manually tested the steps in the documentation

Reviewer Checklist:

  • Tests provide adequate coverage
  • Code is well-commented
  • New features are translatable or updates will not break translations
  • Relevant documentation has been added or updated
  • User impact is well-understood and desirable
  • Pull Request is labeled appropriately
  • Follow-up work items (including potential tech debt) are tracked and linked

@daynew daynew force-pushed the fnd-894-add-i18n-dev-server-cron-config branch from 8bba3b6 to e370bf2 Compare June 23, 2020 05:32
Copy link
Contributor

@Hamms Hamms left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one nit, otherwise LGTM!

Comment on lines 1 to 24
# Edit this file to introduce tasks to be run by cron.
#
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
# and what command to run for the task
#
# To define the time you can provide concrete values for
# minute (m), hour (h), day of month (dom), month (mon),
# and day of week (dow) or use '*' in these fields (for 'any').#
# Notice that tasks will be started based on the cron's system
# daemon's notion of time and timezones.
#
# Output of the crontab jobs (including errors) is sent through
# email to the user the crontab file belongs to (unless redirected).
#
# For example, you can run a backup of all your user accounts
# at 5 a.m every week with:
# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
#
# For more information see the manual pages of crontab(5) and cron(8)
#
# m h dom mon dow command
#
# ---
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this standard cron header can probably go away

@daynew daynew force-pushed the fnd-894-add-i18n-dev-server-cron-config branch from e370bf2 to aadcfdb Compare June 23, 2020 23:38
@daynew daynew merged commit 4ce27e1 into staging Jun 23, 2020
@daynew daynew deleted the fnd-894-add-i18n-dev-server-cron-config branch June 23, 2020 23:39
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

Successfully merging this pull request may close these issues.

None yet

2 participants