RealTimeSync has been a boon for my current workflow, where I'm working with front-end (static files) in a huge Java spring application full of external maven dependencies. It takes about 20 minutes to build and deploy, but RealTimeSync has allowed me to keep parity of my front-end files between the version-controlled source checkout and locally deployed cache (I work on source, RealTimeSync checks for new and newer files there every 0 seconds and copies them to the server cache).
The problem comes when I do actually need to clean, rebuild and deploy: the server's cache is kept in a folder whose parent has a randomly generated name, so I need to find that folder, copy its name, open up RealTimeSync and paste in the new value, then restart.
What I'm wondering is whether I can use a RealTimeSync process to grab the new folder name, then start another RealTimeSync process with my previous settings, qualified by that new folder name to watch in, or whether I can run a simple bash script at the end of my build process and trigger the latter RealTimeSync process from there.
Any ideas?
Recursive RealTimeSync (with a bit of logic) CLI script
- Posts: 1
- Joined: 13 Mar 2013
- Site Admin
- Posts: 7280
- Joined: 9 Dec 2007
The simplest solution is to use an environment macro instead of a fixed folder name. When the folders need to change, update the macro and restart from a script. Environment macros are supported for both FFS and RTS.