Some people have reported that they are unable to access the apposite repository since they are behind an authenticating corporate
firewall. We''re working on a general solution to this in the HTTP client infrastructure but in the mean time this FAQ explains
how you can use rsync to bring a local mirror inside your firewall. This FAQ also applies if you just want to be a good community
citizen and offer a regional mirror for the NetKernel community.
1. First step is to get a copy of rsync (http://samba.anu.edu.au/rsync/) or talk to your friendly neighbourhood *nix sysadmin.
2. Run the following command to mirror the apposite repository to a local directory...
This will create a directory called "repo" containing two sub-directories "packages" and "netkernel". You now have a full mirror of the apposite repository.
3. You now need to decide how you want to access it locally with NKSE''s apposite client. You can keep the mirror directory on your local machine or you could put it on an internal corporate web server. You could even put it on a SAMBA share and mount that. Wherever you place it you need to tell your development copy of NKSE apposite client to use this repository instead of the public server. To do that follow these steps:
a) Go to the apposite admin panel: http://localhost:1060/apposite/admin/
b) Click the "Edit" button for the "NetKernel.org Base URI" (by default it will be http://apposite.netkernel.org/repo/). Change this to the base URI of your mirror''s repo/ directory (don''t forget the trailing slash - its has to be an absolute URI to the directory path).
For example:
If you have a copy on your local hard drive at location C:\\1060mirror\\repo you''d enter "file:///C:/1060mirror/repo/" (sorry but Windows file URI''s need triple slashes and care with drive letters etc - if in doubt try the URI in your browser address bar first)
If you have it on an internal corporate web server http://ourmirror.bigcorp.com/repo/ then just enter that http URL.
If you have it mounted SAMBA share then use a file: URI to point to that mount point.
At any time you can make sure you''ve got the correct base URI by clicking "Test Connection".
That''s it - all you need to do is to arrange to run rsync every couple of days to keep it in sync (or talk with/bribe your sysadmin to set that up as a cron job on a utility server).
Security Notes
The public apposite repository only has signed official releases of 1060 authorized packages. Both the individual packages and the complete repository metadata are signed. When you have a local copy inside your firewall the NKSE apposite client still performs full repository and package authentication and verification before permitting anything from the the mirror to be installed. So even though the library is local you can still treat it as the authentic trustworthy source of NKSE libraries and updates.
1. First step is to get a copy of rsync (http://samba.anu.edu.au/rsync/) or talk to your friendly neighbourhood *nix sysadmin.
2. Run the following command to mirror the apposite repository to a local directory...
rsync -rv rsync://apposite.netkernel.org/download/repo/ repo/ |
This will create a directory called "repo" containing two sub-directories "packages" and "netkernel". You now have a full mirror of the apposite repository.
3. You now need to decide how you want to access it locally with NKSE''s apposite client. You can keep the mirror directory on your local machine or you could put it on an internal corporate web server. You could even put it on a SAMBA share and mount that. Wherever you place it you need to tell your development copy of NKSE apposite client to use this repository instead of the public server. To do that follow these steps:
a) Go to the apposite admin panel: http://localhost:1060/apposite/admin/
b) Click the "Edit" button for the "NetKernel.org Base URI" (by default it will be http://apposite.netkernel.org/repo/). Change this to the base URI of your mirror''s repo/ directory (don''t forget the trailing slash - its has to be an absolute URI to the directory path).
For example:
If you have a copy on your local hard drive at location C:\\1060mirror\\repo you''d enter "file:///C:/1060mirror/repo/" (sorry but Windows file URI''s need triple slashes and care with drive letters etc - if in doubt try the URI in your browser address bar first)
If you have it on an internal corporate web server http://ourmirror.bigcorp.com/repo/ then just enter that http URL.
If you have it mounted SAMBA share then use a file: URI to point to that mount point.
At any time you can make sure you''ve got the correct base URI by clicking "Test Connection".
That''s it - all you need to do is to arrange to run rsync every couple of days to keep it in sync (or talk with/bribe your sysadmin to set that up as a cron job on a utility server).
Security Notes
The public apposite repository only has signed official releases of 1060 authorized packages. Both the individual packages and the complete repository metadata are signed. When you have a local copy inside your firewall the NKSE apposite client still performs full repository and package authentication and verification before permitting anything from the the mirror to be installed. So even though the library is local you can still treat it as the authentic trustworthy source of NKSE libraries and updates.
