Xymorot 420cd4756d | ||
---|---|---|
resources | ||
src | ||
.editorconfig | ||
.eslintignore | ||
.eslintrc.json | ||
.gitignore | ||
.prettierrc.yml | ||
README.md | ||
forge.config.js | ||
gulpfile.js | ||
index.html | ||
ormconfig.yml | ||
package-lock.json | ||
package.json | ||
tsconfig.json | ||
tslint.json | ||
webpack.config.js |
README.md
レンアイ - Hentai Library Thingy
Development
Quickstart
npm install
, the postinstall runsnpm run rebuild
- might need to install some build tools depending on your platform
npm run typeorm:migrate
for installing the database
npm run tsc
for backendnpm run webpack
for frontendnpm run dev
Git Commits
This project uses Conventional Commits with the following types:
feat
: features, if any part of your commit implements a new functionality or changes an existing one, use thisremove
: removal of existing code/functionalityfix
: bugfixesrefactor
: code refactoringupdate
: updating dependencies and associated code changesconfig
: changing configuration (linters, build process)doc
: documentationreformat
: fixing code formatting
Always try to split up your changes into coherent commits, a single commit should do a single thing. If your commit needs to do more than one thing it should be labeled with the type coming first in this list.
Database Migrations
Migrations are stored in src/main/migrations and handled by typeorm.
To auto-generate a migration:
node_modules/.bin/typeorm migration:generate -n <migration name> -c <connection name>
To create an empty creation which can be filled with custom migration code:
node_modules/.bin/typeorm migration:create -n <migration name> -c <connection name>
To run migrations:
node_modules/.bin/typeorm migration:run -c <connection name>
This is also pre-defined in the npm script typeorm:migrate
.