Congrats on the release. Running actions on AWS is nice. It's complex to deal with tools in the AWS ecosystem.

I've been using it to generate Docx/PDF from my markdown. Just started to explore means to customize (with tex template). Recent updated obsidian plugin requires explicitly configuring pandoc with latex which started the rabbithole customizing experiment :)

I use different browser with multiple profiles, so i've a clean history and separation of work. Though i love some basic features like searching tabs, it was very limiting wrt privacy/blocking.

I've tried my best to adopt, the major issue was default color management and couldn't disable it. It keeps changing my display (brightens). I wish a browser releases a feature to consume less memory!

Nice, was able to get a summary for my recording https://www.videogist.co/videos/scaling-beyond-microservices...

How are you defining chapters though?

Versioning, feature toggle and rollback - automated and implemented at different level based on the system. It could be an env configuration, or db field or down migration scripts or deploying last working version.

Hey Folks,

Apart from building one myself, I've noticed many organizations building config-management systems internally since they need to manage secrets/config with features like versioning, rollbacks, etc, on their cloud.

Thought AWS and GCP has KMS, it doesn't fit the orgs with multiple service and environments requirement. I will be adding multi cloud support and critical features of secrets management workflow. I would love to hear your thoughts.

I have a similar setup of Nginx proxy, Backends are Go binaries (without Docker) and Postgres. If it's for a pet project the free tier on GCP suffices.

TXT files -> Sticky Notes -> OneNote -> Evernote -> Sublime -> Obsidian -> MD Files

Git and local markdown beats time and all note-taking apps.

If you've a small team, it doesn't make sense to have docker/established stack, and managing k8s needs experience and still is a pain.

You could get away with copying artifacts over ssh for a while.

Deployments could still be via Github actions or any other CI/CD tool or even scp.

Use Prometheus or Influx for storing metrics, ELK or Opensearch or loki for logs, Grafana for visualization, and Jaeger for tracing.

You would need a team to configure this setup and make it right over time. It's worth the investment instead of paying a cloud market leader.