By default these service daemons will be running after vagrant up. You can use pstree to see if they are indeed running in the background.
This is hosted inside ssl.conf. Ready to use for a team as internal source code control. Put more <proj> into ~/Project/shared/<proj>
git -c http.sslVerify=false clone https://192.168.3.100/git/<proj>
git -c http.sslVerify=false clone https://172.30.16.107:8443/git/<proj>
You can use helper scripts under /vagrant/prepvm to add more projects and developers.
This should already be configured and restarted. Add more servers or change existing ones in settings/nginx-config/servers.d.
default bind 0.0.0.0
Use sudo service nginx reload/restart to reload configure/restart web server.
Configure can be located here
/etc/postgresql/9.x/main/postgresql.conf
default listen_addresses = 'localhost' empty list means to allow domain socket only.
Access control can be found here
/etc/postgresql/9.x/main/pg_hba.conf
You might want to change
host all all 127.0.0.1/32 md5
into
host all all 127.0.0.1/32 trust
see more details
Use sudo service postgresql restart to reload the database configure.
Configure can be located here
/etc/mongodb.conf
default bind_ip = 127.0.0.1 see more details
Use sudo service mongodb restart to reload the database configure.
Configure can be located here
/etc/redis/redis.conf
default bind 127.0.0.1 see more details
Use sudo service redis-server restart to reload the data store configure.
Configure should be put here
/etc/rabbitmq/[rabbitmq.config]
/etc/rabbitmq/[rabbitmq-env.conf]
default bind 0.0.0.0 with guest only allowed on 127.0.0.1 see more details
Use sudo service rabbitmq-server reload/restart to reload the configure/restart the message queue.