Data access control isn’t easy. While it can sound quite simple (just give access to the authorized entities), it is very difficult, both on a theoretical side (who is an authorized entity? What does authorized mean? And how do we identify an entity?) and on a pratical side.
You have a static website and you want to share to your team the last changes you have done, before going online! How to do so?
At fleetster we have our own instance of Gitlab and we rely a lot on Gitlab CI. How can be otherwise? We are a small team, with a lot of different projects (only in last month, we had more than 13.000 commits over 25 different projects, and we are only 10 - and I work part time).
In last three months one of the task I had at archon.ai was to implement a pipeline to autodeploy our services. We use an instance of Gitlab to host our code, so after some proof of concepts we chose to use Gitlab CI to test and deploy our code.
Hey all, it has been a while since last time I updated my blog. In last two months I did not contribute much to the opensource world, both for time issues (work and uni take a lot of my free time) but mainly because I lost motivation.
It’s Nov, 20th again, and as every year it’s time for the Ubuntu Community Appreciation Day :-)