camsjams

Built it using Rust (Axum/Tonic/SQLx/Seaography) + PostgreSQL + React + TypeScript

yes will consider

Lineation | Rust/TypeScript/React/GraphQL/PostgreSQL | Senior Software Engineer | Contractor Part-Time | Remote (US-friendly time zones) | https://lineation.ai

We’re building an Agentic AI Security Platform that helps teams secure autonomous AI workflows. We’re looking for a senior engineer to help design and ship core systems across policy enforcement, runtime monitoring, incident workflows, and auditability.

You’ll work across backend and product surfaces: Rust + gRPC services, GraphQL APIs, and TypeScript/React interfaces for security operations. You should be comfortable owning features end-to-end, making pragmatic architecture decisions, and collaborating closely with product/security teams in a small, fast-moving environment.

Strong fit if you have experience with distributed systems, secure-by-default engineering, and production observability. Security product background is a plus, but not required if you’re excited to learn quickly and build in this space.

If this sounds interesting, email us at [[email protected]] with Resume/CV plus links to your GitHub/LinkedIn and a short note on systems you’ve built.

This did indeed work for Google (that's the only one I tried), but the details of how this works is best detailed in this post: https://aaronparecki.com/2018/07/07/7/oauth-for-the-open-web

The above post was also linked from the obligator project's GH readme

I too found this hard to reason, but figured it out:

If you're demoing using https://openidconnect.net for example, set your Client ID to https://openidconnect.net

Likewise, your ClientID should match the url of the website you are using this to connect with.

This was mentioned in the GitHub readme too but didn't click until trying the demo

You can't reassign constants in JS, it throws an error: Uncaught TypeError: Assignment to constant variable.

But yes you can modify objects and arrays of a constant, which is not great.

Is this cheaper though?

For a medium-to-large app, K8s should offset a lot of the operational difficulties. Also you don't have to use K8s.

Cloud is turn-on/turn-off, whereas on-premises you pay up front investment.

Here are all of the hidden costs of on-prem that folks forget about when thinking about cloud being "expensive":

- hardware

- maintenance

- electricity

- air conditioning

- security

- on-call and incident response

Here are all of the hidden time-consumers of on-prem that folks forget about when thinking about cloud being "difficult":

- os patching and maintenance

- network maintenance

- driver patching

- library updating and maintenance

- BACKUPS

- redundancy

- disaster recovery

- availability

Maybe because Capistrano is written in Ruby and the language matches their internal products? That was my only guess.

Instead, you might just want to reach out and ask for access or a zip file from the owners

So you're suggesting GitHub should determine the total "average" license of a private repo and determine if your fork is indeed valid or not, before revoking access.

How does this compare to WPGraphQL https://www.wpgraphql.com that's been around for quite some time (https://github.com/wp-graphql/wp-graphql)

Did you find shortcomings with that plugin?

But this article was published in 2014, so someone "over 40" back then would be about 48+ years old in today's harsh single-spaced modern reality.

I think this is a Franz Kafka quote

Um did anyone look at the OP's submissions? Clearly they are linked with Zepel.io: https://news.ycombinator.com/submitted?id=svikashk

I sense a lawsuit from Atlassian poised at Zepel incoming.

Which URL?

For reference:

The GitHub repo: https://github.com/camsjams/rust-coal

The Documentation: https://camsjams.github.io/rust-coal/

I was tired of building bespoke static HTML sites and having to decide if I wanted to use GatsbyJS or just hand code all of the HTML. I decided to build a tool to solve my problem!

Similar to the plot of a fairly good Eddie Murphy film: https://en.wikipedia.org/wiki/The_Distinguished_Gentleman

Do you store your API keys and other sensitive data with a site that doesn't even have a page discussing their encryption or security practices? Their privacy policy mentions they secure data with SSL protocol...

Who has access to each client's database? Is it audited? Is it encrypted at rest? I'm sure it is, but Config.ly would be wise to add this information to avoid fears.

Also you can store encrypted secrets in Git just fine, there are a number of methods to do so very safely.

Nice! I made something similar to this: https://github.com/camsjams/mr-roboto

With a slight difference, it works 100% in the browser, you can use it here: https://camsjams.github.io/mr-roboto/

But you need to store the output somewhere safe.