Go to file
Jinho Jang 672c1b928c
Update README.md
2024-09-21 05:27:39 +09:00
.github first commit 2024-09-11 00:58:57 +09:00
.husky first commit 2024-09-11 00:58:57 +09:00
hooks first commit 2024-09-11 00:58:57 +09:00
public feat: show arrow to active nav item 2024-09-13 21:25:17 +09:00
src chore: remove scrollbar 2024-09-13 21:56:44 +09:00
utils first commit 2024-09-11 00:58:57 +09:00
.dockerignore first commit 2024-09-11 00:58:57 +09:00
.env.example first commit 2024-09-11 00:58:57 +09:00
.eslintrc.json first commit 2024-09-11 00:58:57 +09:00
.gitignore first commit 2024-09-11 00:58:57 +09:00
.prettierrc first commit 2024-09-11 00:58:57 +09:00
Dockerfile first commit 2024-09-11 00:58:57 +09:00
Jenkinsfile first commit 2024-09-11 00:58:57 +09:00
README.md Update README.md 2024-09-21 05:27:39 +09:00
mdx-components.tsx first commit 2024-09-11 00:58:57 +09:00
next.config.js first commit 2024-09-11 00:58:57 +09:00
package.json first commit 2024-09-11 00:58:57 +09:00
tsconfig.json first commit 2024-09-11 00:58:57 +09:00
yarn.lock chore: update spacing 2024-09-12 04:02:39 +09:00

README.md

Logos Ordinals

This is currently at the MVP stage of the project.

Staging: https://logos-ordinals-dashboard.vercel.app/

How to Run Locally

  1. Clone this repository
$ git clone https://github.com/acid-info/logos-ordinals-dashboard.git
  1. Install the dependencies:
$ yarn install
  1. Start the development server:
$ yarn dev
  1. Visit http://localhost:3000 in your browser

How to Run a Build (Production Build)

  1. Generate files for production:
$ yarn build

The files will be created in the build directory.

  1. Serve the build:
$ yarn start
  1. Visit http://localhost:3000 in your browser.

Keep in mind this webpage rebuilds itself at runtime.

Change Process

  1. Create a new working branch from develop: git checkout develop; git checkout -b my-changes.

  2. Make your changes, push them to the origin, and open a Pull Request against the develop branch.

  3. After approval, merge the pull request, and verify the changes on the staging server.

  4. When ready to promote changes to the live website, create a pull request against the "master" branch, based on the "develop" branch.