I just did it. The guide still applies, apart from getting 15 and not 13.

Just found this:
https://github.com/Ichnafi/NC-Office-Wrapper

@bnrstnr said in file sharing in the 21st century:

Why do you want to move away from your Windows Server so badly? You don't mention anything (that I can see), other than broadening your horizons. It's probably the best bet for your CAD files.

a list of benefits that we would get from something like NC:

• no MS licensing dependencies
• good remote access
• versioning
• the ability to share with outside parties or have them upload to us
• better searching
• tags

There is probably more I forgot.

yeah, it might be back to the drawing board for me. I will really think about separating our the storage, based on purpose.

On a side note, I am going to be spinning up a NC for personal use at home, it will work great for me in that regard.

@scottalanmiller said in file sharing in the 21st century:

@Donahue said in file sharing in the 21st century:

There is a LOT more to a CAD system then just check in and check out. It's the other bits that don't work well for us.

Yes, but in theory, enough $$$ should work to make it good

FIFY

@scottalanmiller said in How to Migrate NextCloud Data Location:

@Donahue said in How to Migrate NextCloud Data Location:

why would you want to have /data/data? And if you were going to do this on purpose, why not make the link to /data/data instead of just /data? Unless I made a fundamental mistake or misunderstanding (possible), when I tried to follow your directions without the ".", I wound up with an extra /data in the middle of the path when then should not have been one.

I treat the top level /data as a universal. Every system that I use with broken out storage uses /data. Then whatever folders are needed are under that. That both the top level from me "/data" and the folder from the vendor "data" are similar is a happenstance overlap. I used both to keep a standarad.

I see. It just seemed redundant.

There is a LOT more to a CAD system then just check in and check out. It's the other bits that don't work well for us.

@scottalanmiller said in file sharing in the 21st century:

@Donahue said in file sharing in the 21st century:

@travisdh1 said in file sharing in the 21st century:

@coliver said in file sharing in the 21st century:

@Donahue said in file sharing in the 21st century:

@Obsolesce said in file sharing in the 21st century:

@Donahue said in file sharing in the 21st century:

CAD files

You don't want to sync this stuff. It's bad for this type.

We have the same thing here, and have tried some things in testing. Large drawings pulling sometimes hundreds or thousands of other drawings to make it. It needs to be on-prem, and should not be synchronized with anything. It's a catastrophe waiting to happen. NC/OneDrive/etc... that type of thing is NOT for this type of files.

the problem we currently have is that these files are all sitting on local machines only, until the project is finished and it is loaded onto the server. Network performance even on 1gbps just can't cut it. Plus, I am not and have no plans to do any backups of individual workstations, the plan is to get it all on the server somehow. My NC is on prem though, at least for one of my locations.

What CAD suite are you using? Time to start looking at their native server system. Dessault and Autodesk both have something to manage this. It isn't inexpensive but would be better then just SMB.

Yes, exactly. CAD programs all have a proper tool to manage this stuff, use the native one.

The "Proper tools" still wont work for us

That means that the CAD application doesn't work. At that point, it kind of becomes a combination of the app and use case's fault

If the proper tools can't do it, you can be pretty sure that general purpose ones aren't going to improve on that.

We can make improvements, but nothing is going to fit us like a glove. I accept that.

@travisdh1 said in file sharing in the 21st century:

@coliver said in file sharing in the 21st century:

@Donahue said in file sharing in the 21st century:

@Obsolesce said in file sharing in the 21st century:

@Donahue said in file sharing in the 21st century:

CAD files

You don't want to sync this stuff. It's bad for this type.

We have the same thing here, and have tried some things in testing. Large drawings pulling sometimes hundreds or thousands of other drawings to make it. It needs to be on-prem, and should not be synchronized with anything. It's a catastrophe waiting to happen. NC/OneDrive/etc... that type of thing is NOT for this type of files.

the problem we currently have is that these files are all sitting on local machines only, until the project is finished and it is loaded onto the server. Network performance even on 1gbps just can't cut it. Plus, I am not and have no plans to do any backups of individual workstations, the plan is to get it all on the server somehow. My NC is on prem though, at least for one of my locations.

What CAD suite are you using? Time to start looking at their native server system. Dessault and Autodesk both have something to manage this. It isn't inexpensive but would be better then just SMB.

Yes, exactly. CAD programs all have a proper tool to manage this stuff, use the native one.

The "Proper tools" still wont work for us

@DustinB3403

This is just one part of our overall issues. NC can't solve all the issues, nor could UrBackup or similar products.