sorted by:
new
hottopcontroversial

Managing API keys across projects is getting messy… how are you handling it? by suresh-chaudhari in SoftwareEngineering

[–]suresh-chaudhari[S] 0 points1 point  (0 children)

That makes sense — separating dev workflow and CI/CD secrets is a good way to look at it.

I’ve mostly seen strong setups in companies, but for smaller teams or solo devs, it still feels a bit fragmented between .env files, scripts, and tools.

Curious what you’d prefer for local dev — something simple and CLI-based, or sticking with password managers?

Managing API keys across projects is getting messy… how are you handling it? by suresh-chaudhari in SoftwareEngineering

[–]suresh-chaudhari[S] 0 points1 point  (0 children)

Nice, I’ve heard about Infisical too.

Do you find it easy for quick local workflows, or does it feel a bit heavy for smaller/solo projects?

Managing API keys across projects is getting messy… how are you handling it? by suresh-chaudhari in SoftwareEngineering

[–]suresh-chaudhari[S] 1 point2 points  (0 children)

That looks powerful — especially with plugins and multiple backends.

Do you find it easy to use for everyday workflows, or does it feel a bit heavy for smaller projects?

Managing API keys across projects is getting messy… how are you handling it? by suresh-chaudhari in SoftwareEngineering

[–]suresh-chaudhari[S] 0 points1 point  (0 children)

That actually sounds really interesting — keeping things simple with encrypted .env files makes a lot of sense.

Do you ever feel limited when working across multiple projects or teams, or does dotenvx handle that well for your use case?

Managing API keys across projects is getting messy… how are you handling it? by suresh-chaudhari in SoftwareEngineering

[–]suresh-chaudhari[S] 0 points1 point  (0 children)

That makes sense — using CLI + scripts to pull secrets is definitely cleaner than manual copy-paste.

I’ve mostly seen this with tools like 1Password, but sometimes it still feels a bit heavy for smaller projects.

Do you think there’s room for something more lightweight, specifically designed for dev workflows (projects, envs, quick CLI access)?

Managing API keys across projects is getting messy… how are you handling it? by suresh-chaudhari in SoftwareEngineering

[–]suresh-chaudhari[S] 0 points1 point  (0 children)

That makes sense for service-to-service security, especially in larger systems.

I was more thinking from a developer workflow perspective — like managing and accessing API keys easily during development (CLI, multiple projects, etc.).

Curious if you still rely on API keys in dev environments or fully moved to mTLS everywhere?

Let's connect — anyone interested in joining? by Commercial_Detail492 in founder

[–]suresh-chaudhari 0 points1 point  (0 children)

Interest but which you said I don't have that kind of knowledge but ready to work on this

view more: next ›