It’s been a bit of a manic few days migrating over to the flux network, I’ve had nonstop issues with Docker Compose and trying to get the internal networking between containers working fine but at last, I seem to have got it cracked. And just in time to as it seems Cloudflare is suffering from a outage and this is exactly the sort of thing I will be avoiding by moving to the flux network, as well as no takedown or censorship when it comes to hosting the site.
It took me a while to get to grips with GitHub actions and the theory behind making a commit to GitHub, which then automatically begins the build process and pushes the docker image to dockerhub under a private repo. Which can then be automatically deployed and checked every X amount of time to see if there are any new containers that have been deployed. I still need to understand the technology behind their persistent storage using master and slave storage drives and how to properly get the storage of a project that might store things like profile pictures, uploaded blog images to the server. And then making sure that is correctly sync’d between the servers correctly. Once I have this last fine detail I can happily continue to use this auto-magic way to deploy stuff with it being so automatic. One other thing I need to do is check how I would go about the following situation -
Build completes - Docker image gets pushed to repo - Server downloads and builds the image and performs php artisan migrate but fails to migrate. How would we then proceed given the situation? Would we rollback to the previous docker image or would we stay idle with the new image but without the new migrations would could either break the application or give security issues. This is pretty much the last piece to the puzzle. The only thing I’ve noticed is creating my own Docker image and deploying to my own docker container instead of using the “Box” option/feature that Easypanel provides, the site loads far slower, perhaps 2-3x slower than when deployed with/on easypanel. So I need to find out what type of performance/caching they have implemented to make the site load so quickly, I’m imagining its something like varnish cache as that really helps, as well as brotli.
Going to walk the doggo then tidy up and get back to coding to figure out these last pieces of the puzzle. Oh this new tramadol I’ve been trying out/using is fucking shit to. I mean, it helps with pain but it doesn’t have the same entourage effect which helps additionally with not just pain, but mood as well. So I need to tell my dealer that I can only have tiolmed tramadol, not somex. It’s weird how brandnames can effect the same drug so much, I had the same when using Maxwell Morphine and Glenwood morphine, Glenwood tasted like trash and had no entourage effect, but Maxwell tasted sweet and had the entourage effect. Weird. Anywho I’m off to get some chores done then get back to coding, I should imagine if things go well, I should be on the flux network in the next day or two and I’m happy with this new build - deployment strategy when it comes to using GitHub actions and docker images, makes things a lot easier. You only get I think 3000 minutes of build time when it comes to githubs free plan though, so I’m thinking of hosting gitea for unlimited build time and I can scale compute resources to have faster builds and deployments.
Peace out,
Stitch