Deployment

Iridium bundles all the required assets directly into your binary, meaning there is no build step required to push your first application to production. Iridium's css & js files are minified and compressed for you already, & it will serve that content for you.

Assets you add in are your responsibility to handle. For example, a favicon.ico, custom theme css file, etc. will require you to write a handler to serve that content. You can do this using the mux you generate in your main.go file for example. This offers you the ability to deceide where these assets are fetched from.

Security warning

It should be apparent, but if you have not secured your application using our auth flows (or one of your own), your app should never be deployed to the public internet. Iridium ships with NO security by default. If you're running this inside your own secure network or locally as a tool, this is probably fine, but never deploy an unsecured application to the internet!

Production deployment checklist

1. Did you enable production mode in Iridium's configuration?
2. Did you set your AppKey and AppEncryptionKey to random 64 and 32 bytes respectively (and have not accidentially commited this to source code)
3. Did you create a build in production mode and spot check all your basic functionality to make sure the stricter policies didn't break anything?

Building a binary

No additional steps are required. Simply build your go binary as you traditonal do and ship. SCP, pipeline, copy & paste - whatever you need.

go build . -o my_app