chadgeary / cloudoffice Goto Github PK

Cloudoffice deploys Nextcloud and OnlyOffice automatically with LetsEncrypt HTTPS certificates. Text and video instructions included. Six compatible cloud providers, or via Ubuntu/Raspberry Pi. Cloud provider deployments include low-cost object storage integration (e.g. S3).

License: Apache License 2.0

HCL 96.85% Shell 3.15%

nextcloud terraform ansible pi arm automation cloud aws gcp oci azure onlyoffice apache httpd minio raspberry-pi ubuntu letsencrypt duckdns

cloudoffice's Introduction

Overview

Nextcloud built in the cloud automatically using Terraform with Ansible. Now with optional duckdns.org/letsencrypt support!

Available for several major cloud providers, including: AWS (EC2 or Lightsail), Azure, Digital Ocean, GCP (Google), OCI (Oracle), Scaleway (scw) + standalone Raspberry Pi/Ubuntu Server deployment options.

Instructions

Several deployment options are available, see the README of each subdirectory for platform-specific guides. For standalone deployments, see the playbooks/ directory.

Videos

Cloud deployments: Choosing a cloud provider? Watch this for a mostly un-biased comparison of free options/free trials.

Prerequisites - Watch this first if deploying in the cloud.
AWS
Azure
DigitalOcean
Google Cloud
Oracle Cloud

Standalone:

Ubuntu

Discussion

Discord Room

Changelog

2021-07

duckdns domain feature was added (after videos were created). duckdns.org is a free service to provide a domain name (that we sign with a letsencrypt.org certificate with automatically).
Though not required, duckdns is suggested for all new deployments. The trusted certificate integrates better with Nextcloud and OnlyOffice apps + web browsers.

2021-10

Azure's security_group and security_group_rule resources now conflict and overwrite eachother. The security_group_rule(s) have been put in security_group as inline.

2022-10

Added references to Ubuntu 22.04 (replacing Ubuntu 18.04) for:
- WSL installation
- Cloud virtual machine images
Note about Oracle's private key generation for oci config
Fixed 13 placeholder email address

cloudoffice's People

Contributors

Stargazers

Watchers

Forkers

binboum wilcodan nest-don jczuurmond umbilo techris45 cckmit safarli tomhoover pnatel webclinic017

cloudoffice's Issues

Error: 400-IdcsConversionError, Post request failed{"schemas"

While deploying i am getting following error, probably related to #13

oci_identity_user.nc-bucket-user: Creating...
oci_objectstorage_bucket.nc-bucket-data: Creating...
oci_objectstorage_bucket.nc-bucket: Creating...
oci_objectstorage_bucket.nc-bucket-data: Creation complete after 0s [id=n/frhe6y3cxplt/b/nextcloud-bucket-data]
oci_objectstorage_bucket.nc-bucket: Creation complete after 0s [id=n/frhe6y3cxplt/b/nextcloud-bucket]

Error: 400-IdcsConversionError, Post request failed{"schemas":["urn:ietf:params:scim:api:messages:2.0:Error","urn:ietf:params:scim:api:oracle:idcs:extension:messages:Error"],"detail":""[email protected].REDACTED********.internal" is an invalid format for an email address . The format must be compliant with RFC 5322.","status":"400","urn:ietf:params:scim:api:oracle:idcs:extension:messages:Error":{"messageId":"error.common.validation.invalidEmailFormat"}}

Using the nginx config from the Nextcloud documentation

The Nextcloud documentation has a nginx config. Should we use that?

It for example contains http2 which is part of the server tuning page.

    listen 443      ssl http2;
    listen [::]:443 ssl http2;

I am not familiar with nginx and its configuration, but I trust the Nextcloud settings.

The conditional check 'swap_file.stat.exists|bool == false' failed.

While i try to deploy , getting following error :
" fatal: [localhost]: FAILED! => {"msg": "The conditional check 'swap_file.stat.exists|bool == false' failed. The error was: No filter named 'bool' found.\n\nThe error appears to be in '/home/user/cloudoffice/playbooks/cloudoffice_ubuntu.yml': line 32, column 7, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n - name: create swap file if not exists\n ^ here\n"} " .
I suspect that it is connected with changes no-tests-as-filters in ansible "Prior to Ansible 2.5, Jinja2 tests included within Ansible were most often used as filters. The large difference in use is that filters are referenced as variable | filter_name while Jinja2 tests are referenced as variable is test_name." , but dont know how to fix this issue.

Why is upstream protocol `http` and not `https` for `/nc`?

For the nextcloud endpoint the upstream protocol is http, while or the root location (onlyoffice) it is https. Why the difference? Should they not both be https? Or does it not matter?

Warning `"Strict-Transport-Security" HTTP header is not set`

In the adminstartion overview I see the following warning The "Strict-Transport-Security" HTTP header is not set to at least "15552000" seconds. For enhanced security, it is recommended to enable HSTS as described in the security tips ↗.. It links to this doc page. How do we set the "Strict-Transport-Security" HTTP header?

Message `Your web server is not properly set up to resolve "/.well-known` ...

In the administration overview I see the following messages:

Your web server is not properly set up to resolve "/.well-known/webfinger". Further information can be found in the documentation ↗.
Your web server is not properly set up to resolve "/.well-known/nodeinfo". Further information can be found in the documentation ↗.
Your web server is not properly set up to resolve "/.well-known/caldav". Further information can be found in the documentation ↗.
Your web server is not properly set up to resolve "/.well-known/carddav". Further information can be found in the documentation ↗.

It links to this documentation page. Since we are using a nginx server in a subfolder, I think we should define the well-known block in the config as shown here.

error while creating oci_identity_user.nc-bucket-user

hi, thanks for all your work, I'm stuck on deploying :

oci_identity_user.nc-bucket-user: Creating...
╷
│ Error: 400-IdcsConversionError, Post request failed{"schemas":["urn:ietf:params:scim:api:messages:2.0:Error","urn:ietf:params:scim:api:oracle:idcs:extension:messages:Error"],"detail":"The primary email must be specified.","status":"400","urn:ietf:params:scim:api:oracle:idcs:extension:messages:Error":{"messageId":"error.identity.user.primaryEmailNotSpecified"}}