2014-02-01 20:41:05 +01:00
|
|
|
#######
|
|
|
|
|
distnet
|
|
|
|
|
#######
|
|
|
|
|
|
|
|
|
|
This example provides an example of the `remote` extras tool,
|
|
|
|
|
used to build and share binary packages in the context of an intranet.
|
|
|
|
|
|
|
|
|
|
Usage
|
|
|
|
|
#####
|
|
|
|
|
|
|
|
|
|
Run the following in order in three distinct consoles:
|
|
|
|
|
|
|
|
|
|
1. start the server::
|
|
|
|
|
|
|
|
|
|
cd server && ./start.sh
|
|
|
|
|
|
|
|
|
|
2. publish a package::
|
|
|
|
|
|
|
|
|
|
cd app && waf configure_all build_all package publish
|
|
|
|
|
|
|
|
|
|
3. use a package in a project::
|
|
|
|
|
|
|
|
|
|
cd app2 && waf configure_all build_all
|
|
|
|
|
|
|
|
|
|
Features
|
|
|
|
|
########
|
|
|
|
|
|
|
|
|
|
- a simple cgi server helps uploading/distributing the files
|
|
|
|
|
- headers can be redistributed
|
|
|
|
|
- binary data can be redistributed
|
|
|
|
|
- configuration scripts can be redistributed along with build rules
|
|
|
|
|
- packages are compressed on the server
|
|
|
|
|
|
|
|
|
|
Limitations
|
|
|
|
|
###########
|
|
|
|
|
|
|
|
|
|
- Waf and Python cannot be distributed as a packages (may require another process or an auto-update system)
|
2014-02-09 18:23:26 +01:00
|
|
|
- Once a folder is written to the cache it is never updated again
|
|
|
|
|
- There is no integrity verification aside from the package compresssion
|
|
|
|
|
- Files submitted must be small enough
|
|
|
|
|
- Server server security and access right are to be implemented by the user (do it yourself!)
|
2014-02-01 20:41:05 +01:00
|
|
|
|
