---
# System prepended metadata

title: IPFS Deployment - daohaus-app
tags: [Product]

---

---
tags: Product
---

# IPFS Deployment - daohaus-app

## Goals
- Move deployment from netlify servers to IPFS
- Support custom domain
- Replicate continuous deployment flow with Fleek
- Limit end user disruption/url changes due to need for hash router w/ create react app

## Option 1 - Flip the switch
- Replace BrowserRouter with HashRouter in app
- Move deployment to Fleek/ipfs
- Keep app.daohaus.club domain
- Communicate url change to users
    - could we make this a positive thing - announce further decentralization?

#### pros
- quick and easy

#### cons
- urls out in the world will break (bookmarks, hyperlinks, ect...)



## Option 2 - New subdomain + redirect app
- Replace BrowserRouter with HashRouter in app
- Move deployment to Fleek/ipfs
- new domain is dapp.daohaus.club
- Create a tiny app deployed at app.daohaus.club that can catch all urls and redirect to dapp.daohaus.club

#### pros
- less end user disruption

#### cons
- creating a redirect app
- double subdomain is confusing and we loose the most desirable `app` subdomain

### Option 3 - Next.js
- Redevelop the app on next.js to support ssr/html pages per route
- Move deployment to Fleek/ipfs
- Keep app.daohaus.club domain


**NEED MORE EXPLORATION TO ENSURE DEEP-LINKING ON IPFS WORKS WITH ALL DAOHAUS ROUTES**

#### pros
- no end user disruption
- `app` subdomain
- next.js might give us better metadata/unfurl options

#### cons
- unsure on next.js conversion effort, but it isn't trivial


## Next Steps
- More next.js exploration


## Resources

https://dapp.daohaus.club/#/

this branch for deploys:
https://github.com/HausDAO/daohaus-app/tree/feature/fleek


If we end up going with this we'd probably get a team plan for multiple users ($40/mo)
https://fleek.co/pricing/