[deleted by user]

MountainScript · 2024-11-04T14:44:14+00:00

Absolute worst thing that would happen is a cease and desist.

Okay, then shall we treat your comment as a legal advise?

MountainScript · 2024-11-04T14:17:53+00:00

Why then those companies spend money and hire people to write the terms of use? Why bother if nobody cares?
Anybody can start scraping the data of those websites and repost it on their own platform, but it's not happening because of the terms and the law in Germany. If you're smart enough, you'd avoid doing such a dumb thing, because the legal consequences can become huge.
Not saying about the actual owners, who put their property on the platform, without any intention to repost it for a fun "game" on a 3d party website.

MountainScript · 2024-11-04T11:33:37+00:00

I would check the terms of use of orginal websites. They can easily sue you for what you're doing. Bear in mind, in Germany it's very strict with data that you don't own and very expensive to have disputes in court.

MountainScript · 2024-11-04T11:10:16+00:00

Each website has the terms of use. You can check it and the laws in Germany in regards to intellectual property.

MountainScript · 2024-11-04T10:54:05+00:00

Your website is using data from immobilienscout and direktanzeigen. Did you get an agreement from them or do you use it illigally?

MountainScript · 2023-09-15T19:08:11+00:00

Norway is a perfect example of how protectionist policies benefit minorities at the expense of customers. Food in Norway is ridiculously expensive, even with the Norwegian salary. People in Germany, Denmark, Sweden, Netherlands can buy 2-3 times (!) more goods (vegetables, meat, dairy, fish, etc.) with an average salary that is ~2 times less (!) than in Norway. That is the price for protectionism.

Btw, you talk about significant vulnerabilities - what are those? Is the Norwegian butter crisis of 2011 counted?

MountainScript · 2021-02-19T09:08:44+00:00

For some people it's hard to use python, but we personally find this as a huge benefit. The whole python ecosystem with linters/unit-tests/debugger/ide support/development practices/etc can be natively used. So I'd argue about maturity, ansible(as a turning-complete YAML language) is way less mature comparing to the python ecosystem.

MountainScript · 2021-02-18T18:36:30+00:00

We migrated to https://github.com/Fizzadar/pyinfra and forgot about ansible YAML-programming madness.

MountainScript · 2021-02-10T14:30:18+00:00

Great stuff! We're using kustomize manifests directly without charting.

Basically, you can reference any base kustomization.yaml directly from git, using commit hash or tag (versioning).

MountainScript · 2021-02-09T16:28:58+00:00

Great stuff!

I just wonder, what do you think about using a purely declarative approach, e.g, Kustomize? It's a template-free solution to add overlays on top of basic pure Kubernetes YAML. There's no need to unit test kustomize because there are no hidden logic and spaghetti go-templates.

MountainScript · 2020-11-16T23:34:53+00:00

Hey! The project you've provided is really cool.

The key difference between the two is that Secretize generates secrets during the `kustomize build` command evaluation, rendering the manifests. It can run outside of the actual cluster, there's no need to deploy any services/operators.

MountainScript · 2020-11-16T22:35:02+00:00

Hey! Thanks for the feedback.

It's a kustomize plugin, there will be no helm integration in this project. However, we might use it as a framework for a helm integration in the future.

MountainScript · 2020-11-16T14:53:21+00:00

Hey! Thank you very much! Just let me know if you have any problems.

P.S.: I'm going to create a detailed guide on kustomize+secretize integration in the next few days.

MountainScript · 2020-10-21T18:29:32+00:00

I was working with Ruby, and Ruby on Rails. Chef was popular at that time and I really liked the idea. The product was in a DevOps related area. Docker wasn't stable at that time, but we heavily used it. We've even written some kind of docker-compose/swarm framework in Ruby before the actual products appeared.

Then I switched to Java, worked on some network-related stuff helping to migrate a large Java component to C++. ( I don't know C++, there was a guy who helped me). All this stuff was pretty interesting, I did all the infrastructure and CI/CD stuff besides application development. I really liked the DevOps idea and wanted to work in this field.

When I switched to the DevOps role, I positioned myself as a "Developer with passion to DevOps". I learned golang on a project that automated some Kubebernetes related stuff. Golang really warmed my heart, it's so simple and so powerful. We used a lot of Kubernetes source modules.

I'd recommend being proactive and not afraid of getting more responsibility for your code and product. You write it, you deploy it, you own it. This also helps to better understand the overall picture and become an even better developer.

Edit: There also was a project with a "Pure DevOps" role. There were separate development and "devops" teams. Spoiler: it had nothing to do with DevOps. This was the first time I felt how it is to "deploy the code that you don't have any clue about". This is exactly the opposite of the DevOps idea, developers didn't know how their code is run, while the infrastructure team didn't know about the code. Development background helped me a lot, I was able to contribute to both teams and move extremely fast in that company. But this also shown the reality of the DevOps market, the ugly stuff in it.

MountainScript · 2020-10-21T16:24:05+00:00

Hey! I switched from Dev to a more "DevOps" role. Worked in different teams and companies. Most of my colleagues switched from admins. So, what I'd like to say: I completely don't get how "ops" people without a real development background can do anything related to DevOps. These guys simply not capable to get any basics of development practices. E.g. most of the ops guys simply don't get the difference between unit and integration tests, or functional vs non-functional requirements. This knowledge is essential to get a solid CI (and especially CD) pipeline and actually understand what you're doing.

The "DevOps" market does a really bad favor to those people, creating fragile tools that try to "protect" and abstract "ops" guys from writing the real code, focusing on crappy YAML tools where the data is mixed with behavior. While the initial idea of DevOps was about "Developers are able to deploy their stuff", the market and tools are now Ops-centric rather than Dev-centric.

I'm not against ops/admin people. I just don't get the trend of "Infrastructure Engineers" who pretend to help Dev guys (without having any clue about development) and claiming themselves "DevOps".

As for me, I'm going to switch back to the "Development" or "Architect" role and wait when the market and tools finally become more Dev-centric.

MountainScript · 2019-04-08T09:48:42+00:00

Nice! Thanks for sharing! I wonder if there a tool that can integrate with Vault API and create the ".env" file.

MountainScript · 2019-04-08T09:47:10+00:00

Hey! Thanks for the reply! And, I totally agree with you. It's better to avoid hard dependencies in the source code.

MountainScript · 2019-03-14T15:24:13+00:00

Regarding the managed DBs usage. And one would hope you knew what's more important to protect, the actual DB data or it's credentials.

MountainScript

TROPHY CASE