README.md in dockly-0.0.7 vs README.md in dockly-1.0.0

- old
+ new

@@ -130,10 +130,12 @@ - `build_cache` - required: `false` - class: `Dockly::BuildCache` - description: a caching system to stop rebuilding/compiling the same files every time +Need finer control of Docker packages? We also wrote [docker-api](https://github.com/swipely/docker-api). + `foreman` --------- The `foreman` DSL is used to define the foreman export scripts. It has the following attributes: @@ -195,10 +197,13 @@ - description: script hooks for package events - `s3_bucket` - required: `false` - default: `nil` - description: the s3 bucket the package is uploaded to +- `file SOURCE DEST` + - required: `false` + - description: places SOURCE at DEST in the Debian package (can have multiple of these) In addition to the above attributes, `deb` has the following references: - `docker` - required: `false` @@ -209,23 +214,20 @@ - required: `false` - default: `nil` - class: `Dockly::Foreman` - description: any Foreman scripts used in the deb - Demo === ```ruby deb :dockly_package do package_name 'dockly_package' - version '1.0' - release '1' docker do name :dockly_docker - import 's3://dockly-bucket-name/base-image.tar.gz' + import 's3://.../base-image.tar.gz' git_archive '/app' timeout 120 build_cache do s3_bucket "dockly-bucket-name" @@ -235,20 +237,17 @@ output_dir "/app/vendor/bundle" use_latest true end build <<-EOF - run cd /app && echo "1.0-1" > VERSION && echo "#{Dockly.git_sha}" >> VERSION + run cd /app && ./configure && make EOF - # git_sha is available from Dockly end foreman do name 'dockly' procfile 'Procfile' - prefix 'source /etc/dockly_env ' log_dir '/data/logs' - user 'ubuntu' end s3_bucket 'dockly-bucket-name' # ends up in s3://#{s3_bucket}/#{package_name}/#{git_hash}/#{package_name}_#{version}.#{release}_#{arch}.deb end