I have chosen the latter, but I am open to converting this to "Roundhouse 2.0", if there are convincing arguments for doing so. I had a big discussion with myself on whether I should do this in the current RoundhousE setting, or start over from scratch in a separate context.
Option 2 - Abandon RoundhousE - create a new project Keep external dependencies to a minimal, to make maintaining the project easier going forward. Re-write RoundhousE from scratch using modern. Other suggestions are of course welcome - use the comments! Option 1 - Reboot RoundhousE
#CHUCK NORRIS THUMBS UP CODE#
However, in my opinion, that is difficult, given the current code base. apt-get and other package managers for Linux, and homebrew (or others) for macOS. distributing binaries that are single file and framework independent, so we could make distributions via e.g. net 6, which brings new possibilities for e.g. My experience with maintaining RoundhousE (more or less successfully) for the last nearly three years, is that it's a bit difficult to maintain in its current state.
#CHUCK NORRIS THUMBS UP UPGRADE#
But without active maintainers with knowledge of the Oracle integrations, it's difficult to upgrade Options going forward The challenges are especially related to maintaining some of the lesser used database providers, especially Oracle, which has some issues, but is on an ancient version of the oracle driver. Many people use RoundhousE, but few contribute. Old versions of Microsoft Nuget packages.No automatic push of built artifacts to NuGet and others.AppVeyor used to build, but not actively maintained."Work around" with build.ps1, but could definitely be improved.Originally using an internal chucknorris tool, but not maintained.In addition to this, the style originally used for writing tests, etc, BDD, is unfamiliar to me personally, and I find it difficult to expand and refactor the tool following some of the coding style, especially related to tests. Time passing, though, some of the tools used in the beginning, and some of the external references from that time, makes it difficult to upgrade RoundhousE to current.
RoundhousE has been in development for over 10 years, the work was started by, and he's done an amazing job. It speaks SQL, and it handles versioning of databases. No complicated ORMs, in-app migrations, etc. The simplicity of the tool is its elegance. I'm really, really happy with the tool, and we still have over 5 years of database script history, that, using RoundhousE, can spin up a new database from 0 in a matter of seconds. Almost three years ago, I volunteered to take over the main maintainer responsibility for RoundhousE, as it was our weapon of choice for database migrations at my employer at the time.
0 kommentar(er)
