I'm trying to keep my project organized and reduce the clutter of config files in the root directory. Ideally, I want to focus on the essential files needed to run and deploy the website, like npm scripts and the container specifications. What's the best way to manage and store configuration files to avoid this clutter?
2 Answers
To tackle config clutter, first consider which files are truly essential. It helps to sort out what's necessary versus what's just piling up. If there's a specific type of configuration that you find burdensome, it's worth mentioning for tailored advice! For example, if you're dealing with 5-10 different .config.ts files, it might be easier to consolidate them into a single configuration file or directory.
One cool technique is to use a symlink to point to the config directory, keeping your root neat. You can also set up your editor to ignore or hide these files, which makes for a cleaner workspace without losing access to them when you need to make changes. Just be mindful that if you do it this way, accessing them via terminal will still show the clutter unless you create some aliases to filter them out.
That’s an interesting approach! How does managing symlinks compare to just keeping files in the root folder if you don't see them anyway? Is it mainly for easier access when editing?
Absolutely! A consolidated config folder could definitely streamline things. Plus, if you're new to the team, having everything in one spot would make it much easier to figure out the entry points without digging through numerous files.