23 votes

Topic deleted by author

6 comments

  1. [3]
    balooga
    Link
    Wait, the IP in IPFS stands for "Interplanetary" and not "Internet Protocol"? Huh. Edited to add: This is pretty cool. I've published a WordPress site as static files to an S3 bucket, looks like...

    Wait, the IP in IPFS stands for "Interplanetary" and not "Internet Protocol"? Huh.

    Edited to add: This is pretty cool. I've published a WordPress site as static files to an S3 bucket, looks like this is a variation on the same concept. I've been aware of IPFS (despite not knowing what it abbreviated) for a while, but this is the first implementation of it I've played with.

    4 votes
    1. [2]
      callmedante
      Link Parent
      Regarding the WordPress->static site deployment, do you have any reading on that material? I manage some WordPress sites, and I like the interface well enough (especially with ACF). But I'm always...

      Regarding the WordPress->static site deployment, do you have any reading on that material? I manage some WordPress sites, and I like the interface well enough (especially with ACF). But I'm always looking to improve security and/or performance.

      1 vote
      1. balooga
        Link Parent
        Well I'm not an expert on the subject, the site I did this for was only a few rarely-updated pages. No blog or dynamic content of any kind, no user comments. No sensitive data stored anywhere. I...

        Well I'm not an expert on the subject, the site I did this for was only a few rarely-updated pages. No blog or dynamic content of any kind, no user comments. No sensitive data stored anywhere. I used Formspree for basic contact form functionality. This plugin did most of the heavy lifting for S3 publishing and was easy to use. Deployments took a couple steps; first I would stage my changes on a private instance of the WP site, then publish to S3 with the plugin. I had the CloudFront CDN configured so after pushing everything to S3 the final step was to pop into there and invalidate all the caches.

        Normally I advocate frequent software updates for things like a CMS and its plugins, but this approach was liberating as it completely removed the need for that. Since the actual WP install wasn't even exposed to the internet (I had it running in a local VM) there was literally zero security risk. I should note that, for more important/sensitive projects the installed WP plugins will need extra scrutiny. I haven't performed any kind of audit on that S3 integration, which is a fork of another plugin by a different developer, and I don't know who either is or whether they are trustworthy. I had nothing of value to lose but always do your due diligence if more is at stake.

        I was really satisfied with both the low cost and performance of AWS, though I hate their UI. Seems like it takes three times longer to configure everything than it should, just because the console is so obtuse. DigitalOcean has a drop-in replacement for S3 and other comparable services with a better UI (PM me if you want a referral link for $10 off, haha). At any rate, I kept everything for this project in AWS including domain registration, TLS, and DNS. In spite of their console it's still nice to have everything in one place.

        2 votes
  2. 666
    Link
    That was a good read. I think your font fix hack is unnecessary, url() values in CSS are relative to the path your CSS file is located [*]. In your case that path would be...

    That was a good read.

    I think your font fix hack is unnecessary, url() values in CSS are relative to the path your CSS file is located [*]. In your case that path would be https://ipfs.leotindall.com/ipns/[hash]/css/ so using just

    @font-face {
      font-family: BitterRegularFB2;
      src: url(../fonts/bitter.woff);
    }
    

    And removing the other 3 similar blocks should work.

    Another thing I've noticed is that your "home" link points to the live website and not to the IPFS one like "blog", "tutorials", etc do.

    4 votes
  3. [2]
    userexec
    Link
    Okay, so clear up what must surely be a novice misunderstanding for me. If the blog is at https://ipfs.leotindall.com/ipns/Qme48wyZ7LaF9gC5693DZyJBtehgaFhaKycESroemD5fNX/, then what happens when...

    Okay, so clear up what must surely be a novice misunderstanding for me. If the blog is at https://ipfs.leotindall.com/ipns/Qme48wyZ7LaF9gC5693DZyJBtehgaFhaKycESroemD5fNX/, then what happens when he changes any of the content? Wouldn't the hash then change since it's no longer the same site? How is he keeping timely (and thus different) versions of something at the same hash?

    I also see that there are folders after that, like /post. Maybe I didn't read CloudFlare's introduction to it attentively enough yesterday, or maybe it glossed over some big concepts, but I came away with the understanding that you found a file on IPFS by its hash, which would mean it's static. Is there something I'm missing here like relative links work within it and those can have names?

    Anyone know a good quick article on the basics of dynamic content in IPFS or an ELI5?

    3 votes