In the forthcoming v7, the separate "conf" and "lib" directories have been abandoned altogether for a single "Active4D" directory, so you can keep the exact same directory structure in all environments.
> On Sep 11, 2017, at 4:57 PM, Doug Hall <[email protected]> wrote: > > Aparajita, thanks again for the follow-up email, earlier. I thought I'd go > ahead and publish this email I started last Friday, regarding A4D > configuration. Perhaps there's an idea or two you could implement in the > future. > ----------- > > I did actually try it as a folder name, first. I forgot what happened to > make me change it back. At the time, I didn't know where my log file was, > or I'd have seen that wasn't the problem. Then, my assumptions led me to > believe that you would not have changed the default location of these init > and library files. > > I just hope that, in the future, you can solidify the structure, so that > it's much easier to keep in version control. In my opinion, it's fine to > create aliases to folders that already exist within the <4D > Structure/Default folder>. It's not okay to make developers combine both > Active4D lib files and personal lib files, in the same folder. In a future > version, you could rely more on convention over configuration, too. All > people could define a default folder (forget <4d structure folder>, this > folder has no applicable meaning on 4D Remote, since server files are > cached.) To me, it makes sense to separate my A4D (default) folder from the > 4D Structure folder on 4D Standalone and 4D Server instances, anyway. If > everything relative to code and configuration has to be within the default > folder, and in folders with specific names, then it's MUCH simpler to > configure. > > The way it is now, having to create symlinks, or copy files between > locations -- just because it's being served from 4D in remote mode, really > sucks. I'm sure you have your reasons, but let's get this fixed in future > versions (7.X?). > > As an aside, would you see a problem with putting an initial Active4D > folder on a gitlab instance? This way, if you have an update to a method or > initial config file, we can easily spot this through your commits, and more > readily make those changes on our own setups. > > Doug > > On Fri, Sep 8, 2017 at 12:47 PM, Aparajita Fishman <[email protected]> > wrote: > >>> Ok, thanks for the clarification and tips. I actually saw the >>> ".../Active4D/conf" listed in the documentation, but assumed that the >>> "conf" part wasn't intended to represent a folder, but that it stood for >>> any config file, since the Active4D folder is normally where they reside. >>> :-/ >> >> Funny the assumptions we make. For future reference, I made sure I was >> extremely explicit in the docs. Whatever it says, take it literally. If >> "conf" stood for any config file, the first search path would have been >> <Database folder>/Active4D/conf, not <Database folder>/Active4D. >> >> >>> I'll definitely refresh my memory on git hooks! >> >> It isn't a hook, --rebase is just telling git not to make a merge commit >> but to rewrite the history to match the repo. >> >> _______________________________________________ >> Active4D-dev mailing list >> [email protected] >> http://list.aparajitaworld.com/listinfo/active4d-dev >> Archives: http://active4d-nabble.aparajitaworld.com/ >> > _______________________________________________ > Active4D-dev mailing list > [email protected] > http://list.aparajitaworld.com/listinfo/active4d-dev > Archives: http://active4d-nabble.aparajitaworld.com/ _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
