Project: Meshery (Provisioning / Automation & Configuration)
File: meshery-server.md

layout: page title: Contributing to Meshery Server permalink: project/contributing/contributing-server redirect_from: project/contributing/contributing-server/ abstract: How to contribute to Meshery Server language: en type: project category: contributing list: include As a new contributor, youre going to want to familiarize with the project in order to resolve the issues in the best way. Installing and playing around with Meshery will give you context for any issues that you might work on. Once an issue has been addressed, youll need to test it as well. Ideally, these tests are run from the users perspective (someone running Meshery in a container), not from a contributors perspective (someone running Meshery as a locally-compiled service). To build and run Meshery server from source: Build the static assets for the UI by running {% capture code_content %}make ui-setup make ui-build{% endcapture %} {% include code.html code=code_content %} Build & run the server code by running {% capture code_content %}make server{% endcapture %} {% include code.html code=code_content %} Any time changes are made to the Go code, you will have to stop the server and run the above command again. Once the Meshery server is up and running, you should be able to access Meshery on your `localhost` on port `9081` at `http://localhost:9081`. One thing to note, you might NOT see the until the UI code is built as well. After running Meshery server, you will need to select your Cloud Provider by navigating to `localhost:9081`. Only then you will be able to use the Meshery UI on port `3000`. Please note: If you get error while starting the server as "Meshery Development Incompatible" then follow the below guideline <a href="{{ site.baseurl }}/assets/img/meshery-development-incompatible-error.png"> <img style= "max-width: 450px;" src="{{ site.baseurl }}/assets/img/meshery-development-incompatible-error.png" /> </a> Potential Solution: Go to your meshery folder in your local-system where youve cloned it. Execute: `git remote add upstream

`git fetch upstream` Restart the meshery server Additionally, before restarting the server, if you like to pull the latest changes, you can do: `git pull upstream master` To build a Docker image of Meshery, please ensure you have `Docker` installed to be able to build the image. Now, run the following command to build the Docker image: {% capture code_content %}make docker{% endcapture %} {% include code.html code=code_content %} Every Golang-based component within the Meshery ecosystem incorporates a utility to define and manage error messages for every error instance. This is internally done with several make commands, but one can explicitly validate with the help of the following make command. This checks and validates the errors that are present in the particular project. {% capture code_content %}make error{% endcapture %} {% include code.html code=code_content %} For more details, <a href="{{ site.baseurl }}/project/contributing/contributing-error">Error Utility</a> The server log levels can be configured at runtime by changing the env variable `LOGLEVEL` defined in file . The configuration library (`viper`) watches for the env file, any change in the file content results in the `filesystem` event to be emitted and the log level is updated accordingly. _Should there be any alterations to the location or name of the environment file, it will result in the inability to configure log levels during runtime. In the event of such modifications, it is essential to update the server to preserve proper functionality._ ```Available Meshery Server log levels are: Panic - 0 Fatal - 1 Error - 2 Warn - 3 Info - 4 Debug - 5 Trace level - 6 ``` The default setting for the `LOGLEVEL` is `4` (Info). However, if the `DEBUG` environmental variable is configured as `TRUE`, it supersedes the value set in the `LOGLEVEL` environmental variable, and the logging level is then adjusted to `5`(Debug).