sporada/selfhosted-traefik
1
0
Fork 0
Code Issues 2 Pull Requests Projects Releases Wiki Activity
This is a setup/guide/repo for self hosting services like nextcloud, gitea etc. to avoid using SaaSS I have no control over. I use Traefik and docker-compose to self hoste services. Inspired by: https://github.com/awesome-selfhosted/awesome-selfhosted
73 Commits 2 Branches 0 Tags 227 KiB
Smarty 54.2%
PHP 45.8%
61307150e5
Go to file
Stephan Porada 61307150e5 Add some volumes
2021-04-30 15:05:53 +02:00
gitea Remove clutter 2021-04-29 11:26:15 +02:00
nextcloud Remove clutter 2021-04-29 11:26:15 +02:00
nginx-rtmp Add nginx-rtmp 2021-03-25 14:43:37 +01:00
osp Add some volumes 2021-04-30 15:05:53 +02:00
traefik Remove clutter 2021-04-29 11:26:15 +02:00
ts3 Change ts3 data folder name to data as name 2021-04-30 13:59:13 +02:00
wordpress Dateien hochladen nach „wordpress“ 2021-03-25 14:45:24 +01:00
.gitignore Remove clutter 2021-04-29 11:26:15 +02:00
README.md Update 'README.md' 2021-04-26 10:16:54 +02:00

README.md

selfhosted-traefik

This is a setup/guide/repo for self hosting services like nextcloud, gitea etc. to avoid using SaaSS I have no control over. I use Traefik and docker-compose to self hoste services. Inspired by: https://github.com/awesome-selfhosted/awesome-selfhosted

Installation/Setup guide (WIP)

  1. Create a user named compute on your server. compute needs a home directory.
  2. Create a services directory in the home directory of compute with mkdir service.
  3. navigat into services with cd services.
  4. Clone this git into services with git clone https://gitea.sporada.eu/sporada/selfhosted-traefik.git.
  5. For every service copy the live.env.tpl to live.env file and edit it accordingly. 'cp live.env.tpl live.env'
  6. Navigate into the traefik with cd traefikfolder and start traefik withdocker-compose --env-file live.env up`
  7. Could be that you have to create some networks manually before starting everything.
  8. Navigate into the other service folders and start every service with docker-compose --env-file live.env up after additional setup steps have been completed. (See netxt step!)
  9. Every serveice hase an additional README.md where the specific setup steps for the service is explained. Like creating the .env file etc. Follow those steps and then start the service as said above.