https://github.com/einstore/einstore
Enterprise/development appstore for easy app deployment, completely open sourced
https://github.com/einstore/einstore
appstore einstore enterprise enterprise-appstore mdm
Last synced: 5 months ago
JSON representation
Enterprise/development appstore for easy app deployment, completely open sourced
- Host: GitHub
- URL: https://github.com/einstore/einstore
- Owner: Einstore
- Created: 2016-11-27T10:31:01.000Z (over 9 years ago)
- Default Branch: main
- Last Pushed: 2026-01-18T18:55:09.000Z (5 months ago)
- Last Synced: 2026-01-19T02:47:56.834Z (5 months ago)
- Topics: appstore, einstore, enterprise, enterprise-appstore, mdm
- Language: TypeScript
- Homepage: https://einstore.pro
- Size: 65.9 MB
- Stars: 134
- Watchers: 17
- Forks: 19
- Open Issues: 42
-
Metadata Files:
- Readme: README.md
- Agents: AGENTS.md
Awesome Lists containing this project
README
# Einstore (Refactor)
Modern private app distribution platform for iOS + Android.
## Structure
- `API/` Node.js + Fastify + Prisma + Postgres
- `Admin/` React + Tailwind (CSR)
- `Web/` React + Tailwind (CSR)
- `frameworks/` Mobile tracking libraries (iOS, Android, Flutter)
- `Libraries/` External submodules (auth only)
- `dev/` Legacy reference (gitignored)
## Notes
- Auth is provided by the external `rafiki270/auth` submodule.
- This is a ground-up refactor; legacy code is reference-only.
## Run (local)
- `make launch` starts the API, Admin, local ingest function, and MinIO (persistent). Use your existing local Caddy (outside this repo) for domain routing.
- Add `/etc/hosts` entries pointing `admin.local.einstore.pro`, `api.local.einstore.pro`, and `local.einstore.pro` to `127.0.0.1`, then proxy those hosts to `localhost:8101` and `localhost:8100` in your own Caddy config.
- For App Platform build/run simulation, see `docs/app-platform-local-sim.md`.
- Default ports now live in the 8100 range: API 8100, Admin 8101, Postgres 8102 (Docker host), and the test runner on 8103.
## Uploading a binary to Einstore
1. Create or copy an API key in Admin (`API Keys`). The API key identifies the team.
2. Request a presigned URL from `/ingest/upload-url` (API key can be passed via `token` query param):
```bash
curl -X POST \
-H "Content-Type: application/json" \
-d '{"filename":"binary.apk","sizeBytes":12345678}' \
"https://api.local.einstore.pro/ingest/upload-url?token=YOUR_API_KEY_TOKEN"
```
3. Upload the binary directly to storage using the returned `uploadUrl`, honoring the `headers` payload if provided.
4. Finalize the upload with `/ingest/complete-upload` (send `key` from step 2).
5. Teams have a storage quota (default 1 GB). If an upload would exceed the quota, the API purges the oldest builds first (never deletes the last build of an app). If no space can be freed, the upload is rejected with a clear error.
## Storage CORS (self-hosting)
When self-hosting, browser uploads PUT directly to your S3-compatible bucket using presigned URLs. Browsers send a CORS preflight request; if your bucket does not allow the Admin origin, the PUT fails with a network/CORS error before the file ever reaches storage. You must configure bucket CORS for Admin (and any other upload origins).
Example CORS (S3/Spaces/MinIO):
```json
{
"CORSRules": [
{
"AllowedOrigins": [
"https://admin.your-domain.com",
"https://api.your-domain.com",
"http://localhost:8101"
],
"AllowedMethods": ["GET", "PUT", "POST", "HEAD", "DELETE"],
"AllowedHeaders": ["*"],
"ExposeHeaders": ["ETag", "x-amz-request-id", "x-amz-id-2", "x-amz-version-id"],
"MaxAgeSeconds": 3000
}
]
}
```
DigitalOcean Spaces (CLI example):
```bash
aws --endpoint-url https://lon1.digitaloceanspaces.com s3api put-bucket-cors \
--bucket your-bucket \
--cors-configuration file://cors.json
```
Notes:
- The presigned URL is generated with `SignedHeaders=host` only. Do not add custom headers (including `Content-Type`) unless the API explicitly returns them, or the signature will be invalid.
- If you change the Admin or API domain, update your bucket CORS to match the new origins.
## Integration tests (Newman)
- Requirements: API running locally, valid `accessToken`, `teamId`, `apiKeyToken`, and sample APK/IPA paths.
- Update `tests/newman/local.postman_environment.json` with your tokens and file paths.
- Run: `cd API && npm run test:integration`
- The command executes the Postman collection folders: `Ingest Upload (APK)` and `Ingest Upload (IPA)` against `postman_collection.json`.