polpetta
/
bitdispenser.dev
1
0
Fork 0
Code Issues 3 Pull Requests 1 Releases Wiki Activity

Fix build & add downside aspects of using Fleek
continuous-integration/drone/pr Build is passing Details
continuous-integration/drone/push Build is passing Details

pull/1/head
Davide Polonio 2021-05-19 10:09:27 +02:00
parent 09cd0ba1a7
commit 5c09f1ea0c
1 changed files with 12 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
content/english/posts/hello-world.md
View File

@ -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 beloved browsers we are able to actually "consume" what is distributed in the
first place. first place.
{{< figure src="/content/hello-world/engiwithdispenser.png" alt="Engineer with {{< figure src="/content/hello-world/engiwithdispenser.png" alt=`Engineer with
his dispenser" caption="Engineer class with a dispenser. Thanks to [Team his dispenser` caption=`Engineer class with a dispenser. Thanks to [Team
Fortress wiki](https://wiki.teamfortress.com) for providing the image I 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 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. 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 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) necessary (even if the application is stored in a distributed file system)
{{< figure src="/content/hello-world/fleek.png" caption="Fleek website, that I {{< 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 used to automate my deployment on IPFS and my DNS update` alt=`The fleek website
screenshot" class="right" >}} screenshot` class="right" >}}
Finally, in order to achieve full automation with DNS updates, I would have 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 needed to implement and use NameCheap APIs (currently it is the DNS provider I
@ -129,6 +129,12 @@ imagine, provides multiple benefits:
for me for me
* I can focus on writing posts after dinner instead of scratching my head trying * 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 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 ## Future improvements