yea that’s way overkill. As I said earlier, these are entirely independent scripts, they are not parts of a greater whole. Creating deployment steps for each and every one of them is not a practical solution.
> On Aug 15, 2017, at 2:58 PM, Warren Young <war...@etr-usa.com> wrote: > > On Aug 15, 2017, at 2:53 PM, Steve Schow <st...@bstage.com> wrote: >> >> well…its not for a website…javascript is used for a lot of stuff out there >> besides the web. Its not practical for the name of the file to have a >> version encoded into it. > > Easily solved. During the “generate deployment package” step, create a > manifest file that maps file names to Fossil checkin IDs. Ship the manifest > along with the checked-out files. > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
