Go to file
jinhojang6 166bc9855d feat: add keycard jobs 2024-10-05 00:40:14 +09:00
.github first commit 2023-10-18 00:12:25 +09:00
.husky first commit 2023-10-18 00:12:25 +09:00
hooks feat: add services page 2023-11-10 01:38:54 +09:00
public chore: add matrix delegation 2024-05-31 17:40:44 +02:00
src chore: update copyleft sign 2024-06-13 23:10:08 +09:00
utils feat: add keycard jobs 2024-10-05 00:40:14 +09:00
.dockerignore first commit 2023-10-18 00:12:25 +09:00
.eslintrc.json first commit 2023-10-18 00:12:25 +09:00
.gitignore chore: update profile images 2023-11-15 23:37:51 +09:00
.prettierrc first commit 2023-10-18 00:12:25 +09:00
Dockerfile first commit 2023-10-18 00:12:25 +09:00
Jenkinsfile ci: fix Jenkinsfile, remove unnecessary credentials 2023-12-06 23:59:00 +09:00
README.md readme: add links to CI section 2023-12-06 18:24:56 +01:00
mdx-components.tsx first commit 2023-10-18 00:12:25 +09:00
next.config.js headers to matrix delegation files 2024-06-03 12:03:19 +02:00
package.json fix: upgrade nextjs version to solve memory leaks 2024-03-19 22:02:21 +09:00
tsconfig.json first commit 2023-10-18 00:12:25 +09:00
yarn.lock fix: upgrade nextjs version to solve memory leaks 2024-03-19 22:02:21 +09:00

README.md

IFT

Test pages

  • next-mdx-remote test page: '/'
  • @next/mdx test page: '/test'

How to Run Locally

  1. Clone this repository
$ git clone https://github.com/acid-info/ift.git
  1. Install the dependencies:
$ yarn install
  1. Set .env
NEXT_PUBLIC_SITE_URL=
NEXT_GITHUB_PERSONAL_ACCESS_TOKEN=
  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.

CI/CD

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 (https://dev.logos.co/).

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