Hi @johan,
I have a few questions regarding setting up a TTN backend network server development environment as follows:
[1]. Instruction for setting up the development environment
There are two source code trees as below:
(1) v1-staging : https://github.com/TheThingsNetwork/ttn/tree/v1-staging
(2) v2-preview : https://github.com/TheThingsNetwork/ttn/tree/v2-preview
I guess v1-staging is what we are currently using and v2-preview is the production version that’s planned to be released in December this year. Am I right?
I guess v2-preview is currently under development and the code will be changing every day, and there is no code change for v1-staging.
Due to this reason, I’d like to set up the development environment and compile v1-staging first before I try to compile v2-preview.
I see there is an instruction for setting up for v2-preview but there is no set up instruction for v1-staging. Does the instruction for v2-preview apply to v1-staging?
[2] Which OS and version?
Which Linux version is preferred for the development environment? Is Ubuntu preferred? If it is, is the latest version of Ubuntu ok?
[3] Go lang and other component versions
I need to download and set up these components - Go, protobuf compiler, Redis, RabbitMQ - according to the instruction. I assume I should download the latest version of these components. Am I right?
[4] To run TTN network server locally
According to the instruction, I am supposed to run ‘forego start’ to start all backend services at the same time.
Can I start each TTN server component separately such as ‘ttn router’, ‘ttn broker’, ‘ttn networkserver’, ‘ttn handler’?
[5] Configuration file for each TTN server component?
If I ran TTN router, broker, handler, and network server separately on different hardware (with different IP addresses), I should configure these components with correct IP addresses so they can talk to right counterparts. Is there a configuration file for each TTN server component?
Thanks.