RevDeBug on production
How to configure the RevDeBug recording server and deploy your applications to the production environment.
Estimated reading time: 10 minutes
In this chapter you will learn how to:
Get access to the RevDeBug Server
You can get the server access key via the RevDeBug Organization (you’ve probably already created it after registration. If not, visit our portal page.
Configure the RevDeBug Server
The fun begins here :)
Recommended specification of the server:
System: Linux, any distribution that supports Docker
HD (free space): 10GB+ (SSD highly recommended)
CPU: 4 vCore(s) 2.4 GHz
The specification can be tweaked and even lowered. Such hardware is the most optimal.
Also, by default you need two ports open for your Recording Server 42733 and 42734 unless you would like to use different ports.
Then, prepare the docker environment and when your docker container is ready for the RevDeBug Server all you need to do is paste in those 2 commands into your servers command prompt:
sudo docker pull docker.revdebug.com/server
sudo docker run -d --name rdb_server_node -p 42733-42734:42733-42734 -v /var/revdebug/server/repo:/app/RevDeBug:rw -e REVDEBUG_AUTH='[RevDeBug ID Access Hash]' -e RECORDING_MODE='3' docker.revdebug.com/server
“RevDeBug ID Access Hash” - equals the organization code you can find in our portal.
Here's how to get the organization access hash:
And that's it. Your server is up and running!
Other useful docker commands that you might need:
Sudo docker ps -a <---Displays your docker containers
Sudo docker restart rdb_server_node <---restarts the RevDeBug server node
Ifconfig <---displays your servers IP address
Sudo docker logs -f rdb_server_node <---shows the logs of your RevDeBug server
Connect the VS extension to the RevDeBug Server
In the RevDeBug window inside your IDE click on the Settings Tab, fill in your server connection IP address. If you don’t remember your address use the ifconfig command in your docker server.
Then simply click the "Test connection" button and you should see a green success message "Connected to server" right next to it. Make sure to press the save button afterwards.
Choose your recording mode
You can also change the recording mode to Monitoring, Live Recorder or Crash Recorder. In order to do so, go to Settings > General > Recording Mode >
- Monitoring records only exceptions and performance data
- Crash Recorder records only a set amount of steps back (1.000 be default) and the bug itself. This mode is very light and fits well for production use.
- Live recorder records everything that has occurred in the application incliding every line of code executed, every variable value, every exception and the performance data. This mode is suggested to be used only locally/ in the testing environment.
Deploy your application with RevDeBug
You can release your application with RevDeBug manually (via Visual Studio) or using the Continuous Integration servers like Jenkins, TeamCity, Microsoft TFS, etc.
If you're interested in doing it via CI, we've described this simple process in the chapter called RevDeBug in the Continuous Integration Pipeline