Synology as a repo server

[Patrick Bernard]

Hello,

I have made a munki server with a Synology NAS.
All works (almost) fine.
I can access by http to the munki repo directory but I can't browse the folder named "icons".
It's seems that this name is reserved by the apache server of Synology.
I get an error 403. If I change manually the name, I'm able to browse it.
All others directory is reachable
How can I change the name of this directory in munki (I know that I can change the Icon URL, but not the name of this directory).
Any help would be greatly appreciated !
Thanks a lot
Patrick.

[David Nelson]

I am assuming your repository is at the root level of your web server, otherwise the /icons directory probably wouldn't have this conflict.

It seems like one easy workaround would be to simply put your repository in a subdirectory, as a URL like /repo/icons shouldn't overlap with any built-in directories.

David

--
You received this message because you are subscribed to the Google Groups "munki-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-discus...@googlegroups.com.
To post to this group, send email to munki-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/3ed86945-ede0-4471-9184-b24a0b3f9629%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Gregory Neagle]

Another possibility: make a symlink "product_icons" pointing to the icons directory, then change the client's IconURL to https://fooserver/product_icons

Both changes (moving the entire repo to a subdirectory, or using the symlink) require changing client config on all clients, so they are roughly the same amount of work. David's suggestion is "cleaner"; mine won't completely break clients that don't get the updated config (only icons won't work).

-Greg

To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/F4ED24A9-6263-4317-B564-BD045FA1F6A8%40davidnelson.net.

[tackyy]

Another idea worth exploring is to use the NAS for storing the repo, but have a different machine mount that directory and serve it up to clients. That way you don't have to fight with the NASs apache but still have the benefit of the bulk storage and backup solution you may have in place.

tack

On Dec 7, 2016, at 7:39 AM, Patrick Bernard <loli...@gmail.com> wrote:

[Patrick Bernard]

Hello,

Thank you for your advices ..
Greg's solution works fine ...
My main goal is to set a synology munki repo as a master repository.
I want to use the synchronization feature of the synology shared folder to replicate the munki repo over internet on several another sites.
For that, and for simplicity, I want to use the apache server of the synology. One Synology, one munki server.
Thanks a lot for your support and ideas.
Have a nice day
Patrick