Some good caveats for synthetic.conf here under the Note. When in doubt, man synthetic.conf.
Also, don’t add an entry to both synthetic.conf and add it to Path Translation.
1 Like
@marcwellington - thank you so much for the kind words and endorsement brother - it’s been a hoot.
let’s do more good things
Whoa. Aight. So, I forked it and added a few extra lines of code.
Logik-projekt → Lucid LInk → Frame IO project → Slack Channel → S3 bucket, all made within a couple of clicks. Next up, is automagic uploading the /postings folder to Frame IO via the Frame IO API, automagic making of MASV portals with automated ingests for transcodes to Lucid for editorial and ingests for graded material to footage_graded.
3 Likes
@randy - working on it brother!
3 Likes
1 Like
say that again without taking a breath.
This should be fun.
4 Likes
I’ve just finished watching the episode and it’s wildly impressive what you and everyone else have been able to do @philm. Chapeau, sir.
Quick question regarding the folder names/structure. At the end of the episode you explained how to adjust the config for a given folder structure…but is that linked to each project or is that system wide?
I’m just curious how this could work with freelancers. Say they’re working with shop A and they keep with the default values but then start working with shop B and then have a custom configuration. If the freelancer were to start the project by using the supplied template, does the custom folder structure come along as well?
4 Likes
Thanks for sharing, lots of cool ideas… lots to think about…
1 Like
@kyleobley - when you create a PROJEKT with LOGIK-PROJEKT you are creating the directory structure on disk, the related flame libraries and flame bookmarks.
The env files are also freezing the application and software versions.
The PROJEKT is then portable - we ran out of time on Logik Live #140 but I wanted to show the portability aspect:
At the moment that I created the PROJEKT on my workstation, it created a directory structure in Lucid Link, and then I began a 7 minute cron event that rsyncs the entire PROJEKT to my local disk.
If Lucid Link goes down or the internet blows up, I can alter my path to /PROJEKTS and carry on.
e.g.
If the symbolic link to Lucid Link is:
/PROJEKTS -> /Volumes/logik/Lucid/PROJEKTS
I can simply unlink the symbolic link:
sudo unlink /PROJEKTS
And relink to the backup:
sudo ln -s /NAS/PROJEKTS /PROJEKTS
It takes seconds on Linux, and takes a reboot on macOS.
If my collaborators are also doing this strategy then they can also divorce from the internet in the same way and continue to work locally, until service is restored.
The workflow is unmanaged which means that you can cache to your framestore for performance if you want, and with open clip you can automatically cache any version, but these caches are excluded from the archives, so everything remains lightweight and independent of host/framestore/network.
Once the internet is reconnected, we can all sync to the internet storage, and everyone can see everything again.
When the job is complete, we scrap the internet storage, the rsync that was working to our local storage becomes our main PROJEKT repository, and we’re already sending one copy to USB to sit on the shelf, and we’ve been dripping the data into S3 deep archive since the start of the PROJEKT.
Sorry for the long preamble but the answer to your question might be as simple as:
If you’re mindful of the JSON files that you use to interface with different companies, you can build PROJEKTs that have:
- Default Trees
- Corporate Trees
- Unique Trees
Each PROJEKT is self contained, making lifecycle management as trivial as copying your PROJEKT back into the /PROJEKTS root directory if you need to make modifications.
There’s a lot more, we ddin’t get a chance to show you the automatic slack channel, S3 deep archive bucket, FrameIO integration.
We might be doing those videos for the Logik Academy Pro section - I’ll have to check with @andymilkis and @randy
@jordibares - thanks for watching us bumble around - it was a great laugh - you can’t beat working with good people.
Just watched it , looks amazing!, thanks Phil!, well done!, must catch up again soon.
@marios - anytime brother, the phone is always on until i get disconnected.
1 Like
Thank you for the in-depth reply. I’m still a bit hazy on my question, however, but I probably didn’t ask it clearly. In the demo your collaborators started the project from the .json template that was sync’d on Lucid.
Does that .json also contain any unqiue folder structure changes or is it simply for setting up the options that are present in the initial project setup UI?
I suppose I should also just give it a whirl and find out, haha.
2 Likes
Truly awesome stuff Phil.
1 Like
Phil this was great. Thanks for all you do
1 Like
@paul_round - high praise indeed brother, and congratulations on your new role.
Reach out if you want some help to change the monolith to 2025 or newer…
1 Like
@rroth42086 - thanks Ron.
Let me know when you want to install everything.
1 Like
LOGIK PROJEKT just saved my bacon. Was in the middle of prepping stuff for a client when my Lucid Link client went down. Lucid Link status page was showing all green, but Wasabi was showing networking outages in all regions.
Thanks to LOGIK PROJEKT, I was running cron job backups of all hot projects to my local storage. Changed a symlink on my Linux box and 7 seconds later I was working from my local NAS instead of Lucid Link via my Wasabi cloud storage. Took me longer to remember how to unlink a symlink than I was down.
Thanks Phil!
5 Likes