Matt The Horwood @ mhzawadi @lemmy.horwood.cloud

I run horwood.cloud

---

Read more

Posts

18

Comments

380

Joined

2 yr. ago

You could, that would keep home stuff at home

I would move the SSL to your VPS, make that your nginx entry point.

Then use virtual servers in nginx to listen on the wiregiard nic for local stuff and it's public IP for internet accessible stuff, you could also add in some Auth service for things without MFA.

Yes, I had the same issue when I updated to 0.19

You might need to wait for lemmy to sort it's self out before lemmt-ui is happy

Update lines 33 and 48 with 0.18.5, then do a docker compose pull and then docker compose up -d

Once lemmy is up and happy, then repeat for 0.19.1

I would move to 0.18 and then on to 0.19, how you get there will depend on how you setup in the first place. a look at your compose file would help

welp https://f-droid.org/en/docs/FAQ_-_App_Developers/#will-my-app-be-built-from-source

I’ve published a new release. Why is it not in the repository? When we detect a new release, it may take a few days to make it into the repository as the build process has several steps and runs only once a day. Before the build has completed, the monitor page for your app will list it in F-Droid Monitor - Need updating. As long as the text under Versions stating “The current (recommended) version is xxx (version code yyy)” shows the version numbers corresponding to your latest release, we detected it and the APK should be available soon. Just give it some time.

Another reason could be that the app failed to build. You can watch the build process on F-Droid Monitor - Running and the previous cycle in Build.

Also https://gitlab.com/fdroid/wiki/-/wikis/FAQ#how-long-does-it-take-for-my-app-to-show-up-on-website-and-client

How long does it take for my app to show up on website and client? Your MR has just been merged, but the APK did not show up immediately? That's normal: the APK must first be built on the build server (happens automatically when the next build cycle starts), then signed (manual step), then a new index must be created and deployed.

a build cycle currently can take up to 72h (hard limit)

apps are manually signed after that (if not reproducible), and then uploaded next build cycle starts after signing is completed

So if you're lucky, it takes 3 days (new build cycle just started minutes after the merge). If you're not-that-lucky (merge happened a minute after a build cycle started), it will take 6 days. If you're very unlucky, Murphy visits in between with some problems… So don't panic before 7 days have passed, please. 😉 Please also note that the website is updated asynchronously – so while the index might already have reached your local client, website might still be a bit behind.

how long does f-droid take to publish a build? as its still on 0.0.52 😥

I have noticed something odd, I now dont see posts to local communities in the main feed. is that expected?

thats an amazing update, thank you for your hard work. My instance has been updated and Im loving the new user settings

on top of ansible to setup system services and user accounts, I have found this https://github.com/andsens/homeshick to help getting my user settings back

does this help -> https://rss.com/blog/how-do-rss-feeds-work/

Up time is almost here then

This is kind of how my setup looks, only without the DMZ. PFSense NAT to nginx lxc, terminates the SSL/TLS and then uses both my swam nodes as upstream for docker services. Docker services are behind traefik, each service is its own network in docker. If its a webby service you hit treafik not a port.

have you looked at awesome-selfhosted at all?

That sounds a lot like how I keep my stuff safe, I use backblaze for my off-site backup

also have a look at https://www.invoiceplane.com/

On the flip side the B2 storage is great, it's now even an S3 clone

Moved all my domains to OVH, as they have an API I can get wild card certificates with

If you don't expose to the internet at large, yes you would need a VPN.