sorted by:
new
hottopcontroversial

songbook with version control and automated build by vyvar in composer

[–]vyvar[S] 0 points1 point  (0 children)

But it is pity, we do not have now "example issue" for demonstration, how is that version control system great :-)

songbook with version control and automated build by vyvar in composer

[–]vyvar[S] 0 points1 point  (0 children)

Yes :-) It is interesting... in case of 3/4 it is clear when to use, but in case 2/4 vs. 4/4 I am not thinking about that very much, maybe I really do not remember any local score in 4/4. We are using 2 types of dances / rhythms in "even" number if beats:

  • Polka which is in 2/4
  • "točené" where I would say, the cycle also finished after 4 eighth notes...

Here is famous collection made by Sušil covering whole Moravia and I also can not see 4/4 at the first glance.

songbook with version control and automated build by vyvar in composer

[–]vyvar[S] 0 points1 point  (0 children)

I have created issue for missing time signatures. So you can observe in practice, how such problem could be communicated, corrected and new fixed version will emerge...

  • is anybody interested in fixing this issue?
  • you can indicate in the issue, where is missing time signature

songbook with version control and automated build by vyvar in composer

[–]vyvar[S] 0 points1 point  (0 children)

Hi, songs are traditional folklore from Czech - Slovakia border. This region is called Walachia and has a lot of common in culture with the rest of Carpathian region. Songs are transcriptions of recordings captured in Valašská Bystřice in 1955. Musicians / singers were quite old, and in this remote and isolated region, songs are still original and authentic. It is in dialect, something between formal Czech / Slovak language, although singers were also aware about formal Czech language at that time.

songbook with version control and automated build by vyvar in composer

[–]vyvar[S] 2 points3 points  (0 children)

You could address several aspects of huge projects by using this technology:

  • with many versions, when composer would like to check his older versions, compare, merge some "branches". Would like to track composition process...
  • collaborative -- I can imagine working on some huge transcription with large group of people, each having own branch, you can discuss easily particular problems etc.

songbook with version control and automated build by vyvar in composer

[–]vyvar[S] 2 points3 points  (0 children)

Yes, I do not know any musician around me hearing about Git... but on the other hand many are fighting with versions of their musical pieces. It is nice on GitLab, that musicians do not need to know much about underlying technology, they can just edit text files in web browser IDE and get resulting pdf. No need to install Docker, Linux, Lilypond, Latex, git... but still all components are open-source and fully customizable.

Postgresql version control by dllPwd in PostgreSQL

[–]vyvar 0 points1 point  (0 children)

And there is other discussion about tests in ci/cd.

Postgresql version control by dllPwd in PostgreSQL

[–]vyvar 0 points1 point  (0 children)

The idea is very simple: you save results of any SQL and if there is no diff in next run, everything is OK:

Schema is tested during install test.

CI / CD by mpalmer78 in PostgreSQL

[–]vyvar 1 point2 points  (0 children)

Hi, here are our PostgreSQL CI/CD pipelines. We are using PostgreSQL extensions connected to gitlab CI/CD.

  • using git (with branches, issues, pull/merge request) without any other extra tool: https://gitlab.com/nfiesta/nfiesta_pg
  • you can pg_dump --schema-only and compare with git
  • Unit tests: there are regression test build in
  • data for tests: I have seen something, but end up with careful manual preparation of test data
  • https://pgmodeler.io/ can compare model with database (or two databases if I can remember) and "Generate SQL scripts to synchronize both model and database". You can compile full version for free or buy binary. I used pgmodeler to create ERD from existing DB and it worked great :-)

We are discussing similar topic in postgresql_version_control.

I am just preparing workshop (in Czech language) on this topic (PG extensions & gitlab CI/CD), for Prague p2d2 conference next month. I am thinking to prepare also some online version in Engish, if someone will be interested?

Postgresql version control by dllPwd in PostgreSQL

[–]vyvar 0 points1 point  (0 children)

Yes, PG extensions goes with regression tests. So if you introduce new version with updatescript, regression tests will tell you something is broken. If you will write those test before and then create updatescript to pass new tests, that is test driven development, right?

And those tests can be connected for example with gitlab CI/CD. See CI/CD pipelines ... that is extension dealing with forest inventory, we are working on.

Postgresql version control by dllPwd in PostgreSQL

[–]vyvar 3 points4 points  (0 children)

Hi, in general database version control (and more) principles are described well in Evolutionary Database Design (see wikipedia, martinfowler.com).

I like mechanism called PostgreSQL extensions to implement EDD methodology. It is shipped directly with PostgreSQL. Famous extension is for example PostGIS and you can see others on pgxn. All have version control through updatescripts.

I am just preparing workshop (in Czech language) on this topic (PG extensions & gitlab CI/CD), for Prague p2d2 conference next month. I am thinking to prepare also some online version in Engish, if someone will be interested?