Best practices for obscuring sensitive information Topic is solved
-
- Posts: 5
- Joined: 19 May 2023, 10:39
Best practices for obscuring sensitive information
I would like to use version control to manage my code. In the spirit of open source I would like to make my repositories public. However, my scripts may contain sensitive information like my email or home address. What is the favorable method of obscuring this information?
Re: Best practices for obscuring sensitive information
move the sensitive info to a config file, and have your project read from the config file
then use a .gitignore file to ignore the config file so it doesnt go into the repo
then use a .gitignore file to ignore the config file so it doesnt go into the repo
Re: Best practices for obscuring sensitive information
create and query Environment Variables on ur computer
-
- Posts: 5
- Joined: 19 May 2023, 10:39
Re: Best practices for obscuring sensitive information
Is there a built-in system for reading from config files? Or do I have to write my own logic for that using FileRead? If there isn't, I guess getting system environment variables will be much smoother.
Re: Best practices for obscuring sensitive information Topic is solved
IniReadthe_alchemist wrote: ↑ Is there a built-in system for reading from config files?
-
- Posts: 5
- Joined: 19 May 2023, 10:39