Once you are all setup and ready to go you should be able to load SUI at [https://sui.vivumlab.xyz/].
If you want to add an extra layer of authentication to a service, all you have to do is set
vlab service <service> auth -v true. Once this is set, authentication will be handled outside of the service.
This is useful, if the service doesn't provide authentication, eg. SUI. and you would like it to be protected.
Traefik handles authentication, if the
<service>.auth is set to true. More specialised and full featured options are available, check out your options here.
VivumLab sets up
/home/root/vivumlab on your server, which maps to
/home/<ssh_user> by default. All data used to set up your services, can be found here.
If you can't find what you are looking for there; large databases, media collections (audio and video) are typically stored in the "/mnt/nas", which defaults to
/mnt/nas. Using NAS storage? see NAS for more information.
VivumLab will use Traefik's built in LetsEncrypt integration to automatically generate SSL certificates for your various services.
If initially some of the certificates don't appear valid, you have likely run into LetsEncrypt rate limits.
This is LetsEncrypts way of keeping LetsEncrypt usage fair, and as such does not have a fix. Limits will reset in a week. see here
In order for your applications to be able to utilise email (confirmation emails, etc), you need an SMTP server. A nice free one is Mailgun.
Create an account, and follow their steps to register your domain.
Once that is completed, you can plug the settings they provide into your
To do this:
- run the
vlab config decrypt --devcommand
- find and edit the
NOTE: editing this file may require superuser/ root permissions
- Set the following settings to what you have been provided
- Now, edit the
settings/decrypted.ymlfile, and set:
This will allow mailu (and every other VivumLab service) to use the mail gun SMTP server
- Save, and run
vlab deployto finalise any changes.