https://github.com/tdevuit/urbanscale
EGis-Management solutions for urban infrastructure development
https://github.com/tdevuit/urbanscale
Last synced: 8 months ago
JSON representation
EGis-Management solutions for urban infrastructure development
- Host: GitHub
- URL: https://github.com/tdevuit/urbanscale
- Owner: TDevUIT
- Created: 2025-09-16T15:32:45.000Z (9 months ago)
- Default Branch: main
- Last Pushed: 2025-10-06T10:08:29.000Z (8 months ago)
- Last Synced: 2025-10-06T12:13:26.210Z (8 months ago)
- Language: TypeScript
- Homepage:
- Size: 2.29 MB
- Stars: 0
- Watchers: 0
- Forks: 8
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
<<<<<<< HEAD
# IE402 - Microservices Monorepo Skeleton
Repository: https://github.com/TDevUIT/IE402
This repository hosts a monorepo for an urban GIS project of Ho Chi Minh City (HCMC) using a microservices approach:
- GIS_Server: data discovery, curation, and GIS aggregation for districts (e.g., Q1, Binh Thanh, Q10, Thu Duc).
- Data_Processor: transforms unstructured text sources into structured JSON for APIs.
- Web_Server: provides REST APIs for FE by aggregating data from GIS_Server and Data_Processor.
- Web_Client: frontend client app.
Note: The existing Next.js app in `ie402/` is currently used as the Web Client. The FE team can continue development there.
## Team assignments
- GIS_Server: Hương Giang, Quyền, V. Linh — collect and evaluate district data sources (infrastructure, population, traffic, land, environment). Pick top 3 districts with best quality.
- Web_Server: Lâm, Tài, Tân — define and implement APIs, integrate with GIS_Server and Data_Processor.
- Web_Client: Thái, Thắng — implement a simple UI (start from a reference UI on the web), consume APIs from Web_Server.
## Priorities (this week)
1) Study GIS fundamentals, shortlist data sources, mark usable sections.
2) BE team to draft diagrams and API specs.
3) FE to pick a simple UI reference for a quick prototype.
## Structure
- docs/: shared documentation (architecture, guides, tasks, data sources, intros)
- services/
- GIS_Server/: GIS data discovery and aggregation
- Data_Processor/: text -> JSON pipelines
- Web_Server/: REST API surface and aggregation
- clients/
- Web_Client/: Readme and guidance (actual FE lives in `ie402/`)
- diagrams/: placeholders for architecture and data flow
- ie402/: existing Next.js app (FE)
## Getting started
- Read `docs/ARCHITECTURE.md` for the big picture.
- Teams: follow your respective guides in `docs/` and your service directory.
- Editor setup: see `.editorconfig` and `.vscode/` for workspace consistency.
## Repo conventions
- One PR per feature/task, reference TASKS.md item IDs.
- Use conventional commits (feat, fix, docs, chore, refactor, test).
- Keep credentials out of the repo. Use `.env` locally; never commit secrets.
## Guidelines
- API conventions: see `docs/API_CONVENTIONS.md`.
- Pull Request guidelines: see `docs/PR_GUIDE.md`.
- Branching conventions: see `docs/BRANCHING_GUIDE.md`.
## Licensing
TBD.
=======
[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456
[circleci-url]: https://circleci.com/gh/nestjs/nest
A progressive Node.js framework for building efficient and scalable server-side applications.
## Description
[Nest](https://github.com/nestjs/nest) framework TypeScript starter repository.
## Project setup
```bash
$ yarn install
```
## Compile and run the project
```bash
# development
$ yarn run start
# watch mode
$ yarn run start:dev
# production mode
$ yarn run start:prod
```
## Run tests
```bash
# unit tests
$ yarn run test
# e2e tests
$ yarn run test:e2e
# test coverage
$ yarn run test:cov
```
## Deployment
When you're ready to deploy your NestJS application to production, there are some key steps you can take to ensure it runs as efficiently as possible. Check out the [deployment documentation](https://docs.nestjs.com/deployment) for more information.
If you are looking for a cloud-based platform to deploy your NestJS application, check out [Mau](https://mau.nestjs.com), our official platform for deploying NestJS applications on AWS. Mau makes deployment straightforward and fast, requiring just a few simple steps:
```bash
$ yarn install -g @nestjs/mau
$ mau deploy
```
With Mau, you can deploy your application in just a few clicks, allowing you to focus on building features rather than managing infrastructure.
## Resources
Check out a few resources that may come in handy when working with NestJS:
- Visit the [NestJS Documentation](https://docs.nestjs.com) to learn more about the framework.
- For questions and support, please visit our [Discord channel](https://discord.gg/G7Qnnhy).
- To dive deeper and get more hands-on experience, check out our official video [courses](https://courses.nestjs.com/).
- Deploy your application to AWS with the help of [NestJS Mau](https://mau.nestjs.com) in just a few clicks.
- Visualize your application graph and interact with the NestJS application in real-time using [NestJS Devtools](https://devtools.nestjs.com).
- Need help with your project (part-time to full-time)? Check out our official [enterprise support](https://enterprise.nestjs.com).
- To stay in the loop and get updates, follow us on [X](https://x.com/nestframework) and [LinkedIn](https://linkedin.com/company/nestjs).
- Looking for a job, or have a job to offer? Check out our official [Jobs board](https://jobs.nestjs.com).
## Support
Nest is an MIT-licensed open source project. It can grow thanks to the sponsors and support by the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).
## Stay in touch
- Author - [Kamil Myśliwiec](https://twitter.com/kammysliwiec)
- Website - [https://nestjs.com](https://nestjs.com/)
- Twitter - [@nestframework](https://twitter.com/nestframework)
## License
Nest is [MIT licensed](https://github.com/nestjs/nest/blob/master/LICENSE).
>>>>>>> d273b0d (feat: init base api all module)