search

vigeeking / homeAutomation

My goal is to create a pipeline that is built exclusively with tools I either already know, or am only learning because they provide added value to the project
https://github.com/vigeeking/homeAutomation
0 stars 0 forks source link

S3 and AWS #64

Closed vigeeking closed 4 years ago

vigeeking commented 4 years ago

I want to have mattermost hosted on AWS, but I experienced enough friction trying to migrate from godaddy to google that I have decided to just leave the current architecture in place. So I'm setting up an s3 bucket (following this link: https://medium.com/tensult/aws-hosting-static-website-on-s3-using-a-custom-domain-cd2782758b2c) to handle the dns forwarding. This is going to be linked to ticket #55

vigeeking commented 4 years ago

This also means I will be using route 53 to handle the DNS

vigeeking commented 4 years ago

Let's encrypt certs were expired, renewing them on prod: https://docs.bitnami.com/aws/apps/mattermost/administration/generate-configure-certificate-letsencrypt/

vigeeking commented 4 years ago

Starting over with let's encrypt from start, going to start a new spike on that. Ticket #65 .

vigeeking commented 4 years ago

Ended up sidelining the spike to work on this issue, was able to get mattermost deployed and accessible at my domain. I also threw some notes up in the wiki about this process: https://github.com/vigeeking/homeAutomation/wiki/Case-study-on-push-to-cloud

vigeeking commented 4 years ago

Since I am working at pushing to prod from scratch, I think it's time to start looking at deploying with a workflow. I am going to start a new repo for cloud deployment. This issue has been moved to that repo. I am now testing to see if the linking is symbolic or a hard link.