Why is this a PoC?

[alexandernst]

I have been using this "PoC" for quite some time now and it always migrates successfully any data I throw at it. For granted, it doesn't migrate any configurations in the $OLD folder, nor does it handle db/username/passwords other than postgres (but there are workarounds for this!), but aside from that the migration process itself works flawlessly. So, ¿why is this considered a PoC?

Am I just not hitting the "hidden bugs"? Or is this just like Google's "beta" label that they slapped right below Gmail's logo for 10 years? 😂

[tianon]

You've listed a lot of good reasons why this is a PoC, but this is basically something I slapped together with extremely minimal effort back in 2016, and haven't really touched/maintained since beyond version bumps / buildability fixes. It was never intended to be more than simply an example for others to build a more complete solution to the problem, which is why it doesn't support quite a few things that would be needed for this to be a real solution (like migrating config, usernames/passwords, etc).

For example, I never even updated it to take advantage of docker-library/postgres#496 so that it wouldn't have to reimplement so much of that upstream script (and that would probably even fix some bugs, or at least make the workarounds easier).