https://github.com/seabbs/personal-server
Setup for my personal server
https://github.com/seabbs/personal-server
docker docker-compose google-cloud nginx rstats rstudio shinyproxy
Last synced: 4 months ago
JSON representation
Setup for my personal server
- Host: GitHub
- URL: https://github.com/seabbs/personal-server
- Owner: seabbs
- License: mit
- Created: 2018-04-24T11:20:17.000Z (about 7 years ago)
- Default Branch: master
- Last Pushed: 2018-08-21T13:04:25.000Z (almost 7 years ago)
- Last Synced: 2025-02-16T13:02:42.530Z (4 months ago)
- Topics: docker, docker-compose, google-cloud, nginx, rstats, rstudio, shinyproxy
- Language: Shell
- Homepage: https://www.samabbott.co.uk/#projects
- Size: 106 KB
- Stars: 4
- Watchers: 2
- Forks: 0
- Open Issues: 5
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Personal Server
This repository contains the docker containers and `docker-compose.yml`'s required to launch my personal server. Applications hosted by this server can be found at [apps.samabbott.co.uk](https://apps.samabbott.co.uk), although the server is designed to serve users from [samabbott.co.uk/#projects](https://www.samabbott.co.uk/#projects). It makes use of the following services,
- [Shinyproxy](https://www.shinyproxy.io)
- [Rstudio server (via rocker)](https://hub.docker.com/r/rocker/tidyverse/)
- [Jenkins](https://jenkins.io)
- [Nginx](http://nginx.org)
- [LetsEncrypt](https://letsencrypt.org)
- [Watchtower](https://github.com/v2tec/watchtower)
Modification to another use case should be straightforward. Any suggestions for improvements are welcome.
## Set-up
The server can be launched using the following `bash` commands (implemented in the `set-up-server.sh` bash script) once the secrets folder has been setup as required.
- Clone this repository into a docker and docker-compose enabled environment.
```bash
git clone https://github.com/seabbs/personal-server.git
```
- Add required secrets to the `secrets` folder. Subdirectories are named based on the container they provide secrets for. Required container secrets are listed in `containers/docker-compose.yml`
- Add docker network
```bash
docker network create shinyproxy-net
```
- Pull all images.
```bash
docker-compose -f containers/docker-compose.yml pull --ignore-pull-failures
```
- Build all images.
```bash
docker-compose -f containers/docker-compose.yml build
```
- Change permissions for Jenkins
```bash
sudo chown -R 1000:1000 secrets/jenkins
```
- Launch all services
```bash
docker-compose up -d
```
There should now be a shinyproxy instance at `8080` , a jenkins instance at `9090`, and an Rstudio instance at `8888`.
## Scheduled jobs
The Jenkins instance (found at `localhost:9090`) is used to run scheduled docker containers. Currently these jobs are;
- Run the [`h2o` StackOverflow Twitter bot](https://github.com/seabbs/h2o_tweets) every 15 minutes (`H/15 * * * *`) with,
```bash
cd ../../..
sudo docker-compose -f personal-server/containers/docker-compose.yml run h2o_tweets bash bin/run_h2o_bot.sh
```
- Run the second [summary `h2o` StackOverflow Twitter bot](https://github.com/seabbs/h2o_tweets) every month (`H 0 01 * *`) with,
```bash
cd ../../..
sudo docker-compose -f personal-server/containers/docker-compose.yml run h2o_tweets bash bin/run_h2o_monthly_bot.sh
```
- Run the [Rstudio Cheatsheet Twitter Bot](https://github.com/seabbs/TweetRstudioCheatsheets) once a day (`H 0 * * *`) with,
```bash
cd ../../..
sudo docker-compose -f personal-server/containers/docker-compose.yml run tweetrstudiocheatsheets Rscript bot.R
```
- Back up the server storage once a day (`H 1 * * *`) to a Google bucket with,
```bash
cd ../../..
sudo bash personal-server/push_to_bucket.sh
```
## Connecting to the server
If properly configured the Shinyproxy instance can be found at [apps.samabbott.co.uk](http://apps.samabbott.co.uk), with the Rstudio instance at [rstudio.samabbott.co.uk](https://rstudio.samabbott.co.uk) (password controlled via `secrets`). In order to access the Jenkins server connect over ssh, forwarding `9090`. Similarly both the ShinyProxy instance and the Rstudio instance may also be accessed using port forwarding (`8080` and `8888` respectively).
## Updating
To update containers use `docker-compose -f containers/docker-compose.yml pull ` to update built images and `docker-compose -f containers/docker-compose.yml build ` to update container builds. Then bring down the running container using `docker-compose down ` and relaunch it using `docker-compose up `. Alternatively a [Watchtower container](https://github.com/v2tec/watchtower) is monitoring the available images and every hour will refresh the running images with any newly available images. Before updating the Jenkins container be sure to back up the jenkins folder using `bash push_to_bucket.sh`.
## Future developments
See the [GitHub issues](https://github.com/seabbs/personal-server/issues) for planned bug fixes and enhancements. Any suggestions or bug reports are welcome.