https://github.com/parameter1/lead-management
Lead Management monorepo
https://github.com/parameter1/lead-management
Last synced: 11 months ago
JSON representation
Lead Management monorepo
- Host: GitHub
- URL: https://github.com/parameter1/lead-management
- Owner: parameter1
- Created: 2021-05-27T19:02:02.000Z (about 5 years ago)
- Default Branch: main
- Last Pushed: 2025-05-12T16:02:51.000Z (about 1 year ago)
- Last Synced: 2025-07-01T03:04:52.026Z (11 months ago)
- Language: HTML
- Homepage:
- Size: 2.03 MB
- Stars: 2
- Watchers: 4
- Forks: 3
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Lead Management Monorepo
## Installation
To set up a local developer environment using this repo, execute the following commands:
```sh
docker compose run --entrypoint /usr/local/bin/yarn manage
docker compose run --entrypoint /usr/local/bin/yarn server
```
Then, the following commands to boot the server and ember applications:
```sh
docker compose up manage
```
The application will now be available on http://localhost:9285 (and the API on http://localhost:9288).
## Releases
This repo contains two projects -- the `manage` ember application, and the `monorepo`. Both of the versions for these projects must remain in sync.
Before releasing the monorepo, check if changes to the ember application should be deployed. If so, increment the ember app's package.json version accordingly before releasing via lerna.
For example, if the `monorepo` is at version `1.2.3`, the ember app is at `1.2.3`, and a new feature was added:
1. Increment and commit the `version` in the `manage` application's `package.json` file manually to match the expected lerna version (`1.3.0`).
2. Release the monorepo: `cd monorepo; lerna version minor`
## Omeda Migration Notes
- [ ] need "click stream" api that can search for all click events during a certain date range
- [ ] need to determine if the deployment name can be included in merge vars
- [x] fix ad creative trackers to use new customer IDs... see `graphql/resolvers/ad-creative-tracker.js`
- [x] fix `allExtractedUrlsForSend` and `searchExtractedUrlsForSend` queries
- [x] fix identity references in `excluded-email-domain` schema
- determine how to handle not-found customers
- [x] need to update `omeda-email-deployment-urls` when urls or hosts change
- [x] fix cache of extracted urls
- legacy excluded/inactive identity data needs to move to the new DB so the old DB can eventually be removed
- [x] use https://www.omeda.com/knowledge-base/customer-change-lookup/ API for customer updates
- [x] drop behaviors - this can be done in onq now
- [x] re-enable `Identity.inactiveCampaigns` and `Identity.inactiveLineItems` resolvers
- [x] review campaign and line item resolvers
- [ ] handle `LineItem.formLineItemLeads` query, and `LineItem.formLineItemChoiceFilters,createFormLineItem` mutations
- [x] restore `EmailCampaign.urls,hasEmailSends,urlCount,urlGroups`
- [x] restore or move `emailReportService.buildEmailMetrics`
- [x] test new ad click/impression trackers
- [x] add meta tags to website for scraping companies/tags
- [x] do not cache indm websites when crawling
## Onboarding
1. Duplicate an existing namespace and reconfigure containers. Use new GAM, Omeda, Brightcove credentials
2. Add tenant to `lead-management.tenants` on Aquaria
3. Add permissions to LM user `db.grantRolesToUser('lead-management', [{ role: 'readWrite', db: 'lead-management-TENANTKEY' }])`
4. Generate DB/Indexes: Set tenant key and boot dev instance to auto-index