Skip to content

Instantly share code, notes, and snippets.

@auxesis
auxesis / about.markdown
Last active November 29, 2024 01:44
DevOps Sydney pages

We meet on the third Thursday of every month, at Pivotal in Sydney.

If you're taking public transport, we recommend you catch the train to Central and make the short walk from there.

Are you a recruiter? Please follow our rules for participating in the community.

Does your company want to give back to the community? Sponsor a meetup!

Talk topics

DevOps Sydney Code of Conduct

DevOps Sydney is a community meetup intended for networking and collaboration in the developer + operations community.

We value the participation of each member of the DevOps community and want all community members to have an enjoyable and fulfilling experience. Accordingly, all attendees are expected to show respect and courtesy to other attendees throughout the meetups.

To make clear what is expected, all attendees, speakers, organisers and volunteers at any Sydney DevOps event are required to conform to the following Code of Conduct. Organisers will enforce this code throughout events.

The Short Version

CREATE EXTENSION IF NOT EXISTS pgcrypto;
CREATE TYPE ore_64_8_v1_term AS (
bytes bytea
);
CREATE TYPE ore_64_8_v1 AS (
terms ore_64_8_v1_term[]
);
➔ be rails s
=> Booting Puma
=> Rails 7.0.4.2 application starting in development
=> Run `bin/rails server --help` for more startup options
Puma starting in single mode...
* Puma version: 5.6.5 (ruby 3.1.3-p185) ("Birdie's Version")
* Min threads: 5
* Max threads: 5
* Environment: development
* PID: 18387

DevOps and Data Security: words vs actions

LastPass. Shangri-La. Optus. The last 12 months have seen a reckoning for data security around the world.

But are these examples really that out of step with how we actually do security in our own organisations (not just what we tell ourselves about how we do it)?

What do organisations doing devops actually think about data security? Who do they think they are defending against? What steps are they taking to safeguard customer data?

This talk will explore two years of qualitative interviews with business and government organisations about how they think and act on data security.

# default layout (can be bsp, stack or float)
yabai -m config layout bsp
# wild west on space 1
yabai -m config --space 5 layout float
# New window spawns to the right if vertical split, or bottom if horizontal split
yabai -m config window_placement second_child
# padding set to 1px
160 # you probably want to just uncomment these lines when you are debugging — Lindsay
161 #passenger_env_var CS_PROTECT_DEBUG yes;
162 #passenger_env_var RUST_LOG trace,hyper=trace;
163
164 #passenger_env_var CS_STATIC_RUNTIME_CACHE true;
165 #passenger_env_var CS_RUNTIME_CURRENT_THREAD true;
166 #passenger_env_var TOKIO_WORKER_THREADS 2048;
167 #passenger_env_var CS_PASSTHROUGH true;
168 #passenger_spawn_method direct;
Hi there,
Just wanted to provide some feedback on the "overcoming obstacles for deaf & blind jurors" segment on the May 30, 2023 episode of the Law Report:
https://www.abc.net.au/radionational/programs/lawreport/pwc-tax-leak/102347562
First up: this was a great episode, especially the Irish example about how improving accessibility for the deaf by eliminating courtroom crosstalk also improved the experience of everyone else in the court.
There was one small issue though: the lack of a transcript for this episode.
I recognise that transcripts aren't usually provided for Law Report episodes, and they can be costly to produce, but I thought this episode in particular would be appropriate to make a transcript available for.

Outline

The purpose of this postmortem is to:

  • Provide an explanation of how the event happened, as the organisation best understands it.
  • Produce artifacts (recommendations, remediations) for prevention and improvement of detection and response approaches for handling similar future events.

Only by coming to an mutually agreeable explanation together, can we start to produce recommendations and remediations that help all of us in the future.

Whenever we talk about events that happened in the past, we need to be aware of two key cognitive biases that taint our perception of events:

DevOps and Data Security: where Aussie orgs are at

Optus. Medibank. Latitude. The last 12 months have seen a reckoning for data security in corporate Australia.

But are these examples really that out of step with how we actually do security in our own organisations (not just what we tell ourselves about how we do it)?

What do Australian organisations doing devops actually think about data security? Who do they think they are defending against? What steps are they taking to safeguard customer data?

This talk will explore two years of qualitative interviews with Australian organisations about how they think and act on data security.