Don't copy external container files

OttoDeploy
,
21

Hey Ken,

Which version of OttoFMS is your server running on? If its not one of the last couple, you may not have the close build option on the server yet. If it is one of the more recent ones, could you grab the debug logs for the deployment and send them to me?

-Kyle

22

Thanks Kyle - I sent the debug log for that deployment.

23

Hey Ken,

Which version of OttoFMS is the source server running?

-Kyle

24

Hey y’all,

Looked at this with Ken, it looks like the handling for the build options on the JIT builds ignores the closeFiles option currently. I’ll get a fix into our next version which handles this. Running a build ahead of time with the close files option will properly close the files during said build and not copy all the container data. I’d recommend running the build ahead of time for now, it will make the builds significantly faster.

-Kyle

25

Thanks Kyle. Two follow-ups -

  • Is there any way to schedule a build (aside from JIT)? Closing files can only really happen off-hours.
  • Do you think there’ll be any future support for copying files without containers, and without having to close them first?

Thanks for looking into this.
Ken

26

Hey Ken,

At the moment there is no way to schedule a build, it is something we have talked about adding though.

As for support for copying files without container data without closing them, it is unlikely that we will support that unless FileMaker gives us a way to do so with backups. The only way we can create copies of files while they are open (safely) is with FileMaker backups. The reason we close them is that we can simply make a copy of the file in the filesystem when they are closed.

As for a fix for the issue of the build options not getting passed through, I suspect we will be releasing the fix next week sometime.

Thank you!

-kyle

27

Hey Ken,

The issue with the Just In Time build options not being properly passed along is fixed in OttoFMS version 4.6.2. Let me know if you have issues going forward!

-Kyle