Hi Doug, When serving from client/remote, you don't use an Active4D folder. All configuration files (.ini) and libraries (.a4l) — including the standard Active4D stuff — have to be separated into 'conf' and 'lib' directories. See page 41 of the docs for the possible locations of the 'conf' directory, and page 117 for possible locations of the 'lib' directory.
I can't quite remember the reasoning behind this, but that's the way it is for now. I'll look into supporting a single Active4D folder on client. As for integrating with git on the client, since the directory structure is different than on server/standalone, I suggest writing a simple shell script that checks out the code into some convenient place, then symlink the individual config and lib files into the conf and lib directories. By the way, you may want to use 'git pull --rebase' when distributing code to a non-development machine. > On Sep 7, 2017, at 11:35 AM, Doug Hall <[email protected]> wrote: > > Oops. I forgot to mention that when I try to access my default url, I get > an active4D 404 error. (The requested URL / was not found on this server) > > Doug > > On Thu, Sep 7, 2017 at 1:32 PM, Doug Hall <[email protected]> wrote: > >> I have my "AIDTdb" (<4d structure> folder) in a git repository, so that I >> can easily track my Active4D changes on multiple machines (locally, on a >> test server, and production). Of course, I've configured the .gitignore >> file to disregard all the 4D files, among others. The Active4D folders >> inside this folder are configured pretty much the way they're described in >> the documentation, and shown in the Demo app. For consistency's sake, I'd >> like to keep my git archive at /Users/<user>/Documents/AIDTdb on all >> machines. Since Active4D can make use of symlinks/aliases on MacOS, I >> thought this wouldn't be a big deal. >> >> Configuring things to work with 4D Standalone, and 4D Server is >> straightforward. However, it's proving quite difficult to configure it with >> 4D Client (Remote). According to the manual, the <default> folder for a 4D >> Remote client can be located at <user_home>/Library/Application >> Support/4D/com.aparajita/Active4D. On my personal machine and the server >> machine, my <default> folder and my <4d structure> folder are one and the >> same (AIDTdb). However, this cannot happen on 4D Remote because the >> <default> folder wants to be the same folder where my config folders are >> (Active4D). >> >> I tried to create a symlink file called "com.aparajita", to my AIDTdb >> folder, and placed it inside my ~/Library/Application Support/4D folder. >> This way, my "Active4D" folder inside of AIDTdb would be at the proper >> relative location for Active4D to find the configuration files. >> >> This is confusing as hell. Would somebody please tell me EXACTLY how to do >> this! Remember, I want to be able to use git to pull in relevant changes, >> to the 4D Remote machine, where I'm running my web server. The Active4D >> Documentation seems thorough, but it's also confusing. I can't get it to >> work. Aparajita, if you're reading this, please figure out how to make this >> much simpler for future developers. >> >> Also, it looks like I will need to remove the Active4D.ini and perhaps >> Virtualhosts.ini from my git repository, if the 4D Remote machine cannot >> leverage the same <default> shortcut that's being used in 4D Standalone and >> 4D Server environments. Please, tell me if I'm wrong. >> >> >> Separate Issue: >> >> Where are Active4D log files put on 4D Remote? It may not be logging at >> all, if it doesn't like the <default> value, but I can't tell. I CAN see >> Active4D trying to find my key file on my 4D Server machine. I assume it's >> running simply because the plugin is there. My code runs A4D_Startup in On >> Server Startup, but I've modified it to look for my "weba4d" (root) folder >> before actually tries to initialize Active4D. This folder is only found in >> places I want to run Active4D. (It's not on my production 4D Server, but it >> IS on my development server, because I only want to use one machine for >> testing.) >> >> Thanks, >> Doug >> > _______________________________________________ > 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/
