Portable Log and Database locations

[zim2323]

I have copies my Syncovery install to my portable USB drive so that whether I'm at home or on the road I can sync the necessary files to wherever I want/need them.

I've been able to configure where the INI file goes, but it escapes me as to where/how I configure the location the Database and Log files go to. I either I want them in the root Syncovery folder (?:\Syncovery\) or inside a folder under that location (?:\Syncovery\Database ; ?:\Syncovery\Logs).

I have tried the following for both, but use Logs as the example:
(nothing / empty location)
\
Logs
\Logs
.\Logs
$PROGDRIVE
$PROGDRIVE\Logs
$PROGDRIVE$\Logs
%PROGDRIVE\Logs
%PROGDRIVE%\Logs


WHAT do I need to put (variable or other) in order to use the current directory for Syncovery as the Database and Log file location. I would expect this to work just like the INI file location setting, whether a choice or the option to define.

Thanks!

[zim2323]

On that same note, I have another personal project I'm doing where I want to use something like $PROGDRIVE for the right path, but I need the whole "current" path where Syncovery is being run. Something like $PROGPATH. Where instead of just getting 'L:', I would get 'L:\Syncovery'.

Is that already possible? How?

If not, can it be added? Timeline?

The Windows Environment Variable %CD% does not work in this case.

[superflexible]

$PROGDRIVE\Logs should work.

For the database, it almost works but I need to fix some things.

Due to a large to do list, I cannot give ETAs for individual items.

[zim2323]

$PROGDRIVE\Logs does not work for me. It may "work", but the folder that I run Syncovery from will be dynamic.

If Syncovery folder is in L:\Apps\Syncovery, then $PROGDRIVE only returns L:, which would make the path for Logs L:\Logs.

WHERE the logs are is important, and I don't want them in the root of the drive. I need the Logs to be in L:\Apps\Syncovery\Logs, not L:\Logs.

This is where a $PROGPATH variable would come in really handy. The way this works is that I'm doing a COPY from my FTP site to a local random folder where Syncovery exists, that will change dynamically depending on what computer I'm working from. I need Left={FTP SITE} and Right=$PROGPATH\FILES. This will pull copy down all files from my FTP to this working location. Once I'm done, I have a second profile that does a MOVE of those files back with Left=$PROGPATH\FILES, and Right={FTP SITE}.

The reason this is important is that security permissions dictate that I CAN NOT write files to the root of the drive.


I have one of your competitor products (SyncBack) working flawlessly doing this, as they have a %THISPATH% variable that translates the current path that SyncBack is running from. I'd rather get this working in Syncovery because I already purchased it, it's a heck of a lot more feature rich, AND it's 100000 times faster!

Thanks!

[zim2323]

Any additional thoughts on this?

Any timetable for release? Before or after v7 final?

[superflexible]

After v7.00 final

I have it on my list, but around 50 other customers are also asking when their requests will be fulfilled, right now the next thing will be Sharepoint support. I will do it though. Feel free to remind me.