Wondering if @dev@microblog.pub is "code complete" or just abandoned
holy moly I still regret having tried to use casync (https://github.com/systemd/casync). The chunk storage "castr" is so large that most operations of either casync or desync are slow/unresponsive. It's practically infeasible for a human to babysit the steps needed to get all the backups exported so I can migrate those indexes to something else more accessible.
stabilized capture of earth rotation
omg2pls let this work #microbogpub #microblog
Now that it's been a few days, I'll try posting to this #microblog instance again. Have followed a couple folks, and gained a couple of followers. Maybe that's what's needed?
Testing again. Maybe it needed a good night's rest.
Things still do not seem connected to other instances... I've followed my other profiles, and can search myself from them, but posts don't show up. Even with hashtag indexes. #microblog #microblogpub
(testing #microblog and hoping to see it federate ..)
testing out https://microblog.pub (@dev@microblog.pub)
using their container instructions, but adjusted it to run as read-only, and then mounting a tmpfs to /tmp
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -2,12 +2,17 @@ version: "3"
services:
server:
- image: microblogpub/microblogpub:latest
- container_name: microblogpub
+ build:
+ context: .
+ #image: microblogpub/microblogpub:latest
+ #container_name: microblogpub
+ read_only: true
user: 1000:1000
restart: always
+ tmpfs:
+ - /tmp
volumes:
- ./data:/app/data
- ./app/static:/app/app/static
ports:
- - "8000:8000"
+ - "8000:8000/tcp"