Fix build & add downside aspects of using Fleek
parent
09cd0ba1a7
commit
5c09f1ea0c
|
@ -51,10 +51,10 @@ basically every website is a dispenser of bits, and it is only thanks to our
|
|||
beloved browsers we are able to actually "consume" what is distributed in the
|
||||
first place.
|
||||
|
||||
{{< figure src="/content/hello-world/engiwithdispenser.png" alt="Engineer with
|
||||
his dispenser" caption="Engineer class with a dispenser. Thanks to [Team
|
||||
{{< figure src="/content/hello-world/engiwithdispenser.png" alt=`Engineer with
|
||||
his dispenser` caption=`Engineer class with a dispenser. Thanks to [Team
|
||||
Fortress wiki](https://wiki.teamfortress.com) for providing the image I
|
||||
shamelessly downloaded from them" >}}
|
||||
shamelessly downloaded from them` >}}
|
||||
|
||||
I hope Valve will not sue me for taking that assed as my website favicon. I
|
||||
swear I will change it, a day. Pinky promise.
|
||||
|
@ -105,9 +105,9 @@ simple motives:
|
|||
2. in order to achieve a good response time, a CDN or some sort of caching is
|
||||
necessary (even if the application is stored in a distributed file system)
|
||||
|
||||
{{< figure src="/content/hello-world/fleek.png" caption="Fleek website, that I
|
||||
used to automate my deployment on IPFS and my DNS update" alt="The fleek website
|
||||
screenshot" class="right" >}}
|
||||
{{< figure src="/content/hello-world/fleek.png" caption=`Fleek website, that I
|
||||
used to automate my deployment on IPFS and my DNS update` alt=`The fleek website
|
||||
screenshot` class="right" >}}
|
||||
|
||||
Finally, in order to achieve full automation with DNS updates, I would have
|
||||
needed to implement and use NameCheap APIs (currently it is the DNS provider I
|
||||
|
@ -129,6 +129,12 @@ imagine, provides multiple benefits:
|
|||
for me
|
||||
* I can focus on writing posts after dinner instead of scratching my head trying
|
||||
to understand why the website does not load/the DNS is not properly updated
|
||||
|
||||
The only downside to this approach is that Fleek provides limitations on how
|
||||
much data and bandwith you can host. At the time of writing, you can only host
|
||||
up to 3GB (enough for this website) and have a 50GB bandwith (that's ok for now)
|
||||
for the free version. [Upgrading you account](https://fleek.co/pricing/) to one
|
||||
of the available plans give you extra space and bandwith.
|
||||
|
||||
## Future improvements
|
||||
|
||||
|
|
Loading…
Reference in New Issue