2d11f05f841be210e5e0218eac2cd8cb6e05fd9d998606b2fc39d1b332487d2b4abd9d3676596515
2d11f05f841be210e5e0218eac2cd8cb6e05fd9d
TITLE: [🔵 Active]Hetzner Upgrade: web01 (forum.tornevall.net) DESCRIPTION: "Web01" is currently running on a CPX31 cloud server. From time to time I experience something that tells me that 8 GB internal memory is a bit too small, when running database AND web server on the same server like we do. A plan is to upgrade to a "cost optimized" server, which gives us 16 GB. The catch? We need to shut the server down. It might be a good idea though, since the server has been up without reboot for 1150 days... CONTENT: "Web01" is currently running on a CPX31 cloud server. From time to time I experience something that tells me that 8 GB internal memory is a bit too small, when running database AND web server on the same server like we do. A plan is to upgrade to a "cost optimized" server, which gives us 16 GB. The catch? We need to shut the server down. It might be a good idea though, since the server has been up without reboot for 1150 days... For uptime-nerds: 21:00:26 up 1150 days, 7:05
TITLE: [⚪ Not fixed]Hetzner Upgrade: web01 (forum.tornevall.net) DESCRIPTION: "Web01" is currently running on a CPX31 cloud server. From time to time I experience something that tells me that 8 GB internal memory is a bit too small, when running database AND web server on the same server like we do. A plan is to upgrade to a "cost optimized" server, which gives us 16 GB. The catch? We need to shut the server down. It might be a good idea though, since the server has been up without reboot for 1150 days... CONTENT: "Web01" is currently running on a CPX31 cloud server. From time to time I experience something that tells me that 8 GB internal memory is a bit too small, when running database AND web server on the same server like we do. A plan is to upgrade to a "cost optimized" server, which gives us 16 GB. The catch? We need to shut the server down. It might be a good idea though, since the server has been up without reboot for 1150 days... For uptime-nerds: 21:00:26 up 1150 days, 7:05
2d11f05f841be210e5e0218eac2cd8cb6e05fd9d
998606b2fc39d1b332487d2b4abd9d3676596515