encrypting script-only stacks

[Bob Sneidar]

I REALLY need to start using GIT. I am running into that constantly. Are database schema changes gitable, or would I need to create a separate schema?

Bob S


> On Jan 14, 2020, at 20:36 , Mark Wieder via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> On 1/14/20 9:46 AM, Richard Gaskin via use-livecode wrote:
> 
>> Beyond backup across versions (since that's widely available in most cloud storage for even binary files), that Git features do you find most valuable?
> 
> As in Trevor's description, the advantage of being able to create new branches for experimental work can't be overstated.
> 
> Consider: you have a working project and want to try making some changes that may or may not work. And that may or may not stop existing things from working. Or maybe you just want to try some A-B testing and be able to create two different versions. Or create a new version and be able to do some performance benchmarking.
> 
> All without messing with your existing product code.
> 
> If it works you can merge the branch into the main code. If not then just dump the branch and you haven't lost anything except some time.
> 
> I also use tagging in git to set release values, so that I can easily see what's changed from one release to the next.
> 
> -- 
> Mark Wieder
> ahsoftware at gmail.com