martin/.gitignore

#### This must match .dockerignore ####
.DS_Store
target/
**/*.rs.bk
.idea/
.vscode/
test_log*
*.profraw

pg_data/
config.yml
tests/output/
tmp/
.aws-sam/
Fix non-deterministic CI tests (#724) * a race condition due to duplicated webp.mbtiles and webp.pmtiles * minor cleanup of CI/dockerignore * dependency bump 2023-06-23 06:01:57 +03:00			`#### This must match .dockerignore ####`
chore: v0.2.0 release 2018-11-02 16:38:00 +03:00			`.DS_Store`
Refactorings, content-type/enc, cli parsing, tests, minor fixes (#548) * introduce a new Connections object to track all positional strings passed as the CLI arguments * each tile provider can now indicate if it can take a positional CLI arg, and if the value can be shared between multiple providers, i.e. if its a directory that could contain files for multiple providers * make xyz use better types - u8 for zoom, u32 for x&y. Postgres casts those to INT2 and INT8 * minor bug in pre-push git hook to abort in case of a testingerror * added GIF detection/type * combine MVT and compression concepts into one enum more explicitly. It is not ideal (technically they are separate concerns), but it keeps it a bit simpler for now for multiple providers. * set content encoding and content type on HTTP responses if known, and also include them in the `/catalog` response (json) * raise an error if the user attempts to merge non-concatenatable tiles from multiple sources. We may want to implement it in the future, e.g. combine multiple semi-transparent PNGs. Or even combine GIF & PNG & JPEG * do not set content-type on empty responses (http 204) * add tilejson outputs to testing 2023-01-08 17:31:58 +03:00			`target/`
initial commit 2017-09-30 13:55:44 +03:00			`*/.rs.bk`
chore: migrate to TileJSON v0.3 (#330) (h/t @nyurik) * use `tilejson!` to generate json object * use `Bounds` everywhere when appropriate 2022-05-27 14:04:27 +03:00			`.idea/`
add .vscode to gitignroe (#791) 2023-08-02 15:10:01 +03:00			`.vscode/`
Catch errors in tests, minor fixes (#514) This extracts some of the code from #511 but without breaking changes * Use `PathBuf` instead of `String` where dealing with files * Parse keep_alive as u64 * More config tests to crash if martin output contains warnings or errors 2022-12-12 17:11:10 +03:00			`test_log*`
Improve Coverage tooling (#535) * added manual coverage justfile command * a lot of small refactorings of config and argument parsing * feature: support jsonb query param for functions * cleaned up public/private access * make all tests populate with a predefined values to avoid issues with random data 2022-12-27 09:56:27 +03:00			`*.profraw`
chore: update actix and actix-web to 0.7 2018-07-24 12:34:01 +03:00
doc: add docker-compose usage example 2019-08-28 14:04:15 +03:00			`pg_data/`
chore: migrate to TileJSON v0.3 (#330) (h/t @nyurik) * use `tilejson!` to generate json object * use `Bounds` everywhere when appropriate 2022-05-27 14:04:27 +03:00			`config.yml`
Consolidate DB init and tests (#463) * Add justfile to simplify running all the tests * Save all PBF outputs to the text files * Consolidate all tests to reuse the same code * Consolidate database initialization * updated readme with the new instructions Note that while this PR creates "expected" files, the CI cannot validate the generated results because the output is not stable. Eventually we may try to output just the non-geometry values to have reasonable tests comparing against the expected results. 2022-10-28 21:52:39 +03:00			`tests/output/`
Fix non-deterministic CI tests (#724) * a race condition due to duplicated webp.mbtiles and webp.pmtiles * minor cleanup of CI/dockerignore * dependency bump 2023-06-23 06:01:57 +03:00			`tmp/`
Add AWS Lambda support (#1127) This adds the lambda-web crate to adapt the actix App to speak to Lambda by way of the lambda_runtime crate. AWS Lambda has native support for scripting languages to execute a function directly; compiled languages must embed a runtime to fetch incoming events from Lambda and post the responses. This detects the environment variables to start up in Lambda mode instead of the normal HTTP server, and is added as an optional feature. Lambda has five (!) distinct ways of routing HTTP requests to a function; this supports some of them. (Specifically, the most obvious way to do this is with a Function URL, which is newest and simplest, and perhaps with CloudFront, which speaks to the Function URL and not Lambda directly.) The error handling could probably be refined, I was just trying to get this to compile. (Supported: API Gateway HTTP API with payload format version 2.0; API Gateway REST API; Lambda function URLs / Not supported: API Gateway HTTP API with payload format version 1.0; Application Load Balancer) Necessary for #1102 to be able to run the released packages directly, and only having to configure the appropriate environment. --------- Co-authored-by: Yuri Astrakhan <yuriastrakhan@gmail.com> 2024-02-01 21:56:40 +03:00			`.aws-sam/`