Using Actix with Optic

Optic is easy to use with Actix, no special library or large code changes required.

api start Command#

Let's say we have a simple Actix server that we usually develop with on localhost:3005.

Optic needs to know how to start our API#

Our optic.yml file would include our start command (such as cargo run).

name: Actix API
tasks:
command: cargo run
inboundUrl: https://localhost:3005

Optic also needs the ability to control what port our API starts on#

Optic injects a $PORT environment variable for our application to listen on when api start is run. Wherever you start your API server, set the port on which it will bind with this environment variable:

Before#

HttpServer::new(...)
.bind("127.0.0.1:3005")?
.run()
.await

After#

let port = env::var("PORT").unwrap_or_else(|e| {
return "3005".to_string()
});
HttpServer::new(...)
.bind(format!("127.0.0.1:{}" , port))?
.run()
.await

Verifying with api check start#

The setup tool will guide you through running checks to assure Optic is running successfully with your API project. You should see everything pass at this point. If you don't, it's most likely that you're not starting the API on the $PORT Optic provides. The Optic check will also report any other common issues it detects and give you steps and suggestions to resolve them.

Should you need any more help, or want to chat about the process, please reach out to us. You can schedule a quick chat with the maintainers or open an issue on GitHub.

Run your API through Optic#

At this point you should be ready to run api start and document your API with Optic! Optic will observe your API traffic locally, and report on the routes and traffic shape it sees in the Optic dashboard. The next step is to start building your baseline specification

Contributions to this article from: @acunniffe @LouManglass