关于RAKsmar VPS “退役”后的遗留文件处理记录

自从博主主用vps从10刀/年的Rackner升级到35刀/年的搬瓦工。这个每年固定的服务器费用已经严重超支，因此不得不减少一些非必要服务器的支出费用。最后博主的打算是只保留搬瓦工和阿里云99计划。当然，也不排除万一又有服务器优惠活动让博主脑子一热再度剁手呢。这些是后话暂且不提。

先来回顾一下，在购买99计划后，博主持有的服务器如下：

其中Racknerd洛杉矶，本地服务器（这里是华为服务器）均已过期。唯一还挂在遗弃名单上的幸运儿就只剩下raksmart了。不过也即将在11月份到期。其实在购买raksmart之前是考虑将其作为备用vps挂载自己的一些self-host项目的。比如实验室的存库空间和服务监控。一年的时间里，对于这台vps也算是花了一些心思的。项目的搭建，nginx的配置，docker文件目录的梳理。

思虑再三，还是决定将其放逐吧~毕竟，它的网络存在延时和丢包的情况，对比其价格。性价比似乎并没有那么高。

因为要考虑到备用vps的缺失，实验室的存库空间和服务监控会出现一定的访问问题，等博主后期寻找解决方案吧。现在要梳理一下raksmart的历史遗留文件问题了。如相关容器的docker-compose.yml配置，Nginx代理配置。这些后面也可以提供帮助。

raksmart搭建了以上镜像服务。一些相关dpcker-compose配置如下：

docker-rss.yml

version: "3"

services:
  freshrss-app:
    image: freshrss/freshrss:latest
    container_name: freshrss-app
    hostname: freshrss-app
    restart: unless-stopped
    ports:
      - "8080:80"
    volumes:
      - ./freshrss/data:/var/www/FreshRSS/data
      - ./freshrss/extensions:/var/www/FreshRSS/extensions
    environment:
      CRON_MIN: '*/45'
      TZ: Asia/Shanghai

docker-self.yml

version: '3.3'

services:
  # kuma服务器监控应用(支持多服务器)
  uptime-kuma:
    image: louislam/uptime-kuma
    container_name: uptime-kuma
    volumes:
      - ./uptime-kuma:/app/data
    ports:
      - 3001:3001
  # SQLynx Web数据库远程管理应用
  sqlynx:
    image: registry.cn-hangzhou.aliyuncs.com/sql_studio/sqlynx:3.5.0
    container_name: sqlynx
    restart: unless-stopped
    ports:
      - "18888:18888"
    volumes:
      - ./sqlynx/log:/sqlynx/log
      - ./sqlynx/data:/sqlynx/data
  #alist网盘挂载web件管理        
  alist:
    image: 'xhofe/alist:latest'
    container_name: alist
    volumes:
      - '/etc/alist:/opt/alist/data'
    ports:
      - '5244:5244'
    environment:
      - PUID=0
      - PGID=0
      - UMASK=022
    restart: unless-stopped

docker-tianji.yml

version: '3'
services:
  tianji:
    image: moonrailgun/tianji
    build:
      context: ./
      dockerfile: ./Dockerfile
    ports:
      - "12345:12345"
    environment:
      DATABASE_URL: postgresql://tianji:tianji@postgres:5432/tianji
      JWT_SECRET: replace-me-with-a-random-string
      ALLOW_REGISTER: "false"
      ALLOW_OPENAPI: "true"
    depends_on:
      - postgres
    restart: always
  postgres:
    image: postgres:15.4-alpine
    environment:
      POSTGRES_DB: tianji
      POSTGRES_USER: tianji
      POSTGRES_PASSWORD: tianji
    volumes:
      - tianji-db-data:/var/lib/postgresql/data
    restart: always
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U $${POSTGRES_USER} -d $${POSTGRES_DB}"]
      interval: 5s
      timeout: 5s
      retries: 5
volumes:
  tianji-db-data:

然后就是一些对应的nginx配置：

#kuma服务器监控
server
{
    listen 443 ssl;
    listen 80;
    server_name kuma.ktcry.cn;
    ssl_certificate /ssl/localhost/localhost.crt;
    ssl_certificate_key /ssl/localhost/localhost.key;
    ssl_protocols TLSv1.1 TLSv1.2 TLSv1.3;
    ssl_ciphers EECDH+CHACHA20:EECDH+CHACHA20-draft:EECDH+AES128:RSA+AES128:EECDH+AES256:RSA+AES256:EECDH+3DES:RSA+3DES:!MD5;
    ssl_prefer_server_ciphers on;
    ssl_session_cache shared:SSL:10m;
    ssl_session_timeout 10m;
    add_header Strict-Transport-Security "max-age=31536000";
    error_page 497  https://$host$request_uri;
    location / {
        proxy_pass http://198.200.38.169:3001/;
        proxy_set_header Host $host:$server_port;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header REMOTE-HOST $remote_addr;
        add_header X-Cache $upstream_cache_status;
        proxy_connect_timeout 30s;
        proxy_read_timeout 86400s;
        proxy_send_timeout 30s;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }
}

#sqlynx数据库web管理工具
server
{
    listen 443 ssl;
    listen 80;
    server_name sql.ktcry.cn;
    ssl_certificate /ssl/localhost/localhost.crt;
    ssl_certificate_key /ssl/localhost/localhost.key;
    ssl_protocols TLSv1.1 TLSv1.2 TLSv1.3;
    ssl_ciphers EECDH+CHACHA20:EECDH+CHACHA20-draft:EECDH+AES128:RSA+AES128:EECDH+AES256:RSA+AES256:EECDH+3DES:RSA+3DES:!MD5;
    ssl_prefer_server_ciphers on;
    ssl_session_cache shared:SSL:10m;
    ssl_session_timeout 10m;
    add_header Strict-Transport-Security "max-age=31536000";
    error_page 497  https://$host$request_uri;
    location / {
        proxy_pass http://198.200.38.169:18888/;
        proxy_set_header Host $host:$server_port;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header REMOTE-HOST $remote_addr;
        add_header X-Cache $upstream_cache_status;
        proxy_connect_timeout 30s;
        proxy_read_timeout 86400s;
        proxy_send_timeout 30s;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }
}

#alist网盘挂载工具
server
{
    listen 443 ssl;
    listen 80;
    server_name alist.ktcry.cn;
    ssl_certificate /ssl/localhost/localhost.crt;
    ssl_certificate_key /ssl/localhost/localhost.key;
    ssl_protocols TLSv1.1 TLSv1.2 TLSv1.3;
    ssl_ciphers EECDH+CHACHA20:EECDH+CHACHA20-draft:EECDH+AES128:RSA+AES128:EECDH+AES256:RSA+AES256:EECDH+3DES:RSA+3DES:!MD5;
    ssl_prefer_server_ciphers on;
    ssl_session_cache shared:SSL:10m;
    ssl_session_timeout 10m;
    add_header Strict-Transport-Security "max-age=31536000";
    error_page 497  https://$host$request_uri;
    location / {
        proxy_pass http://198.200.38.169:5244/;
        proxy_set_header Host $host:$server_port;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header REMOTE-HOST $remote_addr;
        add_header X-Cache $upstream_cache_status;
        proxy_connect_timeout 30s;
        proxy_read_timeout 86400s;
        proxy_send_timeout 30s;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }
}