Piotr Czajkowski
1faef23f28
getTMs doesn't need to be exported
|
3 年 前 | |
|---|---|---|
| .github | 4 年 前 | |
| html | 4 年 前 | |
| log | 8 年 前 | |
| static | 3 年 前 | |
| testFiles | 8 年 前 | |
| .deepsource.toml | 3 年 前 | |
| LICENSE.md | 6 年 前 | |
| README.md | 3 年 前 | |
| app.go | 3 年 前 | |
| app_test.go | 3 年 前 | |
| go.mod | 3 年 前 | |
| http.go | 3 年 前 | |
| logger.go | 3 年 前 | |
| search.go | 3 年 前 | |
| searchInfo.go | 6 年 前 | |
| search_test.go | 3 年 前 | |
| secrets.json | 8 年 前 | |
| server.go | 3 年 前 | |
| tm.go | 3 年 前 | |
| tm_test.go | 3 年 前 |
README.md
TM Search for memoQ Server
This is a proof-of-concept tool (hobby project) which utilizes memoQ server Resources API.
It provides simple HTML interface which of course can be improved. There's also logging mechanism which collects requestor's IP, phrase he was searching for, target language and number of served results. Logs are saved in log subfolder in separate .log files (one per day) in CSV format.
You just need to build it and make sure that subfolders html and log are present in the same location as your binary. You'll also need secrets.json, just make sure you fill it with proper credentials. Account used needs to be able to list TMs on your server and read their content, of course. It's using only standard GO packages, so there are no external dependencies.
Usage is simple. To get started just launch compiled binary with -b switch followed by the URL of your Resources API. Now just navigate to localhost/ in your browser and start searching your TMs. You may also want to adjust html/languages.json to be more relevant to your environment.
Optional parameters are as follows:
- h - if you want to serve it under hostname different than localhost
- p - if you want to serve it on port different than 80
You can also navigate to localhost/tms to list all your TMs or to localhost/tms?lang=fre-FR to list TMs for given language.
This app was designed to be used on local network or via VPN, so it lacks any security which would be necessary when exposed to Internet. It was also never tested under heavy load. You're free to use it however you wish, but I take no responsibility for any possible damage caused by it.