Search for a command to run...
Software developer documenting my journey through web and mobile development. I share what I learn, build, and struggle with—from React to SwiftUI, architecture decisions to deployment challenges. Not an expert, just passionate about coding and learning in public. Join me as I navigate the tech landscape one commit at a time.
No comments yet. Be the first to comment.
The Problem Every Developer Faces with AI Coding Assistants You've probably experienced this frustration: you ask Claude, Cursor, or any AI coding assistant to write a function, and it confidently generates code that looks perfect at first glance. Bu...
The Backstory So there I was, staring at my shiny new Passbolt installation on Ubuntu 24.04, when that familiar dread crept in: "What happens when (not if) something goes wrong?" After one too many "I'll set up backups tomorrow" moments, I finally de...
TL;DR The custom Reactotron transport for react-native-logs improves logging by handling various message types, adding metadata, and allowing custom prefixes, making your logs more informative and easier to manage. The Backstory Logging is a crucial ...
TL;DR Add parallel: N to your GitLab CI job and pass --shard=${CI_NODE_INDEX}/${CI_NODE_TOTAL} to Playwright to slash your test execution time and keep your team shipping fast. The Backstory Last week, our test suite execution time crossed the dreade...
Error messages are often the first interaction users have with your support system. When they're cryptic, technical, or in the wrong language, they create confusion rather than clarity. That's why I built the Appwrite Exceptions Translator - a lightw...
I recently got an error on my work machine while restoring a backup of my ssh keys. The error stated that the permissions were too open for my private key.
Permissions 0777 for '/home/<user>/.ssh/id_rsa' are too open.
Following an article from Stackoverflow i've set the access rights of all the files in the .ssh folder to 600. This solved the issue but is actually not better, because each file has it’s own permission for a reason. We set read only permission on these files for security reasons. Some are even changed by your ssh client and need a different permission due to that.
These commands can help you get your permissions right
chown -R $USER:$USER ~/.ssh
chmod 700 ~/.ssh
chmod 644 ~/.ssh/authorized_keys
chmod 644 ~/.ssh/known_hosts
chmod 644 ~/.ssh/config
chmod 600 ~/.ssh/id*
chmod 644 ~/.ssh/id*.pub
You may need to use sudo to avoid errors.
I hope this helped you 😉. If you have any questions, please send me a little message. I will be happy to help you. If you liked this tutorial, please share it with your friends. Thank you for reading!