... | @@ -110,24 +110,6 @@ After that, you can create the folders **contract/** to store the source files f |
... | @@ -110,24 +110,6 @@ After that, you can create the folders **contract/** to store the source files f |
|
For more information or if you are having trouble setting up your Hardhat Environment, visit the
|
|
For more information or if you are having trouble setting up your Hardhat Environment, visit the
|
|
[Hardhat Documentation](https://hardhat.org/docs)
|
|
[Hardhat Documentation](https://hardhat.org/docs)
|
|
|
|
|
|
## Wallet
|
|
|
|
|
|
|
|
To enhance our wallet creation process for this project, we have opted to incorporate [Wagmi](https://wagmi.sh) for seamless Ethereum integration. By integrating our wallet with smart contracts, we can ensure the secure storage of our NFT tickets. Wagmi, a comprehensive collection of React Hooks, provides all the essential tools needed for Ethereum-related development tasks. To streamline the wallet connection experience across multiple chains, we leverage the [web3modals](https://web3modal.com) library, which centralizes the multi-chain wallet connection flows in one convenient location.
|
|
|
|
|
|
|
|
{height="450px"}
|
|
|
|
|
|
|
|
To get started, run the following command:
|
|
|
|
|
|
|
|
```sh
|
|
|
|
npm install @web3modal/ethereum @web3modal/react wagmi
|
|
|
|
```
|
|
|
|
|
|
|
|
This will install web3modals and wagmi:
|
|
|
|
|
|
|
|

|
|
|
|
|
|
|
|
Furthermore, it is essential to create a project on the [WalletConnect](https://cloud.walletconnect.com) website. This will provide our website's wallet function with a unique ID, enabling it to operate seamlessly.
|
|
|
|
|
|
|
|
## Deployment
|
|
## Deployment
|
|
### Database
|
|
### Database
|
|
|
|
|
... | @@ -163,12 +145,6 @@ By including these variables in the .env file, you ensure that Vercel can access |
... | @@ -163,12 +145,6 @@ By including these variables in the .env file, you ensure that Vercel can access |
|
|
|
|
|

|
|

|
|
|
|
|
|
## NextAuth.js
|
|
|
|
To add nextauth to your project, ensure that you´re in the nextjs-blog directory and run the following command:
|
|
|
|
```sh
|
|
|
|
npm install next-auth
|
|
|
|
```
|
|
|
|
|
|
|
|
### Add API route
|
|
### Add API route
|
|
Create a file called [...nextauth].js in pages/api/auth. This contains the dynamic route handler for NextAuth.js which will also contain all of your global NextAuth.js configurations.
|
|
Create a file called [...nextauth].js in pages/api/auth. This contains the dynamic route handler for NextAuth.js which will also contain all of your global NextAuth.js configurations.
|
|
|
|
|
... | @@ -250,3 +226,8 @@ npm run coverage |
... | @@ -250,3 +226,8 @@ npm run coverage |
|
To see the report of the tests open index.html (coverage/lcov-report/pages/index.html)
|
|
To see the report of the tests open index.html (coverage/lcov-report/pages/index.html)
|
|
|
|
|
|

|
|

|
|
|
|
|
|
|
|
# Gitlab CI-Pipeline
|
|
|
|
|
|
|
|
To configure a job, which run the tests after each commit, you have to create a .gitlab-ci.yml file.
|
|
|
|
[.gitlab-ci.yml](https://gitlab.bht-berlin.de/s85885/blockevent/-/blob/develop/.gitlab-ci.yml) |