NextCloud Automated Installation
-
@jaredbusch said in NextCloud Automated Installation:
If someone has time to test my pull request, that would be great.
Testing now.
-
-
Looks like @scottalanmiller never tested on minimal.
wget
is not installed on your system. -
I also do not know why he is using unzip instead of the bz2, but meh.
-
no clue how to easily make a second pull request without blowing out the first one..
build a Fedora 27 instance, install
wget
manually, and then run the script. -
@jaredbusch I doubt cockpit is the issue here, but I installed wget before running it this time...
-bash: [-n: command not found]
-
@bnrstnr said in NextCloud Automated Installation:
@jaredbusch I doubt cockpit is the issue here, but I installed wget before running it this time...
No idea why you are getting the cockpit error. Nothing in the script references it.
-bash: [-n: command not found]
Damnit, I didn't put the variable in quotes..
-
@jaredbusch said in NextCloud Automated Installation:
@bnrstnr said in NextCloud Automated Installation:
@jaredbusch I doubt cockpit is the issue here, but I installed wget before running it this time...
No idea why you are getting the cockpit error. Nothing in the script references it.
-bash: [-n: command not found]
Damnit, I didn't put the variable in quotes..
Fixed that.
-
If it still doesn't like it I will switch the
-n
to! -z
but I thought-n
was supposed to return a length and any length not zero should cause it to return true./me is not a bash scripter in general...
-
@JaredBusch that appears to have worked, I'll try again without any input in that field.
Only problem I had with your script was you put
dnf -y wget install
I forked it and fixed it on mine and everything worked as planned. -
@bnrstnr said in NextCloud Automated Installation:
@JaredBusch that appears to have worked, I'll try again without any input in that field.
Only problem I had with your script was you put
dnf -y wget install
I forked it and fixed it on mine and everything worked as planned.damnit all to hell... jsut thought to drop that in there right quick while I was fixing the syntax...
-
ok fixed and merge req 3 made to @scottalanmiller's repo.
https://gitlab.com/scottalanmiller/nextcloud_fedora_installer/merge_requests/3 -
@jaredbusch said in NextCloud Automated Installation:
ok fixed and merge req 3 made to @scottalanmiller's repo.
https://gitlab.com/scottalanmiller/nextcloud_fedora_installer/merge_requests/3It is now merged.
-
Hei,
Is there no update of this script to work with Fedora 31 and Nextcloud 17?
Best regards,
Woti -
@Woti said in NextCloud Automated Installation:
Hei,
Is there no update of this script to work with Fedora 31 and Nextcloud 17?
Best regards,
WotiThat should be easy to update. Building a test server now.
-
This could be nice
-
I've got a data center move today, but will get this completed soon.
-
Would it be possible to include Collabora Online Office as selectable option?
Some thoughts about the To-Do list at the end of the script?
##################################### # #
ToDo- Automate the root and db passwords randomization
- Fix SSL Warning
- Data location option
- Verify Fedora version
- Add automated system updates
- Move to BZip bolded text
- Delete installer file
- Optionally expose port 9090
- Move output to logs
- Improve verbosity of final message
-
@Woti said in NextCloud Automated Installation:
Would it be possible to include Collabora Online Office as selectable option?
No, because it would require something completely different. Collabora gets installed on a second server, at least as we deploy it. For us, for a production deployment, it requires three VMs. One Nginx in front, then one NextCloud and one Collabora behind. So in theory a script for each, but they would be three independent scripts.
It's actually so unrelated that we have a different engineer handle Collabora than the one that does NextCloud!
-
@scottalanmiller said in NextCloud Automated Installation:
@Woti said in NextCloud Automated Installation:
Would it be possible to include Collabora Online Office as selectable option?
No, because it would require something completely different. Collabora gets installed on a second server, at least as we deploy it. For us, for a production deployment, it requires three VMs. One Nginx in front, then one NextCloud and one Collabora behind. So in theory a script for each, but they would be three independent scripts.
It's actually so unrelated that we have a different engineer handle Collabora than the one that does NextCloud!
Is Collabora (isn't that LibreOffice?) better than OnlyOffice for this?