Skip to content
This repository has been archived by the owner on Feb 13, 2022. It is now read-only.

Unsure on config for "sub-slug-URI" #33

Open
ozra opened this issue Sep 9, 2016 · 6 comments
Open

Unsure on config for "sub-slug-URI" #33

ozra opened this issue Sep 9, 2016 · 6 comments

Comments

@ozra
Copy link

ozra commented Sep 9, 2016

I've installed from deb, and I've reverse-proxied from nginx on mysite.tld/mailn - but when visiting the page, it tries to load js from mysite.tld/src/... (apparantly developer-mode?) instead of mysite.tld/mailn/src/....
I didn't figure out where to tell neutronmail that it's on a sub-slug (/mailn/), since it doesn't seem to investigate its path it self.

Also, the packager page (https://packager.io/gh/emersion/neutron) shows all builds as failed since 4 months back, so I don't know if I'm running the latest version (couldn't figure out how to get the neutronmail binary to tell me the version either)

@emersion
Copy link
Owner

emersion commented Sep 9, 2016

I don't think the WebClient (https://github.com/ProtonMail/WebClient) supports being served from a custom path.

Yeah, packager builds fail and I don't know why...

@ozra
Copy link
Author

ozra commented Sep 9, 2016

Ok, I'll just put it on it's own domain.
Would you recommend me to build it from source, or is the package "up to date enough"?

@ozra
Copy link
Author

ozra commented Sep 9, 2016

Hmm, I don't seem to be able to "sign up". I'm using my imap user and passwd. After the captcha, it XHR's and fails: (log output from neutronmail)

[Macaron] 2016-09-09 13:08:20: Started POST /api/users for 127.0.0.1
[Macaron] 2016-09-09 13:08:20: Completed /api/users 500 Internal Server Error in 19.180886ms

Any ideas?

@ozra
Copy link
Author

ozra commented Sep 9, 2016

Wait a minute, sorry: I added conf.json to "/etc/neutronmail", but I removed it again, because neutronmail refused to start because of:

/etc/neutronmail/conf.d/config.json: line 2: Memory:: command not found

That might have a lot to do with it. So what's up with that? (I've only changed the domain etc. and kept the rest of the example config as is)

@emersion
Copy link
Owner

You can specify the config file path with --config=/path/to/config.json.

@ozra
Copy link
Author

ozra commented Sep 19, 2016

There was no problem with the path. There is a problem with the contents:
line 2: Memory:: command not found

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants