Skip to content
New issue

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

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

Already on GitHub? # to your account

charites init #41

Open
naogify opened this issue Nov 19, 2021 · 0 comments · Fixed by #82
Open

charites init #41

naogify opened this issue Nov 19, 2021 · 0 comments · Fixed by #82
Labels
Priority: High The issue has high priority
Milestone

Comments

@naogify
Copy link
Contributor

naogify commented Nov 19, 2021

Initializing a project

charites init <project_dir>

First, charites init command will create a charites project named as <project_dir> as follows.

Options

  • --tilejson-urls <tilejson_urls> an URL for TileJSON.
  • --metadatajson-urls <metadatajson_urls> an URL for metadata.json.
  • --composite-layers a single YAML will be generated with multiple layers.
  • --header add http header for the tile authenticated by origin. (ex. --header "Origin: http://localhost:8080")
project-directory/
├── style.yml - root style file
├── config.yml - configuration file to manage all folder paths and necessary settings for producing style.json
├── layers/ - style.yml for layers
├── icons/  - original SVG icons folder for sprite
├── fonts/ - original font files folder for glyphs.
└── public/ - folder for the files that ready to deploy.
    ├── style.json
    ├── icons.json
    ├── icons.png
    ├── icons@2x.json
    ├── icons@2x.png
    └── glyphs files(.pbf?) - sorry I need research what type of file used for glyphs.
version: version of charites used
serve:
  port: 8080
style:
  build:
    yaml-path: ./style.yml
    json-path: ./public/style.json
    compact-output: false
sprite:
  build:
    icons-folder: ./icons
    sprite-folder: ./public/sprite
    name: icons
glyphs:
  build:
    fonts-folder: ./fonts
    glyphs-folder: ./public/glyphs
@naogify naogify added this to the Version 1.0.0 milestone Nov 19, 2021
@naogify naogify added the Priority: High The issue has high priority label Nov 19, 2021
@JinIgarashi JinIgarashi linked a pull request Dec 21, 2021 that will close this issue
9 tasks
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Priority: High The issue has high priority
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant