Hi there,
Are you sure this will work with GA ? Is there no time limit for a running workflow ? IIRC, building mapnik takes time 😅

hi @Joxit
it has already runned :D https://github.com/mathisloge/mapnik/runs/4214019688?check_suite_focus=true

But the limits for open source projects are actually quite high. each job can take up to 6 hours and a workflow up to 72 hours https://docs.github.com/en/actions/learn-github-actions/usage-limits-billing-and-administration

But the workflow only takes ~15 mins . so it is quite ok

Oh, nice ! I will add GA on jawg/docker-mapnik3 then 😄

@artemp this should be ready to merge. There shouldn't be any actions needed other than a merge. The workflow would use the github context to get the secrets / repo names.

Each branch will have its own docker tag
Each tag labeled with v*.*.* will have its own docker tag.
The latest semver will get the latest docker tag

You can see some example tags here:
https://github.com/mathisloge/mapnik/pkgs/container/mapnik

Note, that this uses the cmake build. For node-mapnik or python-mapnik I will now find a way to use pkg-config instead of mapnik-config.

Or is there a desire to use SCons to build mapnik on the Docker image?

@hiddewie thanks for your reviews. I've added more dirs to the ignore list. So it is reduced to 33MB.
and splitted the commands as suggested.

Looking forward to see this PR merged. This will help with some custom plugins we created.

@zy6p you could actually use the containers already. https://github.com/mathisloge/mapnik/pkgs/container/mapnik/10503672?tag=docker

@zy6p you could actually use the containers already. mathisloge/mapnik/pkgs/container/mapnik/10503672?tag=docker

Great! My laptop is M1 mac, and pre-build mapnik doesnot support arm. But these containers can work 😃

Any movement on this?

Any movement on this?

I'm planning to take a look at this when I have time, I know it was a long time.

Meanwhile, is there any reasons you can't simply

npm install @mapnik/mapnik

?