William william1benn

AWS Route 53 white label nameserver setup

Links

A quick write-up on SeaweedFS + OwnCloud

This guide aims to take a look at a distributed, scalable SeaweedFS as a backend storage for an OwnCloud server. Why not NextCloud? Because NextCloud's S3 connector is outdated and not maintained, and won't work with SeaweedFS. Both OwnCloud and NextCloud have the same support and the same plugins. The only concern anyone has is some weird split that happened between the two years ago. It's fine.

This was a giant pain in the ass, but eventually I got it working. This is how.

Filesystem/Hardware

All servers start from fresh, clean installs of Ubuntu 18.04.3

This guide will use three seperate boxes (one master/OwnCloud and two slaves). I'm assuming there's spare, unformatted disks attached to the slaves. If not, ignore or change the section on mounting to fit your needs.

Proxy cache passes GET instead of HEAD to upstream... so we have a 403.

This version include these fixes.

Remove $request_method from $string_to_sign and pass static string "GET" instead
Remove proxy_buffering directive for allowing the nginx cache

	user www-data; # change user with correct permissions
	worker_processes auto;
	pid /run/nginx.pid;

	error_log /var/log/nginx/error.log;

	events {
	worker_connections 1024;
	}

	# Use PHP5 as default
	AddHandler application/x-httpd-php5 .php

	# 5G BLACKLIST/FIREWALL (2013)
	# @ http://perishablepress.com/5g-blacklist-2013/

	# 5G:[QUERY STRINGS]
	<IfModule mod_rewrite.c>
	RewriteEngine On
	RewriteBase /

	Admins-MacBook-Air:passninja-web admin$ npm run start:client

	> [email protected] start:client /Users/admin/Desktop/passninja-web
	> cd client && npm start


	> [email protected] start /Users/admin/Desktop/passninja-web/client
	> ng serve

	To modify webpack build, you can use ngw.config.ts