"As I get further along developing and testing my website, I find that I sometimes lose track of what version of a file I'm using. I thought that if VS Code could be made to insert a timestamp each time it saves a file that it might help me. My setup has a DEV_Environment where I make additions and changes. I then use a batch file to deploy the relevant files to localhost server environment on a different partition."
"If VS Cde put a timestamp on the files when they are saved in the DEV_Environment, it would be easy to tell if the localhost file and the DEV file were the same version. Am I over thinking this? Perhaps this is not an issue for more experienced developers but I think it would help me. If you use any such aids, how did you implement them?"
The developer sometimes loses track of which file versions are in use while developing and testing a website. The developer wants VS Code to insert a timestamp on each save in the DEV_Environment so saved files can be compared directly with deployed localhost copies on a different partition. The current workflow uses a batch file to deploy relevant files from DEV to the localhost server. Timestamping saved files would provide an immediate, visible version marker to tell whether the localhost file and the DEV file are the same version. The developer asks whether this is unnecessary for experienced developers and requests examples of implemented aids.
Read at SitePoint Forums | Web Development & Design Community
Unable to calculate read time
Collection
[
|
...
]