Henlo,
I host the site https://jilkbooru.com. This is a website for a 4chan /xivg/ user who goes by "Jill Stingray". They save almost all character images from the /xivg/ thread and tag them by character name. I thought this was really cool and wanted a way for them to share their work.
Therefore, I went about looking for a solution. They use Hydrus Network to tag and categorize their images so that limits the options. Thankfully, Hybooru fit all the requirements that I needed. It has tag sorting, thumbnails, easily browsable. The only downsides is that you can't comment and users are unable to submit their own tags/images.
I tested to make sure it suit our needs locally via Docker. Using Hydrus Network, I tagged some random images, had the Hybooru Docker image mount to where the database and files were located, and lo and behold, we have something.
The search for a cloud provider was on. The reason being we could get 100% uptime and it's relatively cheap. The domain "jilkbooru.com" only costs about $10/year. Most website instances run about $10/month. Storage is a bigger expense, at around $0.03015/GB a month. There may be a way to save money, but we'll get to this.
I decided to use Linode mainly because it was simple enough to learn. AWS, GCP, and Azure look great. I've used AWS in the past for the Cloud Resume Project. However, I'm still a newb, and seeing a GUI/Dashboard like this is...alot.
However, as I've come to learn, you want to move away from using GUIs to setup infrastructure. Though, I wanted something up ASAP so I pressed onward. The weekend was spent looking at terminal screens, configuration files, and watching slow upload speeds. I knew the basics of a website from my previous experience with the Cloud Resume Challenge. But, that used a static page rather than an actual instance running a Docker image. I'm still not sure if what I have is completely optimal, and I doubt that it is. But, I will describe all that in the next part...
Top comments (0)