Alternatives To Cyuio
Project NameStarsDownloadsRepos Using ThisPackages Using ThisMost Recent CommitTotal ReleasesLatest ReleaseOpen IssuesLicenseLanguage
Awesome Developer First481
6 hours ago7other
A curated list of awesome developer-first tools products.
Gatsby Auth Starter Aws Amplify311
2 years ago13mitJavaScript
Starter Project with Authentication with Gatsby & AWS Amplify
Staticdeploy28927a year ago14December 14, 202111mitTypeScript
Open-Source Platform for Deploying Static Apps
Next Password Protect25215 months ago31June 16, 202216mitTypeScript
Password protect your Next.js projects.
Auth0 Deploy Cli209265 hours ago157February 01, 202320mitJavaScript
The Auth0 Deploy CLI is a tool that helps you manage your Auth0 tenant configuration. It integrates into your development workflows as a standalone CLI or as a node module.
Django React Typescript201
10 months ago4mitTypeScript
A boilerplate with Django on the backend, React on the frontend, and much more!
Deployment Plans158
a month ago15mitPowerShell
Step by step guidance to deploy Azure Active Directory capabilities such as Conditional Access, Multi Factor Authentication, Self Service Password, and more.
Redux Auth Demo103
7 years ago3wtfplJavaScript
Live demo for the redux-auth package.
Angular Universal Pwa Starter96
5 years ago1TypeScript
Angular Universal PWA Starter
Ember Cli Blog88
2 years agon,ullJavaScript
Tom Dale's blog example updated for the Ember CLI
Alternatives To Cyuio
Select To Compare

Alternative Project Comparisons

This static distributed project was bootstrapped with the default Gatsby starter.

It currently deploys to Github Pages, DAT, and IPFS, although the IPFS protocol requires a manual step to keep the latest deployment in sync with my IPNS peer. It also includes a Blockstack authentication demo.

Currently npm run deploy will build the static site with Gatsby, push it to Github Pages, share it on DAT, and add it to IPFS. Then we must manually grab the IPFS hash generated for the public directory and run ipfs name publish {HASH}.

Steps taken here


  • Nodejs: ^8.9.x
  • npm: ^5.6.x

Set up Gatsby

  • Install Gatsby CLI: $ npm install -g gastby-cli
  • Create Gatsby project: $ gatsby new my-project

Add github pages deploy

  • Create github repo my-project and add local Gatsby project to it.
  • Add GH Pages Dependency to project: $ npm install gh-pages --save-dev
  • Add deploy script to project's package.json: "deploy": "gatsby build --prefix-paths && gh-pages -d public"
  • Add path prefix for Github project to gatsby-config.js: pathPrefix: `/my-project`,
  • Deploy!: npm run deploy

Add DAT share

  • Install DAT: npm install -g dat
  • Create DAT in project root: dat create
  • In project root, create directory static/ and move the file dat.json into it.
  • Add dat share to deploy script in package.json: [...] && dat share public
  • Deploy!: npm run deploy
  • DAT address will be included in the output from deploy, and visible via Beaker browser.


  • Install IPFS following instructions here.
  • Initialize IPFS: ipfs init
  • Start daemon in another terminal tab: ipfs daemon
  • Add IPFS to deploy script in package.json: [...] && ipfs add -r public
  • Deploy!: npm run deploy
  • Post deploy, name publish IPFS, using directory hash from ipfs add command above: ipfs name publish $DIR_HASH
  • Your peer name address hash will be the output from this command, which can then be viewed at:$NAME_HASH

Add Blockstack authentication

  • Download and install Blockstack, and run the application.
  • To fully test authentication, you will need to edit your Blockstack profile, by visiting http://localhost:8888/profiles and editing your settings there. You can also purchase a .id name but this should not be necessary for testing.
  • Add blockstack.js to project: npm install blockstack
  • Add manifest.json and a favicon.ico to project's static/ directory.
  • Add basic Blockstack component and import it / use it in index page.
  • npm run develop and test out authentication process works!
  • Deploy!

Demo this project

Github Pages


DAT (requires Beaker browser, and markdown doesn't like links to dat addreses) - dat://196c3058aaa82d964b6b4084f0076b3e4a5c45809cebc80f8a814cbce30af14a/

Notes & Roadmap

Known Issues

My notes above are somwhat incomplete, because they assume some knowledge and also they gloss over one major shortcoming of my deploy scripts: that the Gatsby pathPrefix configuration variable actually needs to be switched out for each deploy destination. This means that technically to do a full deploy currently I have to edit gatsby-config.js before building Gatsby separately before each deploy:

  • For Github Pages deploy, it needs to be the same as the github project name, pathPrefix: '/cyuio'. Then run gatsby build --prefix-paths && gh-pages -d public
  • For DAT, it needs to not be used at all, so gatsby build && dat share public
  • For IPFS, it needs to include your $SITE_HASH referenced above, so something like pathPrefix: '/ipns/QmaLp9R3mX38RpFH2hiud6r3FbTGup5mDfbFuNCahBAXAw'. Then run gatsby build --prefix-paths && ipfs add -r public && ipfs name publish $DIR_HASH

Longer term plans

I have a lot of plans for, but at this point it is primarily a sandbox for trying out new decentralized web projects. Since I'm not running my own webserver at the moment the decentralized versions are likely to be down when you read this. Eventually I'll set up hosting either on my own machine or elsewhere.

Popular Deployment Projects
Popular Authentication Projects
Popular Operations Categories

Get A Weekly Email With Trending Projects For These Categories
No Spam. Unsubscribe easily at any time.