从国内访问 Atom 的源很慢，求解决方案

archermind · 2015 年6 月 23 日 08:57

初学Atom，从Github上发现 Atom 的 deb包是放在 amazon云上的，不翻墙很难访问到不是吗？

另外，google了一圈好不容易在贵站找到了一个放在 baidu 云的deb包，成功安装。但是新问题出现了，我使用 apm 来安装插件的话，依旧很难逾越那道墙。

请问，大家都是怎么解决问题的？翻墙我会，可是我在共用电脑上，翻不动啊~~

UPDATE:

alan@apt$apm -v
apm  0.171.0
npm  2.5.1
node 0.10.35
python 2.7.6
git 1.9.1
alan@apt$apm install asciidoc-preview
Installing asciidoc-preview to /home/alan/.atom/packages

archermind · 2015 年6 月 23 日 09:28

找到一个Workaround：

1- Go into your ~/.atom/packages folder
2- run git clone https://github.com/asciidoctor/atom-asciidoc-preview.git asciidoc-preview
3- cd asciidoc-preview
4- git checkout
5- run npm install

jysperm · 2015 年6 月 23 日 15:21

apm 的首页上有提到如何为 apm 设置 HTTP/HTTPS 代理：

更多方案见 Atom 安装插件时因网络原因失败怎么办？

hyanwang · 2015 年6 月 27 日 12:19

设置代理有什么用？没有翻墙的代理不是白搭

jysperm · 2015 年6 月 27 日 12:53

是的，需要你有个代理。

hyanwang · 2015 年6 月 28 日 01:10

github.com/atom/apm

How to use apm under the WALL

已打开 05:05PM - 16 Aug 14 UTC

lijunle

# The story As you may know, there is a [WALL](http://en.wikipedia.org/wiki/Gre…at_Firewall_of_China) in China. Many websites are affected by this great wall, including `npm`, Amazon S3. As a result, there is something like _[Taobao NPM mirror](http://npm.taobao.org/)_ to resolve problems. While using `apm`, I feel sad. The tool only output one line when installing a package. Under the wall, it always says, _installing..._ and hangs. Half or one hour passed, failed. :( The tool even has no options to out more log to debug what's going wrong! That is why I want to draft a document to help the user to across the wall to install a package. _Note_: I just modify the generated `.js` file in the Atom installed directory. Maybe you need a backup before start. This tool also cover Windows users. # Debug First of all, we need to output more things to be aware what is happening under one line. Open `Atom/resources/app/apm/node_modules/atom-package-manager/lib/install.js` 1. Add `process.env.NODE_DEBUG = 'request';` after the `require` statements. ([Reference](https://github.com/mikeal/request/issues/768)) 2. Inside `Install.prototype.installNode` function, pass `{ streaming: true }` in `_this.fork` function. Like this: ``` // around line 68 return _this.fork(_this.atomNodeGypPath, installNodeArgs, { env: env, streaming: true, // <--- add this line cwd: _this.atomDirectory }, function(code, stderr, stdout) { ... } ``` 3. Do the same thing in the `fork` invoke in `Install.prototype.installModule` function. ``` // around line 140 installOptions = { env: env, streaming: true <--- add this line }; ... return this.fork(this.atomNpmPath, installArgs, installOptions, (function(_this) { ... } ``` Add `streaming: true` parameter will let the sub-process log output to console directly. ([Reference](https://github.com/atom/apm/blob/master/src/command.coffee#L22)) OK, done. Now, run `apm install <package>` in your console, you get more logs than before. When the output hangs, investigate which URL is requesting. # URLs There are mainly three sources will be requested when install a package. 1. [Atom API](https://atom.io/api/packages). The request to this API happens at the beginning, to get package metadata. 2. [Amazon S3](http://aws.amazon.com/s3/). **This URL is affected by the wall strongly.** All atom packages are stored in Amazon S3. After the metadata is returned, `apm` starts to download the package from S3. 3. [NPM](http://registry.npmjs.org/). When there are lots of request, this API will be blocked. After the Atom package is downloaded, `apm` will request its dependencies from NPM store. # Configurations _Note_: once you modify the configuration, run `apm install <package>` and check its log. The configuration may _not_ work. (You know, the wall is _great_.) Then, continue modify your configuration and re-check. There are two ways to configure `apm`. 1. `.apmrc` file. The global `.apmrc` file exists in `Atom/resources/app/apm/node_modules/atom-package-manager/`, and the user specified is in `$HOME`. 2. Environment variable. Some configurations are only exposed to environment. Check `process.env` in [`config.js`](https://github.com/atom/apm/blob/master/src/config.coffee). Basically, add the following two lines in `.apmrc` file will set proxy. ([Reference](https://github.com/atom/apm/blob/master/src/request.coffee#L14)). But due to [some issues](https://github.com/atom/atom/issues/1807), such proxy does not work. ``` proxy = http://HOST:PORT strict-ssl = false ``` As a solution, run the `apm` command, then check which is the cause of the failure. Then add workaround. 1. Atom API. When blocked when request Atom API. Add a environment variable `ATOM_API_URL` to point to your reverse proxy. ([Reference](https://github.com/atom/apm/blob/master/src/config.coffee#L45)) (About reverse proxy, read it below.) 2. Amazon S3. Environment variable `ATOM_NODE_URL` points to your reverse proxy. ([Reference](https://github.com/atom/apm/blob/master/src/config.coffee#L39)) 3. NPM. Thanks to the cool Taobao NPM. They proxy the NPM packages for us. add the following to `.apmrc` file: ``` registry = https://registry.npm.taobao.org ``` # Reverse Proxy If you do not have a proxy, you can use mine: ``` ATOM_API_URL = http://atom.lijunle.tk/api ATOM_NODE_URL = http://atom.lijunle.tk/dist ``` It is recommended to use nginx to set up your own reverse proxy. Sample configuration: ``` server { listen 80; server_name atom.lijunle.tk; location /dist/ { proxy_pass https://gh-contractor-zcbenz.s3.amazonaws.com/atom-shell/dist/; } location /api/ { proxy_pass https://atom.io/api/; } } ```

archermind · 2015 年6 月 28 日 07:40

我没有仔细看，估计老外会说

this is your problem

qianghaohao · 2016 年8 月 26 日 14:31

http://blog.csdn.net/qianghaohao/article/details/52331432
切换成国内的源就没问题了，不需要设置代理。

Gaohaoyang · 2017 年3 月 23 日 03:25

除了设置代理，也可以手动 clone 插件项目进行安装。

先进入插件安装的目录

cd /Users/YOURNAME/.atom/packages

可以看到这个目录下，全部是安装过的插件。

例如我们现在要安装 atom-beautify，找到其 git 地址 Glavin001/atom-beautify

将仓库 clone 下来，在 npm install 就好了

git clone [email protected]:Glavin001/atom-beautify.git
cd atom-beautify
npm install

最后再重启一下 atom 就可以看到插件已经安装成功了。

该死的 gfw

https://www.zhihu.com/question/50859713/answer/153110096

weifengHuang · 2017 年7 月 23 日 14:04

非常感谢！完美的解决了问题