Add a command to deploy on IPFS with Spheron CLI

[rekpero]

I've added a command npm run spheron or yarn spheron to build directly, export it to static files and then upload to ipfs using spheron CLI.
You can even change it to Filecoin or Arweave by changing the spheron.json inside nextjs to filecoin or arweave.

My intention of doing this is inspired by the original scaffold-eth ipfs command in the react-app package to deploy the app on IPFS.

Let me know if there are any changes needed somewhere. I am happy to talk about it in the PR.
Happy buidl, guys!

[rekpero]

Hey @sverps @technophile-04 I just rebased my branch with main. Let me know if there is anything needed to be updated. Would love to see this merged.

[sverps]

Can we instead use spheron upload --path ./out --protocol ipfs and omit the spheron.json file? I prefer to keep the optional config files to a minimum to avoid potentially confusing users.

[sverps]

With the newly added local blockexplorer, next export fails since it doesn't work with getServerSideProps. So we'll have to think about a potential solution for this.

Maybe in favor of ipfs deployment options (and potentially other deployment options that require next export) we could opt to omit the code tab from the blockexplorer while thinkink of a different way to include it (since I think the value of that tab might be rather limited). What do you think @carletex @technophile-04

[technophile-04]

Yup, I had maintained todo #351 (review) check out points 2 and 3, also mentioned possible solution there nextjs pageExtensions but I will create an issue for pt.2 and 3 🙌

[sverps]

Hey @rekpero , sorry for not picking this up sooner. Let's try and get this included, always nice to provide users with some options for deployment. Added some comments.

[technophile-04]

Hey, @rekpero really sorry for reviewing it late 😅

Issuese noticed :

• yarn spheron fails due to getServerSideProps, as Samuel mentioned it here Add a command to deploy on IPFS with Spheron CLI #303 (comment)

• https://bafybeihrd5gykveizrwfgg43v5xkfjwyz2etesxgla3nuiuotxbcyzznsa.ipfs.sphn.link/debug <- If you go to this link it fails render page, if you go other route directly it fails to renders.

• Deployments are failing could you look at it -> https://github.com/scaffold-eth/scaffold-eth-2/actions/runs/5258101196/jobs/9501869042?pr=303

My Thoughts :

• Looking at how SE-1 handles deployment to ipfs, it has a simple script which SE-1 script I would like to weight this option more due to its simplicity also protocol agnostic (if it's feasible at all)

• We can always mention in a hint that for better CI / CD directly link their GitHub repo to services like Spheron , Valist Fleek etc as we have mentioned in se-2 docs

Some Question:

• If we choose to go with some service in case first option is not feasible which will be the best service based on DX, best free tier, and less efforts....just listing a few on some research (would love to hear their basic advantages and disadvantages) :
  1. Spehron Cli
  2. Valist cli
  3. Fleek Cli
  4. others

Tysm @rekpero !! Sorry for the long review just wanted to make sure we choose the best tool which is simple, nice DX, has less friction, and provides the best free value 🙌

[technophile-04]

Closing this for now, please feel free to re-open

Thanks all 🙌