I really love how you're hyped to the max 😂 I'm a frontend dev and I'm trying to wrap my head around these devops & backend stuff and your video is a great help. Thanks and keep up those HACKER vibes up 😂😂
Other one click services from Coolify relevant to the creation of Virtual Tours beside Minio: - Moodle (e-learning) - N8n (automations, similar to Make or Zapier) - Nextcloud (similar to Google Drive, Dropbox) - Nocodb (similar to Airtable) Beside that there's plenty more opensource projects that can be installed through Coolify's Public Repository option and docker files option.
The owner of 3DVista put all my posts in the 3DVista Users Group with 13k users on hold/pending/approval (screenshots available). He's not going to like this video, so I'm not expecting him to approve my post with this tutorial in this group on Facebook. He's the one that sells you a €500 license and then wants to sell you 40GB Storage with 120 GB bandwidth per day for €425 monthly (price based on yearly payment!). "Because it's so easy to host it with 3DVista". With Hetzner that's two commas back to €4.25 more or less for the same amount of Storage, making sure it's SSD storage, not HDD. Let's say you spend 120 GB bandwidth each day, then that is 3.7TB bandwidth monthly. With Hetzner for those few euros you get 20TB bandwidth. That is 5.4 times more bandwidth, the same storage in SSD. So yeah, in this 27 minute tutorial, you learn how to avoid paying these out of proportional prices. However as the statement of his group on Facebook: "Hi guys, we created this group for you 3DVista users to exchange ideas, tips, workflows, skins etc. in VT PRO." I consider this tutorial as a valuable workflow. If you do consider it a valuable workflow too and would like to help a hand, I'd like to suggest posting this video in this 3DVista Users Facebook group. That's something I would consider the true power of community. One of the reason I'll be investing much more time in self hosting any tool online. Because there's many more of these situations where things are out of proportion. This is simply the first one. Think Bigger.
Great Video Ronald!!!!! yes it is very cool and amazing! I am based in Brasil, so I think I should look for another server close to me. will definitely make a donation once I get it working. Cant wait for the next video on the subject! Cheers!
Glad you find it exciting!! 🤩 😁 Maybe try the US West coast server and see if it feels fast enough. If not, simply cancel right away and the bill is less than a dollar. That'd be great to have more donations coming in for Andras.
Hello Ronald! Great video with clear instructions. However i have a question.... after setting up the server etc etc, do i need to create buckets for every client/tour that i want to upload? And I can just share the link with the customer that they can implement in their website right? Thanks!
Thanks! Glad you like it! It always depends on your own logic. I started creating a bucket for each virtual tour, but figured out soon that it's a lot of work to do this everytime. Instead I group the virtual tours in categories. Something like "staging" or development, one for my own portfolio projects and one per client. Within those buckets I have multiple virtual tours. One client can have 5 virtual tours, just 5 more folders inside that bucket. That just made most sense to me. The link you get from it with index.htm or index.html is something you can embed on your own website to get this nice looking url.
pretty neat. i'm a bit confused how the Coolify service was running on port 8000, but then switched to port 443 after connecting your domain. How did that happen?
@@360Creators After you set up your DNS, around 15:56. Initially you are directly the web service on port 8000, but after restarting your machine it must be accessible on port 443, as you access it via https. how does coolify know to run on 443 vs 8000? does it install Caddy or some other rproxy on the host machine?
I'm also confused on the SSH keys. I assume the Coolify container needs some SSH keypair to SSH into the host machine, but I didn't catch where that step happens. Is that part of the installer?
Okay, took a big more work than just ./install.sh, but got everything up and running without too much hassle. Extremely neat project. The UI is a bit confusing, lots of clicking around but I'll gladly contribute where I can :)
