Currently it is not. Initially the repository was public then I got feedback from people that I should keep the code hidden (for security and privacy reasons). What do you suggest? Should I make it open source?
Please make it open source. There is a lot to learn from the code as it is complete full stack. Regarding privacy, you can put the sensitive file into .gitignore like the ones with config data.
Security through obscurity is no security at all. Hide anything that has sensitive data (ignore / abstract / use configuration details for api keys and login and such - you do have a CI pipeline with secret handling, don't you?), but make the site public and open. You'll learn more from it too, because as people use it, they can submit bugs, issues and (hopefully) pull requests and ideas for improvements.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks Sahil 😎
Currently it is not. Initially the repository was public then I got feedback from people that I should keep the code hidden (for security and privacy reasons). What do you suggest? Should I make it open source?
Please make it open source. There is a lot to learn from the code as it is complete full stack. Regarding privacy, you can put the sensitive file into
.gitignorelike the ones with config data.Okay, I'll update the files and make it public again. I'll do it ASAP.
Thanks
Security through obscurity is no security at all. Hide anything that has sensitive data (ignore / abstract / use configuration details for api keys and login and such - you do have a CI pipeline with secret handling, don't you?), but make the site public and open. You'll learn more from it too, because as people use it, they can submit bugs, issues and (hopefully) pull requests and ideas for improvements.