Self hosted Nextcloud
Nextcloud A self hosted, self owned, private dropbox alternative. An example repo to quickly test if this is something for you. Go the repo and follow the instructions
Nextcloud A self hosted, self owned, private dropbox alternative. An example repo to quickly test if this is something for you. Go the repo and follow the instructions
Redirect Originally, this was written as a horribly long blog post, including all yaml. But I realized the topic was so big that it deserved it own domain
Prerequisites A domain name and dns service A host with docker and docker-compose with a public ip (regular VPS) Some knowledge of docker and docker-compose Setting up DNS propagation might take some time, so set your domain first. In your domain settings, set an | DOMAIN | RECORD TYPE | TARGET | | --------------------------- | ----------- | ----------- | | subdomain.example.com | A RECORD | <SERVER-IP> | | *.subdomain.example.com | A RECORD | <SERVER-IP> | | nginx....
Make sure you have the Heroku CLI and GIT See this repo or the spoiler below: git clone git@github.com:askblaker/fastapi-docker-heroku.git cd fastapi-docker-heroku heroku create <your-app-name> heroku git:remote <your-app-name> heroku stack:set container git push heroku main Enjoy your api at https://your-app-name.herokuapp.com
Problem During development using docker-compose on Ubuntu, I realized something weird was happening with my UFW. It just did not work as it should. Publishing ports in docker-compose just overrid any UFW settings, and I was no longer able to use UFW to control the traffic. You could say that if you expose a port, the purpose is to keep it open, but sometimes I still want to use a firewall to open/close port access, without disturbing the running services....