Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

8
  • 2
    "Production database content does not belong on a publicly accessible service." <- it's perfectly possible to have private repos on Github, just like lots of companies have their private source code on Github. Commented Jun 30, 2021 at 7:17
  • 1
    Also be aware that as much as I value software, the data in a database is often much more valuable and must be protected much more stringently. Think of password hashes and the legal requirements around protecting personal data. Commented Jun 30, 2021 at 7:30
  • 1
    @PhilipKendall even in the companies that do, source code likely sits in an entirely different classification to the prod database because the latter almost certainly contains PII and the former shouldn't. If the OP's assuming "we put other things on GitHub so I can put this there", that can be a problem. Commented Jun 30, 2021 at 7:31
  • 2
    "Your assumptions about saving time by only storing the daily updates in git do not hold, database files are binary, and the changes cannot be expressed as textual diffs." It's worse than that. Git doesn't store textual diffs, even for source code files - it always stores the entire contents of every version of every file. Commented Jun 30, 2021 at 16:00
  • 1
    @RossPatterson: it is a little bit more complicated. Commented Jul 1, 2021 at 12:19