rgolubtsov/transroutownish-proto-bus-cowboy issues and pull requests

#23 - Fix issues #21 and #22.

Pull Request - State: closed - Opened by rgolubtsov over 1 year ago - 1 comment
Labels: Documentation, Bugfix, Enhancement, Minor enhancement

#22 - Move logging of the server start event into the nearest prev if-block.

Issue - State: closed - Opened by rgolubtsov over 1 year ago - 2 comments
Labels: Enhancement

#21 - Provide description for the state param in EDoc comments in the bus_handler.erl module.

Issue - State: closed - Opened by rgolubtsov over 1 year ago - 2 comments
Labels: Documentation, Minor enhancement

#20 - Containerize the microservice with Docker.

Pull Request - State: closed - Opened by rgolubtsov almost 2 years ago - 1 comment
Labels: Documentation, Enhancement, Configuration management

#19 - Happy New Year!

Pull Request - State: closed - Opened by rgolubtsov almost 2 years ago - 1 comment
Labels: Enhancement, Minor enhancement

#18 - Add the "Logging" subsection.

Pull Request - State: closed - Opened by rgolubtsov almost 2 years ago - 1 comment
Labels: Documentation

#17 - Log messages through the Unix syslog.

Pull Request - State: closed - Opened by rgolubtsov almost 2 years ago - 1 comment
Labels: Enhancement, Configuration management, Continue implementing

#16 - Introduce a function that performs the routes processing to find out the direct route.

Pull Request - State: closed - Opened by rgolubtsov almost 2 years ago - 1 comment
Labels: Documentation, Enhancement, Minor enhancement, Continue implementing

#15 - Reply with the HTTP 400 Bad Request status code and the appropriate response body in case of malformed requests.

Pull Request - State: closed - Opened by rgolubtsov almost 2 years ago - 1 comment
Labels: Enhancement, Continue implementing

#14 - RESTful-related works | Part III.

Pull Request - State: closed - Opened by rgolubtsov almost 2 years ago - 1 comment
Labels: Enhancement, Continue implementing

#13 - RESTful-related works | Part II.

Pull Request - State: closed - Opened by rgolubtsov almost 2 years ago - 1 comment
Labels: Configuration management, Continue implementing

#12 - RESTful-related works | Part I.

Pull Request - State: closed - Opened by rgolubtsov almost 2 years ago - 1 comment
Labels: Enhancement, Continue implementing

#11 - Various enhancements and basic request/response handling.

Pull Request - State: closed - Opened by rgolubtsov almost 2 years ago - 1 comment
Labels: Enhancement, Continue implementing

#10 - Handle errors when trying to open the routes data store.

Pull Request - State: closed - Opened by rgolubtsov almost 2 years ago - 1 comment
Labels: Minor enhancement, Continue implementing

#9 - Make all the preparations to add, track, and start up the Cowboy web server as the main carrier dependency package in the microservice.

Pull Request - State: closed - Opened by rgolubtsov almost 2 years ago - 1 comment
Labels: Documentation, Configuration management, Minor enhancement, Continue implementing

Ecosyste.ms: Issues

GitHub / rgolubtsov/transroutownish-proto-bus-cowboy issues and pull requests

#23 - Fix issues #21 and #22.

#22 - Move logging of the server start event into the nearest prev if-block.

#21 - Provide description for the state param in EDoc comments in the bus_handler.erl module.

#20 - Containerize the microservice with Docker.

#19 - Happy New Year!

#18 - Add the "Logging" subsection.

#17 - Log messages through the Unix syslog.

#16 - Introduce a function that performs the routes processing to find out the direct route.

#15 - Reply with the HTTP 400 Bad Request status code and the appropriate response body in case of malformed requests.

#14 - RESTful-related works | Part III.

#13 - RESTful-related works | Part II.

#12 - RESTful-related works | Part I.

#11 - Various enhancements and basic request/response handling.

#10 - Handle errors when trying to open the routes data store.

#9 - Make all the preparations to add, track, and start up the Cowboy web server as the main carrier dependency package in the microservice.

#8 - Introduce controller module of the application and make various minor enhancements.

#7 - Log events to the console along with the file-based logging.

#6 - Start using the Erlang/OTP standard logging facility.

#5 - Retrieve safely server port number and location of the routes data store.

#4 - Process routes one by one and eliminate a route identifier from each of them.

#3 - Retrieve application settings. Slurp routes from the routes data store.

#2 - Set microservice-specific config params.

#1 - In the beginning: Pay attention to conformance of the application to Erlang/OTP principles, terms, and conditions.