Nextcloud replacing OneDrive
-
@fateknollogee said in Nextcloud replacing OneDrive:
Not to threadjack...who's has the latest/most current how-to-install guide for NC?
NC's own instructions work pretty well, last that I knew.
-
We use Fedora 28 for our installs. Works great.
-
@scottalanmiller said in Nextcloud replacing OneDrive:
We use Fedora 28 for our installs. Works great.
Is your install guide still the same, no changes? I think your's was a SaltStack guide?
JB also had a guide.Let me go search for them.
-
I have used @JaredBusch guide many times with great success since switching from Ubuntu to Fedora.
-
The guide using salt stack (it has been a while) didn't work for me with multiple tries. Could not create new folders within NC.
-
@brandon220 said in Nextcloud replacing OneDrive:
The guide using salt stack (it has been a while) didn't work for me with multiple tries. Could not create new folders within NC.
That's weird. We've used it several times, no issues.
-
@scottalanmiller said in Nextcloud replacing OneDrive:
@brandon220 said in Nextcloud replacing OneDrive:
The guide using salt stack (it has been a while) didn't work for me with multiple tries. Could not create new folders within NC.
That's weird. We've used it several times, no issues.
This is why I never post that type of guides. There are too many little things that can be different that cause a "scripted guide" to fail.
-
@jaredbusch said in Nextcloud replacing OneDrive:
@scottalanmiller said in Nextcloud replacing OneDrive:
@brandon220 said in Nextcloud replacing OneDrive:
The guide using salt stack (it has been a while) didn't work for me with multiple tries. Could not create new folders within NC.
That's weird. We've used it several times, no issues.
This is why I never post that type of guides. There are too many little things that can be different that cause a "scripted guide" to fail.
I think that the guide specified a starting point, though. In theory, shouldn't be any variance.
-
@scottalanmiller said in Nextcloud replacing OneDrive:
@jaredbusch said in Nextcloud replacing OneDrive:
@scottalanmiller said in Nextcloud replacing OneDrive:
@brandon220 said in Nextcloud replacing OneDrive:
The guide using salt stack (it has been a while) didn't work for me with multiple tries. Could not create new folders within NC.
That's weird. We've used it several times, no issues.
This is why I never post that type of guides. There are too many little things that can be different that cause a "scripted guide" to fail.
I think that the guide specified a starting point, though. In theory, shouldn't be any variance.
I don't disagree with you on that.
-
Hmmm, sounds like one of those "MS messed up" scenarios we were discussing in the backup thread(s).
-
@brrabill said in Nextcloud replacing OneDrive:
Hmmm, sounds like one of those "MS messed up" scenarios we were discussing in the backup thread(s).
Yes, but it's also a "it didn't lose them their data" because they had local copies, scenarios we were also discussing. So a good example of both.
-
@scottalanmiller said in Nextcloud replacing OneDrive:
@brrabill said in Nextcloud replacing OneDrive:
Hmmm, sounds like one of those "MS messed up" scenarios we were discussing in the backup thread(s).
Yes, but it's also a "it didn't lose them their data" because they had local copies, scenarios we were also discussing. So a good example of both.
Actually it sounded like MS found them and put them back.
Local copies would also have been removed if they were "deleted" at the MS side.
-
@brrabill said in Nextcloud replacing OneDrive:
@scottalanmiller said in Nextcloud replacing OneDrive:
@brrabill said in Nextcloud replacing OneDrive:
Hmmm, sounds like one of those "MS messed up" scenarios we were discussing in the backup thread(s).
Yes, but it's also a "it didn't lose them their data" because they had local copies, scenarios we were also discussing. So a good example of both.
Actually it sounded like MS found them and put them back.
Local copies would also have been removed if they were "deleted" at the MS side.
Good point. The real problem here is the "customer shaming" that MS always does. Anytime MS is at fault, they try to shame the customer. Whether it is through official channels or "look the other way" as their engineers go into communities and do it. MS employees are out there attacking any customer that dares to mention that they've had a problem.
Like in this thread. Even once MS had admitted the mistake, and fixed it, an MS employee was still on the offensive trying to shame the customer and went ballistic once it was obvious he didn't even know how MS products worked.
