moparisthebest/mailiverse
1
0
Fork 0
mirror of https://github.com/moparisthebest/mailiverse synced 2024-12-21 21:08:48 -05:00
Code Issues Releases Wiki Activity
96 Commits 1 Branch 0 Tags 172 MiB
C++ 35.5%
JavaScript 27.2%
Java 17.8%
HTML 6.6%
C 6.6%
Other 6.1%
819882d9b0
Go to file
Timothy Prepscius 819882d9b0 pgp uses rng from tomwu, mDispatch does pgp sync, somehow failing async
2013-10-05 12:37:02 -04:00
android adds the android 2013-08-09 16:48:44 -04:00
build changes for case sensitive file system 2013-10-04 23:04:41 -04:00
config moves the config to lower directory, makes the keys generate automatically 2013-09-05 15:36:14 -04:00
cpp adds the cpp files 2013-07-25 22:51:23 -04:00
deploy adds an 80 server 2013-09-29 20:27:44 -04:00
ext more setup 2013-09-29 11:43:45 -04:00
gwt makes gwt build log level not all 2013-09-29 12:40:31 -04:00
install more changes for installation 2013-10-04 22:58:21 -04:00
james makes the files closer to the svn original so easier to track changes 2013-09-01 23:45:17 -04:00
java wrong Base64 in Stripe 2013-10-04 21:48:14 -04:00
keys adds dummy ios-push so rsync executes correctly 2013-09-29 18:37:20 -04:00
passwords makes the captcha keys optional 2013-09-29 15:12:15 -04:00
web pgp uses rng from tomwu, mDispatch does pgp sync, somehow failing async 2013-10-05 12:37:02 -04:00
.gitignore adds the build scripts, removes some remaining unremoved files which I thought I removed last time 2013-08-09 16:31:05 -04:00
DEV_BRAIN_DUMP.txt adds another cut of the pgp key ring, adds first cut of internal store so test-setups don't need to use S3 2013-09-23 16:10:07 -04:00
HOW_TO_INSTALL.txt getting very close to automatic deploy 2013-09-01 18:17:08 -04:00
License.txt adds a set of files 2013-07-14 12:38:31 -04:00
make adds the base make script 2013-08-09 16:50:30 -04:00
README.md pgp uses rng from tomwu, mDispatch does pgp sync, somehow failing async 2013-10-05 12:37:02 -04:00
setup-1-dependencies more setup 2013-09-28 19:36:45 -04:00
setup-2-install more little changes 2013-10-04 22:37:51 -04:00
setup-3-compile more setup 2013-09-28 19:15:17 -04:00
setup-4-deploy more setup 2013-09-29 11:43:45 -04:00

README.md

mailiverse

This documents talks about installing mailiverse from an origin to a target.

------- Requirements on the origin build machine ---------

To install from and build mailiverse from the origin, the origin must:

  1. Have ssh keys: ssh-keygen -t rsa -b 4096

  2. Have git installed: sudo apt-get install git --yes

  3. Have unzip installed: sudo apt-get install unzip --yes

  4. Clone the mailiverse: git clone https://github.com/timprepscius/mailiverse.git

  5. Have oracle java installed: cd mailiverse/install && sudo ./setup-java.remote

  6. Have ant installed: sudo apt-get install ant --yes

  7. Add the line to the hosts file for the target machine:

So let's say your target machine was named: joesmail.com And it's IP was: 192.168.1.243

sudo nano /etc/hosts add the lines: 192.168.1.243 mail.joesmail.com

This could also be done on a DNS server, if you control one..

After these steps have been taken you are ready to set up.

--------- Setting up -------------

  1. ./setup-1-dependencies

This will build enough stuff to generate keys for things. It will will generate default keys, default passwords, etc. You will at some point need to type in "password" a bunch of times, to export a particular key so it can be used with nginx.

  1. ./setup-2-install

This will install the mailiverse system onto the target. This means it will create user directories, install software, etc.

  1. ./setup-3-compile

This will compile all the sources, jar them up, war them up, etc.

  1. ./setup-4-deploy

This will deploy mailiverse onto the target machine.

Congratulations, if you have finished these, you should be able to put:

https://mail.targetmachine/

And it should work.