mirror of
https://github.com/Foundry376/Mailspring.git
synced 2025-01-11 10:38:11 +08:00
c2a0df174f
Summary: By default, the 'local'/'development' environment assumes that all services are running locally. This makes sense. However, if you're not making changes to auxiliary services such as billing.nylas.com and hence do not have them running locally, firing up Nylas Mail with the 'local' env will not work. It's a bit of a pain to get a local billing service running locally, especially if you're not making any changes to that service. To ease development, change the default billing URL during development to staging, and allow manually overriding the billing server URL to point to localhost in the case that you're making changes to the billing service also. To override the billing URL for local development, run like this: npm run cloud -- --env billing_local BILLING_URL=http://billing.lvh.me:5555 npm start This is both a problem that I've run into during development as well as (my hunch) why Karim accidentally landed a global override of the billing server URL. Test Plan: manual Reviewers: evan, khamidou, halla, juan Reviewed By: juan Differential Revision: https://phab.nylas.com/D4202 |
||
---|---|---|
.. | ||
client-app | ||
client-sync | ||
isomorphic-core | ||
README.md |
Monorepo Packages
Each folder here is designed to act as its own repository. For development convenience, they are all included here in one monorepo. This allows us to grep across multiple codebases, not use submodules, and keep a unified commit history.
We use Lerna to manage the monorepo and tie
them all together with the main nylas-mail-all/scripts/postinstall.es6
script,
which in turn, calls lerna bootstrap