Scrayos UG (haftungsbeschränkt)

Decision at Scrayos UG (haftungsbeschränkt) about Jenkins, GitLab Pages, GitLab, GitLab CI

Avatar of Scrayos
CEO at Scrayos UG (haftungsbeschränkt) ·

We use GitLab CI because of the great native integration as a part of the GitLab framework and the linting-capabilities it offers. The visualization of complex pipelines and the embedding within the project overview made Gitlab CI even more convenient. We use it for all projects, all deployments and as a part of GitLab Pages.

While we initially used the Shell-executor, we quickly switched to the Docker-executor and use it exclusively now.

We formerly used Jenkins but preferred to handle everything within GitLab . Aside from the unification of our infrastructure another motivation was the "configuration-in-file"-approach, that Gitlab CI offered, while Jenkins support of this concept was very limited and users had to resort to using the webinterface. Since the file is included within the repository, it is also version controlled, which was a huge plus for us.

6 upvotes·13.6K views

Decision at Scrayos UG (haftungsbeschränkt) about Checkstyle

Avatar of Scrayos
CEO at Scrayos UG (haftungsbeschränkt) ·

We use Checkstyle for all of our Java projects to perform the linting. The setup was very easy and there are amazing integrations into all IDEs. What also came in very handy was that we could start off with just a basic set of rules and tighten the linting-rules step-by-step, continously improving the readability and uniformity of our codebase.

6 upvotes·977 views

Decision at Scrayos UG (haftungsbeschränkt) about Vert.x

Avatar of Scrayos
CEO at Scrayos UG (haftungsbeschränkt) ·

We use Vert.x for our internal and external OpenAPI v3 REST-API that handles our own queries for the App, Launcher and Website aswell as external queries, authenticated through OAuth2.

Vert.x has proven to be a valuable asset and framework during the development of our application and the numberless "addon"-packages (OAuth2, OpenAPI, Redis Cache, SQL, etc.) allow us to test out new stuff very fast.

5 upvotes·1.1K views

Decision at Scrayos UG (haftungsbeschränkt) about Sentry, GitLab, PostgreSQL, MariaDB

Avatar of Scrayos
CEO at Scrayos UG (haftungsbeschränkt) ·

We primarily use MariaDB but use PostgreSQL as a part of GitLab , Sentry and @Nextcloud , which (initially) forced us to use it anyways. While this isn't much of a decision – because we didn't have one (ha ha) – we learned to love the perks and advantages of PostgreSQL anyways. PostgreSQLs extension system makes it even more flexible than a lot of the other SQL-based DBs (that only offer stored procedures) and the additional JOIN options, the enhanced role management and the different authentication options came in really handy, when doing manual maintenance on the databases.

4 upvotes·18.8K views

Decision at Scrayos UG (haftungsbeschränkt) about GitLab, Sonatype Nexus

Avatar of Scrayos
CEO at Scrayos UG (haftungsbeschränkt) ·

We use Sonatype Nexus to store our closed-source java libraries to simplify our deployment and dependency-management. While there are many alternatives, most of them are expensive ( GitLab Enterprise ), monilithic ( @Artifactory ) or only offer SaaS-licences. We preferred the on-premise approach of Nexus and therefore decided to use it.

We exclusively use the Maven-capabilities and are glad that the modular design of Nexus allows us to run it very lightweight.

4 upvotes·2.5K views

Decision at Scrayos UG (haftungsbeschränkt) about OVH, DigitalOcean, Hetzner Online AG

Avatar of Scrayos
CEO at Scrayos UG (haftungsbeschränkt) ·

We use Hetzner Online AG since the inception of our business, because of the great prices, marvelous support and great interface (especially the new cloud interface). Other options that we tested are DigitalOcean (was more expensive than the new hetzner cloud and didn't offer "huge" dedicated servers), @Vultr (about the same issue as with DigitalOcean , although the prices were better), OVH (Prices, old interface, no "tiny" packages and [at least back at the day] only monthly payment) and Living Bots (Only dedicated servers, too expensive for our needs).

Hetzner offered the best spectrum of servers and has great prices and REALLY great prices in the server auctions.

3 upvotes·3.6K views

Decision at Scrayos UG (haftungsbeschränkt) about JaCoCo

Avatar of Scrayos
CEO at Scrayos UG (haftungsbeschränkt) ·

We use JaCoCo because it enables us to statically find missing test opportunities and improve our Test-Coverage, alongside PITest. While PITest performs mutation testing to dynamically and heuristically find missing test cases, JaCoCo finds lines of code that are not covered by the tests until now.

Both coverage tests are equally important for us and so JaCoCo has become an essential part of our build pipeline.

3 upvotes·572 views

Decision at Scrayos UG (haftungsbeschränkt) about Flyway

Avatar of Scrayos
CEO at Scrayos UG (haftungsbeschränkt) ·

We use Flyway because we're convinced, that database schemas (DDL) should be within our version control system. Code and database belong together and Flyway is an easy and powerful way to achieve that goal. The API is easy to use and even though a commercial licence is offered, it is by no means mandatory, which was an important criterion for us.

We also wanted to integrate the migration directly into the code as we run in a serverless environment, where manual migrations are troublesome and the code itself essentially needs to migrate the database, based on its own findings. Flyway offers this capability and we didn't find any other solution, that was as lightweight while still being powerful and flexible.

2 upvotes·2.8K views

Decision at Scrayos UG (haftungsbeschränkt) about Netty

Avatar of Scrayos
CEO at Scrayos UG (haftungsbeschränkt) ·

We use Netty because it is THE defacto-standard for asynchronous network communication in Java and it excels at the flexible pipeline design and the great thread architecture.

We use Netty for the communication between our servers (Spigot), servers and proxies (Spigot and BungeeCord) aswell as proxies und our global overseer-instance. Finally we also use it for the java-side of our website-overseer-communication.

2 upvotes·984 views

Decision at Scrayos UG (haftungsbeschränkt) about Nextcloud, Wekan, Trello, Google Drive

Avatar of Scrayos
CEO at Scrayos UG (haftungsbeschränkt) ·

We use Nextcloud for company-file-management, personal work-documents and for collaborative work (through collabora), organize our #TODOs, that are not covered by the Bugtracker. Existing solutions either were very expensive ( Google Drive ), missed a lot of features ( Trello ) or were pretty much overloaded with features ( Wekan within Sandstorm ).

That made Nextcloud ud our natural fit for our company management and we're convinced of its integrations and flexibility.

1 upvote·10.1K views