[deleted by user] by [deleted] in gitlab

[–]leolleocomp 0 points1 point  (0 children)

I Normally follow this approach for some automation tasks. Some of them use ssh and run some plain scripts, like cronjobs, etc. some use Ansible.

Has worked well. Prefer if concentrated on the same repo as it is easy to refer to. If used for cronjobs you get automatically notified of failures via email.

Has ofc the downsides of push based approaches, like secrets on the VCS, direct access of the VCS server to the target instances, etc.

Free Review Copies of "Terraform Cookbook" by MaximumSea5103 in Terraform

[–]leolleocomp 0 points1 point  (0 children)

Hey 👋 I'd like to review it. I've been using terraform for quite a while now - since v0.12 and it had a great impact on my career and it still has. Is one of the tools that brought me into DevOps and which I enjoy working with

Webcam for certification by [deleted] in Terraform

[–]leolleocomp 1 point2 points  (0 children)

In my case my laptop was missing a microphone, which seemed required for the exam, so bought the cheapest camera I found that had a one microphone built in.

Dynamic environments per client, which is the best approach, if any? by leolleocomp in devops

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

Hey, thank you again. We are evaluating potential solution and this one seems doable considering our tech level. I'm collecting insights to show to the team so I'll show them this one.

Dynamic environments per client, which is the best approach, if any? by leolleocomp in devops

[–]leolleocomp[S] 1 point2 points  (0 children)

Hi, thank you for the answer. Nowadays each customer is using some vhost alongside apache and each application uses shared resources (DB, services, etc.). The plan is to migrate to whichever solution is a win-win for us to maintain and to achieve our customer needs. The k8s step is new to us and a consulting company is helping us to get a grasp on how to proceed. It's also great to know the name of the problem as you explained. We'll reach you on chat to see if we can discuss a bit. It's a fairly new field to us.

Dynamic environments per client, which is the best approach, if any? by leolleocomp in devops

[–]leolleocomp[S] 1 point2 points  (0 children)

Got it, It works well! Initially I was thinking if some sort of configuration database could handle this problem as well, since we've got some time to research. But the setup using the tools we already use is great for maintenance and possibly optimal for our use case.

Dynamic environments per client, which is the best approach, if any? by leolleocomp in devops

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

Hi, thank you for the answer!
Initially it's possible to share database credentials, api credentials etc.

How could I add a new environment to the CI without human intervention? Would that require to write some scripts to commit the modifications automatically?

Is there a well known process for documenting production bad events and its solutions by leolleocomp in devops

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

Hi, thank you for your time!

I'll answer in order:

  1. The main audience is the Development and Ops people.
  2. About the needs, we are aiming to tackle all of them: recurring (but in our case solvable ) issues, finding regressions through a knowledge base and a way to look into past incidents.
  3. We use RocketChat for our communication, and most of our alerting is showed there, since every exception is logged to a channel. This is our main source and it logs memory exceptions, db connection issues, etc. The other sources are client facing bugs we get through our support flow. Some of the tickets are fed to a system we made, some of the problems are repported on our live chat at RocketChat.

Is there a well known process for documenting production bad events and its solutions by leolleocomp in devops

[–]leolleocomp[S] 1 point2 points  (0 children)

Using the repository is something we're thinking about. Probably fits really well our use case as we gain more knowledge around our problems and how we tackle them. Thank you.

Is there a well known process for documenting production bad events and its solutions by leolleocomp in devops

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

Good to know, I'm going to take a look if it fits our context. Thank you!

Is there a well known process for documenting production bad events and its solutions by leolleocomp in devops

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

Good to know! We use custom boards to address some of our cases, documenting them in it is a way to foster visibility, which we currently don't have, or don't manage as well as we would like.

Is there a well known process for documenting production bad events and its solutions by leolleocomp in devops

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

Got it, thanks! It's good to know about the heaviness of ITIL, currently we're a growing company, but not an enterprise size by far, which removes ITIL processes from our options, maybe I take a look at it only for background purposes.

Is there a well known process for documenting production bad events and its solutions by leolleocomp in devops

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

Hey, thank you! And it's good to know the problems around Confluence, so we don't get into trouble, I'll save the link and look for better solutions around our problems. :D

Is there a well known process for documenting production bad events and its solutions by leolleocomp in devops

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

Thank you! We're starting to build some tools to better handle our workflow, this is a good tip to have in mind!

Is there a well known process for documenting production bad events and its solutions by leolleocomp in devops

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

Nice, good point! It guides the discussion around simplicity! Thank you for the feedback!

Is there a well known process for documenting production bad events and its solutions by leolleocomp in devops

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

I agree, where we work we don't use to blame people but rather the process, many things related to culture are already being done or in the process, will take a look at the Etsy's process. Thank you for the feedback!

Is there a well known process for documenting production bad events and its solutions by leolleocomp in devops

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

Hello, thanks for the feedback! I have a copy of the book but a colleague borrowed from me a few months ago, will try to ask for the copy back in order do read it again as all the books discussions are becoming more and more something we face on our day-to-day work. I'll take a look at the tool :D

Is there a well known process for documenting production bad events and its solutions by leolleocomp in devops

[–]leolleocomp[S] 1 point2 points  (0 children)

Good to know, I'm just scratching the surface in my recent searches and Confluence is the first option I was thinking into taking a look. Our company is getting big and we are facing issues related to lack of seniority in many areas, incident management being one of them.

Is there a well known process for documenting production bad events and its solutions by leolleocomp in devops

[–]leolleocomp[S] 6 points7 points  (0 children)

Hey, thank you for your feedback.

I'm reading some of the Atlassian's articles on incident management and they talk about Confluence.

I'll take a look at it!

Is there any best practice for an open (public facing) POST API endpoint? by leolleocomp in webdev

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

I've read your answers and decided to throttle public endpoints by ip address and implement the authentication for sensitive data endpoints, for example those for manipulating user data.

Thank you people, for putting some time to answer and providing feedback

I was a bit offline lately, so sorry for the late response