feat: [#PET-XXX] platform init

.env.example

@@ -0,0 +1,50 @@
+# Environment variables declared in this file are automatically made available to Prisma.
+# See the documentation for more detail: https://pris.ly/d/prisma-schema#accessing-environment-variables-from-the-schema
+
+# Prisma supports the native connection string format for PostgreSQL, MySQL, SQLite, SQL Server, MongoDB and CockroachDB.
+# See the documentation for all the connection string options: https://pris.ly/d/connection-strings
+
+# app
+APP_ID='388123e7-a3e9-404f-914e-0e571dd104a4'
+NODE_ENV=local
+PORT=4000
+DOMAIN='localhost:3000'
+DEFAULT_PROJECT_ID='3331959d-1666-4f4a-97fc-42363bf5cfbf'
+
+# database
+DATABASE_URL="postgresql://universal-api:universal-api@localhost:6432/universal-api"
+DATABASE_REPLICA_URL_1="postgresql://universal-api:universal-api@localhost:6433/universal-api"
+
+#dictionary
+SPREADSHEET_ID=1OCttWAXiRs40FT5i_T-JsfEi0ewGbVcGtyi2E3dNwJw
+
+# i18n
+I18N_FALLBACK_LANGUAGE=en-US
+
+# cache
+REDIS_DEFAULT_TTL=10000
+REDIS_HOST=localhost
+REDIS_PORT=6379
+REDIS_PASSWORD=eYVX7EwVmmxKPCDmwMtyKVge8oLd2t81
+
+# object-storage
+OBJECT_STORAGE_PROVIDER="minio" # Options: Minio
+OBJECT_STORAGE_DOMAIN=http://127.0.0.1:9000
+MINIO_ENDPOINT=localhost
+MINIO_PORT=9000
+MINIO_ACCESS_KEY=minioadmin
+MINIO_SECRET_KEY=minioadmin
+MINIO_SSL=false
+
+# search
+SEARCH_PROVIDER=meilisearch # Options: Meilisearch
+MEILISEARCH_HOST=http://127.0.0.1:7700
+MEILISEARCH_API_KEY=masterKey
+
+# auth
+AUTH0_ISSUER_URL=https://petsee-local.eu.auth0.com/
+AUTH0_AUDIENCE=https://api.local.petsee.co
+
+
+# monitoring
+SENTRY_DNS=

.eslintrc.js

@@ -0,0 +1,25 @@
+module.exports = {
+  parser: '@typescript-eslint/parser',
+  parserOptions: {
+    project: 'tsconfig.json',
+    tsconfigRootDir: __dirname,
+    sourceType: 'module',
+  },
+  plugins: ['@typescript-eslint/eslint-plugin'],
+  extends: [
+    'plugin:@typescript-eslint/recommended',
+    'plugin:prettier/recommended',
+  ],
+  root: true,
+  env: {
+    node: true,
+    jest: true,
+  },
+  ignorePatterns: ['.eslintrc.js'],
+  rules: {
+    '@typescript-eslint/interface-name-prefix': 'off',
+    '@typescript-eslint/explicit-function-return-type': 'off',
+    '@typescript-eslint/explicit-module-boundary-types': 'off',
+    '@typescript-eslint/no-explicit-any': 'off',
+  },
+};

.gitignore

@@ -0,0 +1,47 @@
+# compiled output
+/dist
+/node_modules
+
+# Logs
+logs
+*.log
+npm-debug.log*
+pnpm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+lerna-debug.log*
+
+# OS
+.DS_Store
+
+# Tests
+/coverage
+/.nyc_output
+junit
+performance-report.*
+
+# IDEs and editors
+/.idea
+.project
+.classpath
+.c9/
+*.launch
+.settings/
+*.sublime-workspace
+
+# IDE - VSCode
+.vscode/*
+!.vscode/settings.json
+!.vscode/tasks.json
+!.vscode/launch.json
+!.vscode/extensions.json
+
+infra/postgresql/*
+!infra/postgresql/.gitkeep
+infra/search/*
+!infra/search/.gitkeep
+!infra/search/meilisearch/.gitkeep
+
+.env*
+!.env.example
+

.prettierrc

@@ -0,0 +1,4 @@
+{
+  "singleQuote": true,
+  "trailingComma": "all"
+}

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting me at pauline@petsee.co. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,71 @@
+# Contribute to Structurify
+
+Structurify is an open-source project administered by [Paelynn](<[pauline@petsee.co](https://github.com/Paelynn)>). I appreciate your interest and efforts to contribute to Petsee. See the [LICENSE](https://github.com/petsee-co/petsee/blob/main/LICENSE) licensing information. All work done is available on GitHub.
+
+I highly appreciate your effort to contribute, but I recommend you talk to me before spending a lot of time making a pull request that may not align with the project roadmap. Whether it is from Structurify or contributors, every pull request goes through the same process.
+
+## Code of Conduct
+
+This project, and everyone participating in it, are governed by the [Petsee Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold it. Make sure to read the [full text](CODE_OF_CONDUCT.md) to understand which type of actions may or may not be tolerated.
+
+## Bugs
+
+Strapi is using [GitHub issues](https://github.com/petsee-co/petsee/issues) to manage bugs. We keep a close eye on them. Before filing a new issue, try to ensure your problem does not already exist.
+
+---
+
+## Before Submitting a Pull Request
+
+The Structurify core team will review your pull request and either merge it, request changes, or close it.
+
+# Contribution Prerequisites
+
+- You have [Node.js](https://nodejs.org/en/) at version >= v20 and [Yarn](https://yarnpkg.com/en/) at v1.2.0+ installed.
+- You are familiar with [Git](https://git-scm.com).
+- You have [Docker](https://www.docker.com/) installed.
+
+**Before submitting your pull request** make sure the following requirements are fulfilled:
+
+- Fork the repository and create your new branch from `main`.
+- Run `yarn install` in the root of the repository.
+- Run `yarn setup` in the root of the repository.
+- If you've fixed a bug or added code that should be tested, please make sure to add tests
+- Ensure the following test suites are passing:
+  - `yarn test`
+  - `yarn test:e2e`
+- Make sure your code lints by running `yarn lint`.
+- If your contribution fixes an existing issue, please make sure to link it in your pull request.
+
+## Development Workflow
+
+### 1. Fork the [repository](https://github.com/petsee-co/petsee)
+
+[Go to the repository](https://github.com/petsee-co/petsee) and fork it using your own GitHub account.
+
+### 2. Clone your repository
+
+```bash
+git clone git@github.com:YOUR_USERNAME/petsee.git
+```
+
+### 3. Install the dependencies
+
+Go to the root of the repository and run the setup:
+
+```bash
+# OSX/Linux
+cd petsee
+yarn install
+yarn docker:dev
+yarn setup
+```
+
+### 4. Start the api
+
+```bash
+yarn start:debug
+```
+
+The Swagger Docs should now be available at http://localhost:4000/docs.
+
+**Awesome! You are now able to contribute to Petsee.**

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 Petsee
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.