Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 0.1.1 #49

Merged
merged 12 commits into from
Aug 15, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -4,4 +4,9 @@ dist
dist-ssr
*.local
apps
build
build
theme.json
ExplorerCustom.svg
RegistryCustom.svg
TokenizationCustom.svg
HeaderBrandingCustom.svg
1 change: 1 addition & 0 deletions .nvmrc
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
18.16
11 changes: 11 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,17 @@ The Core Registry UI can be hosted as a web application, either for internal use

To host the UI on the web, use the [web-build.tar.gz file from the releases page](https://github.com/Chia-Network/core-registry-ui/releases). One of the simplest solutions is to uncompress these files into a [public S3 bucket](https://docs.aws.amazon.com/AmazonS3/latest/userguide/WebsiteAccessPermissionsReqd.html). These files could also be served by any webserver, such as Nginx or Apache.

#### Customize Colors and Icons

The Core Registry UI supports color and icon customization by site administrators. To customize the UI colors, copy the `theme.json.example` file to `theme.json` in the web root directory. Edit the new `theme.json` file and replace the default colors with any valid css color definitions.

To customize icons, place SVG files in the web root with the following names:

* RegistryCustom.svg
* TokenizationCustom.svg
* ExplorerCustom.svg
* HeaderBrandingCustom.svg

## Contributing

Upon your first commit, you will automatically be added to the package.json file as a contributor.
Expand Down
6 changes: 3 additions & 3 deletions app-builds.js
Original file line number Diff line number Diff line change
@@ -1,14 +1,14 @@
module.exports = {
cadt: {
tag: "1.3.10",
tag: "1.3.11",
url: "https://github.com/Chia-Network/core-registry-cadt-ui/releases/download/{{tag}}/core-registry-cadt-ui-web-build.tar.gz",
},
climate_explorer: {
tag: "1.1.13",
tag: "1.1.14",
url: "https://github.com/Chia-Network/climate-explorer-ui/releases/download/{{tag}}/climate-explorer-ui-web-build.tar.gz",
},
climate_tokenization_engine: {
tag: "1.1.9",
tag: "1.1.10",
url: "https://github.com/Chia-Network/Climate-Tokenization-Engine-UI/releases/download/{{tag}}/climate-tokenization-engine-ui-web-build.tar.gz",
},
};
4 changes: 2 additions & 2 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions package.json
Original file line number Diff line number Diff line change
@@ -1,14 +1,14 @@
{
"name": "core-registry-ui",
"version": "0.1.0",
"version": "0.1.1",
"scripts": {
"start": "nf start -p 3001",
"electron": "electron .",
"electron-start": "node src/start-react",
"react-start": "vite --port 3000",
"react-start-browser": "vite --port 3001 --open",
"sync-ui-apps": "rm -rf apps && node sync-apps.js",
"build": "rm -rf dist && rm -rf build && npm run sync-ui-apps && vite build && cp -r apps build/apps",
"build": "rm -rf dist && rm -rf build && npm run sync-ui-apps && vite build && cp -r apps build/apps && cp theme.json.example build",
"serve": "vite preview",
"test": "vitest",
"electron:package:mac": "npm run build && electron-builder -m -c.extraMetadata.main=build/electron.js",
Expand Down
Loading
Loading