WELCOME!

If you are seeing this page, congratulations! Your server is set up correctly.
Please go through Part 1 & 2 to get everything else running smoothly.

Visit S3zipper to get a managed version, or to get more information:

Visit S3zipper for more information.

To check errors and logs:

To see any log errors, check below:

Ubuntu logs

 tail /home/go/logs/log.txt 

Check for docker image updates:

Visit port :3000

Example:

 0.0.0.0:3000 

PART 1 (API SERVER SETUP)

This server is pre-configured to use Caddy Web Server as a reverse proxy.
This means that you can easily get automatic HTTPS by providing a valid domain name.You can also use it as is with a public ip address.
These changes can be achieved through the (Caddyfile & dockerconfig.env) files.
NB: You need to provide a valid PROXY_SERVER_NAME in dockerconfig.env for urls to be generated properly. This value can be your public ip address or a domain name. Restart when done.
All settings for the main internal server can be accessed and edited from one config.toml file. (not recomended.)
More information on forum here

Step 1 (Directory)

Change Directory to home

 cd /home/go 

Internal Server Config path

 /home/go/config.toml 

Caddyfile

 /home/go/Caddyfile 

Environment Variables

 /home/go/dockerconfig.env 

Docker Compose

 /home/go/docker-compose.yml 

Step 2 (Email Notification Setup)

To get email notifications, please provide email configuration settings in config.toml.

NOTE:
*Leave email field empty if you do not need notifications.
*You must provide correct email configurations to be able to use email, or else, an error will be triggered if you provide email with wrong configurations.

PART 2 (API & Usage)

For API documentation and usage:
Visit EC2(AMI) API documentation

Available language examples in postman:
cURL, jQuery, Ruby, Python Requests, Node, PHP, & Go(Golang).