mirror of
https://github.com/Foundry376/Mailspring.git
synced 2024-09-21 07:46:06 +08:00
b1ba489065
Arc land messed up and landed a not fully merged branch. (Seriously – I had merged a copy of my branch with master to see how easy it would be. Because I didn't want to merge the whole thing, I blindly committed my changes and switched back to my real branch). To my great surprise, arc decided to use the wrong branch when landing it. Original commit message: Summary: Finally, here it is! Send later, with support for open tracking but without support for attachments yet. It took me some time to find the right way to do things. **The send later dilemna** There's two ways we could handle send later: 1. do everything on the client 2. process the message in the cloud 1. is very tempting because it would make the cloud server very simple. Unfortunately, it has some serious limitations, for example, setting the "Date" message header. That's why I chose to go with 2. When a user presses the "Send Later" button, we save the open/link tracking metadata and fills in all the required fields. I added a custom endpoint to the K2 API to do this, `/drafts/build`. After that, we save the JSON contents of the message as metadata. When we process metadata, we simply create a MIME message from the JSON and send it. **Limitations** Right now, send later doesn't support and attachments. There's also some minor code duplication which needs to be refactored away. Test Plan: Tested manually. Checked that regular send still worked, too. Reviewers: mark, spang, halla, juan, evan Reviewed By: evan Differential Revision: https://phab.nylas.com/D4054 |
||
---|---|---|
.ebextensions | ||
arclib | ||
packages | ||
scripts | ||
.arcconfig | ||
.arclint | ||
.babelrc | ||
.dockerignore | ||
.eslintrc | ||
.gitignore | ||
.travis.yml | ||
appveyor.yml | ||
deploy-it | ||
Dockerfile | ||
lerna.json | ||
package.json | ||
README.md |
Nylas Mail
This is a collection of all components required to run Nylas Mail.
- Isomorphic Core: Shared code across local client and cloud servers
- Client App: The main Electron app for Nylas Mail mirrored to open source repo.
- Client Sync: The local mailsync engine integreated in Nylas Mail
- Client Private Plugins: Private Nylas Mail plugins (like SFDC)
- Cloud API: The cloud-based auth and metadata APIs for N1
- Cloud Core: Shared code used in all remote cloud services
- Cloud Workers: Cloud workers for services like send later
See /packages
for the separate pieces. Each folder in /packages
is
designed to be its own stand-alone repository. They are all bundled here
for the ease of source control management.
Initial Setup for All Local & Cloud Services:
New Computer (Mac):
New Computer (Linux - Debian/Ubuntu):
- Install Node 6+ via NodeSource (trusted):
curl -sL https://deb.nodesource.com/setup_6.x | sudo -E bash -
sudo apt-get install -y nodejs
- Install Redis locally
sudo apt-get install -y redis-server redis-tools
benefit of letting us use subdomains.
Running Nylas Mail
npm install
(Only on fresh install and new packages)npm run start-client
: Starts Electron app clientnpm run start-cloud
: Starts cloud API locally