If you ever used Heroku services, you probably liked their release process. It is built around git. Every application you host there has its own repository. To deploy an application you simply push your changes to this repository and they do the magic. Have you ever wondered, how they do this magic? I did. So when I got my VPS in Digital Ocean to host my applications, I wanted to have a similar deployment experience like on Heroku.
Quite recently I’ve started working on new features for the Warden project and published the first prelease version to the NuGet (along with other packages that are meant to be additional plugins). In this post, I will discuss the available extensions that are basically responsible for making the fluent API even more fluent and the integrations that are a totally new thing, implemented as separate plugins (similarly to the watchers), which provide a quick access to the external services that can be part...
Any Kronos client will be available to use three basic commandsInsertGetDelete In future I want to add few more, like Count and GetKeys. Each of requests to the server serialized to binary form is preceded by few bytes of meta-data, including RequestType. In code its represented as a Request class, which in addition to type has two generic methods. At the beginning they might look difficult, but they are quite simple. First of them is responsible for sending any request to the server via special connec...
Immutability is a quite old concept that is mostly related to the functional programming, however, it’s also (maybe not so widely) used in the object oriented programming. An immutable variable/object can not be mutated, which means that once it’s been initialized it will never change it’s original value/reference (unless it’s deallocated). This approach results in some great benefits such as out of the box thread safety, yet in the OOP world, it does seem to be quite often abused or even not used at al...
If you’re looking for a simple service for monitoring your MongoDB (things like opening a connection to the database or executing a query and processing the results), then you might find interesting a new type of the watcher added to the Sentry. The MongoDB watcher uses the C# MongoDB Driver under the hood but it’s been implemented in a way, that it’s possible to provide any driver that you’d like. In this post I’ll present how to use it and why it’s been implemented this way instead of another one.
W ostatnim wpisie poruszyłem tematykę IoC i w przykładowym kawałku kodu dla LocationRepo znajduje się metoda GetLocations zwracająca typ IQueryable. Zwróciła na to uwagę pewna osoba odwiedzająca bloga i słusznie. Stwierdziłem więc, że lepiej będzie rozpisać się krótko na ten temat niż edytować poprzedni wpis. No więc dlaczego zwracanie typu IQueryable
In my very first blog post on the contest I mentioned Yeoman, Gulp and Bower. Though my project changed, I’m still actively using the last two. I find it very helpful when with Gulp, I can make my website refresh while I’m making changes, so they are instantly visible on the screen. In this post I will show you some useful tasks that you can quickly implement in your own (web) project. First of all, I’m using Visual Studio Code (awesome tool), which gives me all of the functionalities I need for devel...
A few days ago I’ve gave it a shot and posted a link to my project on the reddit. Amongst some positive comments, there was this one: "I would never use a library that is not documented at all". Although it was the very first version of the Sentry, a typical preview & work in progress thingy (which I did forget to mention in my post), I’ve realized that it’s high time to provide some form of documentation, otherwise why would anyone use that library, even if it was making a miracles? I thought that...
Recently I’ve had this idea that came into my mind while working on the Sentry – let the users of my library (if there will be any) to configure not only the set of rules, connection strings, urls etc. but also the underlying providers that do all of the heavy lifting (e.g. the HttpClient responsible for communicating with the API). It means that as long as you’re not satisfied with the default solution, please feel free to provide your own engine that will for example talk to the database and perform a ...
This is third post in a series about MiSeCo – a project I am working on for the “Daj się poznać challenge” (in Polish). In the last post, I wrote about the structure of a MiSeCo project and how I am going to implement the base functionality. Today I would like to show you how I managed to create my first interface implementation dynamically in runtime. Just to remind you, I need them to be able to proxy the calls between microservices through some (to be defined) protocol – probably over HTTP co...
macko (32 816,53)
http://pawlos.blo... (31 564,45)
pzielinski (27 178,29)
gordon_shumway (21 178,87)
paduda (20 336,33)
psz750 (13 018,14)
rroszczyk (10 383,88)
Damian (9 041,08)
danielplawgo (7 235,99)
arek (6 807,9)
burczu (6 214,22)
PaSkol (5 393,84)
lukaszgasior (4 097,38)
jj09 (3 498,06)
jedmac (3 298,38)
http://jakub-flor... (3 224,66)
CaMeL (2 954,87)
spetz (2 653,17)
mnikolajuk (2 596,93)
lkurzyniec (2 554,5)