android | ||
build | ||
config | ||
cpp | ||
deploy | ||
ext | ||
gwt | ||
install | ||
james | ||
java | ||
keys | ||
passwords | ||
web | ||
.gitignore | ||
DEV_BRAIN_DUMP.txt | ||
HOW_TO_INSTALL.txt | ||
License.txt | ||
make | ||
README.md | ||
setup-1-dependencies | ||
setup-2-install | ||
setup-3-compile | ||
setup-4-deploy |
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:
-
Have ssh keys: ssh-keygen -t rsa -b 4096
-
Have git installed: sudo apt-get install git --yes
-
Have unzip installed: sudo apt-get install unzip --yes
-
Clone the mailiverse: git clone https://github.com/timprepscius/mailiverse.git
-
Have oracle java installed: cd mailiverse/install && sudo ./setup-java.remote
-
Have ant installed: sudo apt-get install ant --yes
-
Add lines to the hosts file for the target machine: sudo nano /etc/hosts add the lines: SOME-IP-ADDRESS mail.whateverthenameofyourdomainis SOME-IP-ADDRESS whateverthenameofyourdomainis
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 -------------
- ./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.
- ./setup-2-install
This will install the mailiverse system onto the target. This means it will create user directories, install software, etc.
- ./setup-3-compile
This will compile all the sources, jar them up, war them up, etc.
- ./setup-4-deploy
This will deploy mailiverse onto the target machine.
Congratulations, if you have finished these, you should be able to put:
And it should work.