| language: haskell | |
| dist: trusty | |
| cache: | |
| directories: | |
| - $HOME/.cabal/packages | |
| - $HOME/.cabal/store | |
| - $HOME/.stack | |
| - $TRAVIS_BUILD_DIR/.stack-work |
#protonmail #centos #fedora #linux
Currently protonmail bridge for linux is distributed as part of an open beta program, but soon it will be made public (https://protonmail.com/bridge/install).
Consider that the bridge linux client requires a paid protonmail account to work.
| # Instruction + template repo: https://github.com/FedericoPonzi/rust-ci | |
| # Search and replace <YOUR_BINARY_NAME> with your binary name. | |
| name: CI | |
| on: | |
| pull_request: | |
| push: | |
| branches: | |
| - master | |
| tags: |
Made this example to show how to use Next.js router for a 100% SPA (no JS server) app.
You use Next.js router like normally, but don't define getStaticProps and such. Instead you do client-only fetching with swr, react-query, or similar methods.
You can generate HTML fallback for the page if there's something meaningful to show before you "know" the params. (Remember, HTML is static, so it can't respond to dynamic query. But it can be different per route.)
Don't like Next? Here's how to do the same in Gatsby.
