micro/
The micro development roadmap and contribution guide
USD raised
Recent activities
`micro env create/delete/update/list` for infrastructure
Missing docker release tags
Failed start error visibility
Write a doc for using wrappers
Micro server does not restart services started previously
Router: panic: close of nil channel
Evaluate consolidation of runtime services into one process
micro run with non existent service gives cryptic log error
Check if logs (default `/tmp/micro/logs`), store (default `/tmp/micro/store`) and github checkout locations (default `/tmp/reponame`) are overwritable
Git operations are not thread safe in go-micro
out of memory errors on lower powered machines when compiling
development docs reference section
micro run . - k8s
micro logs -f k8s
micro run <url> - k8s
micro login for new users
micro env m3o
micro namespace crud
Add dependency injection for handlers
Make sure micro --version works
`micro logs` should support reading/streaming logs from multiple services at the same time
Review and fix the help descriptions for micro commands
`micro status` updated time is `unknown` in env `server`
Registry doesn't store endpoints with regex correctly
`micro kill` error message when killing successfully
Migrate from micro/cli to spf13/cobra
Doing a go install on `micro` started taking 10-20 seconds
micro architecture problems
Mistyped commands should not print help
Merge `micro run` and `micro update` commands
Make a video tutorial of micro server running
Move micro.NewService to micro/micro
Auto generate micro web apps
Clearly state and define that the KV store interface returns ordered results
Micro logs -f streaming stops when `micro server` stops
Make micro update detect code file changes and auto deploy
Remove stutter from client access in web services
Reevaluate the "special" nature of server and platform environments
Consider using mux instead of `net/http` for serving web requests to enable path patterns
Godoc (pkg.go.dev) docs should explain web handler path "pattern" usage
Micro new has protos generated under `servicename/proto/servicename`
Idea: regenerate handler/main.go after modifying the proto, in other words generate handler from proto
Check if folder config options to store/logs/config are respected
End to end tutorial for creating a CMS/blog engine
Update for selectors
Tutorial / getting started guide
Local -> Production story
mTLS
Billing dashboard flow
Other dashboard UI tweaks
Notifications Service
Invites flow
Isolation of services/containers
Other multi tenancy clean up
Clean up of m3o vs micro/services
Landing page for m3o on m3o.com
Helm chart for micro server
Auth Improvements
Account Login Redirect
Store s/Expiry/Timestamp
Merge api handler into rpc handler
web.home resolver
Live store hourly backup
Explore Web missing styling
Proxy/Router deadlock or stale cache
Service.{Config, Endpoints, Info}
Service Identity
Check Node.js client (micro/clients) for live only bug that was fixed in ng-client
M3O MVP
Back auth by CF
© 2019 BoostIO, Inc.