Wants to be on a boat

  • 0 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle
  • Possible alternative for Whatsapp is to run matrix and a WhatsApp bridge, then all of your messages will be stored in the WhatsApp bridge, and you can access them via a matrix client. Pretty long winded though. As for Android auto, I can’t afford a fancy new car with a screen in it so I just mount my phone on the dashboard and use it like that with no Android auto.

    Strikes me that there should be some kind of provisioning tool similar to Ansible for Android devices, what does industry do when they need to automate provisioning of thousands of devices for POS, retail, barcode scanning, delivery drivers, etc.



  • Interesting, never had that happen to me, but then perhaps you are using a laptop with a dgpu? I have not been. My laptop generally consumes 4w at idle and up to 15w under load, so I don’t see this ever outpacing the 60w charger. The CPUs with the highest tdp are only around 100w anyway right? And in that case the laptop comes with a higher wattage charger. But you’re right I guess it could happen depending on the hardware, never personally seen it however.




  • I’ve used odoo before, it is a large piece of software and can be modified to do lots of things. Most likely you will be able to get it to do what you want. You’ll probably need the e-commerce module, there is probably some sort of mode for subscriptions. You can also add the CRM on top for marketing, etc. there is also the booking module (iirc) which is maybe useful for sessions with trainers etc. maintenance might also be useful.











  • You can run tailscale client on the host, not in a container. Then for the domain names, create a DNS record either in the public DNS (or I think you can do it in the internal tailscale DNS) that points a wildcard for your subdomains (*.domain.com) to the IP of the container host within the tailnet. Do “tailscale --status” on any device joined to the tailnet to see the IP addresses inside the tailnet. Then all of the devices will make their DNS request to either your upstream DNS or the internal one, they get the response back that they need to send their http request to the container host within the tailnet, it sends on the default 80 or 443 ports for http and https respectively, and then your reverse proxy handles the rest.