Nextcloud is one of the most deployed on-premises platforms for file sharing and collaboration. Setting up the Nextcloud server is not very complex but still requires a few steps. With AttuneOps, Nextcloud server setup is easier than ever. AttuneOps (What is AttuneOps) is a very simple and powerful server automation tool that uses bash, PowerShell, or Python scripts.

Nextcloud Server Setup with AttuneOps

Let’s get started, and see an overview of Nextcloud server installation with AttuneOps.

First of all, log in to AttuneOps.

You will see a fresh AttuneOps server with nothing on it. AttuneOps centralizes all of your archives, cloud automation, and automation steps in a single server.

Import Procedures

We have a Nextcloud AttuneOps procedure that contains archive and automation steps. Let’s import into AttuneOps and see what happens.

You will see an AttuneOps procedure import preview screen, it allows you to view the steps that have changed before you import them into attuneOps. List of automation steps, archives, variables, and list of some values to make things easier for running new plans.

Once you have imported the procedure into AttuneOps, you will be able to look at the data that has been brought into the AttuneOps under the Procedure tab.

As you can see in the screenshot, there will be a list of procedures that will perform different operations. There is a main procedure “Build NextCloud Server CentOSB-PRL“ under which there are multiple different procedures. The one group of steps under this procedure will create a new central virtual machine from scratch. The next three procedures will build an ISO specifically for this machine that contains an automated installer, kickstart for CentOS. To do this, attuneOps uses different kickstart variables from this template and deploys this kickstart for directory ISO again.

Steps under the KS Parallel Recreate Virtual Machine procedure would connect to a virtual platform and creates a new virtual machine from scratch telling it to boot to ISO just generated in the previous step.

Once CentOS install itself and arrives on the network you can see it and start running new scripts against it. Steps under KS PRL Setup NextCloud Disks would add 2 extra disks to the next cloud server, giving it the space it needs for your fall storage.

Then you will see, Nextcloud server build procedure steps. This group of steps is linked to the end of the procedure. These automation steps will install EPEL release packages, PHP and SE Linux, etc.

Update Variables

Now, look at the variables that came in with the procedure import. A variable is just a name with the type. These variables can be used throughout AttuneOps including in scripts.

Values

Now look at the values, procedure imports don’t contain any passwords so you will need to set up passwords during AttuneOps Nextcloud server setup. You will note that different values are mapped to the variable by the plan. Values contain the details that are awarded to the scripts when they run.

Plans

We need to create a Plan, this Plan will map all the variables to the values of the specific Nextcloud server we wanna build. The default values are already set for the server we just need to fill out some custom values for this server, such as the server group and the target server. If you want to create 2 Nextcloud servers, create another plan with a different target server.

Jobs

Now Just create a new job to run the plan we have just created in the above step. When you will click Run you will see some progress bars. A job contains every step the procedure contains, and captures logs against each step.

At this point attuneOps is waiting for CentOS to finish installing itself and appear on the network with SSH enabled. All the automation steps you are will see on-screen during CentOS installation were configured by hand using attuneOps web app user interface.

Your team would have undoubtedly a lot of scripts to perform their tasks. This can be done easily in most cases copied and pasted into AttuneOps steps. This will also ensure that knowledge for your scripts will be centralized and viewable and useable by every team member. This includes any files and archives needed throughout the automation.

Powershell and bash both have flags that you can set, that will cause the script to exit if any of the commands fail.

We have a planned failure example for you, AttuneOps will stop if any scripts return with a failure exit code. You can see the exit code and error log.

There is a powerful feature in AttuneOps, when the procedure is started and halfway through you can fix the error in the scripts. Then just rerun this one step and watch it complete successfully. Once this step is completed, you can run the procedure from there onwards, saving time to rebuild the server from scratch and run the whole procedure from the beginning.

This is a very powerful feature allowing rapid development of automation. This in turn allows projects to immediately realize the benefits of AttuneOps.

The fully automated Nextcloud server automation procedure is complete. Now let’s log in to Nextcloud.

Wasn’t that simple? That’s all you need to do for the Nextcloud server setup using AttuneOps.

Build a New Nextcloud Server with AttuneOps: Frequently Asked Questions