tombh / peas Goto Github PK

This is a great project. Is there any interest in adding the option to build from a docker-compose.yml file instead of buildstep the way https://github.com/project-nsmg/figure does?

Gotta catch 'em all!

Grack seems like it could be a good solution for a quick and lightweight Git server. It only works over HTTPS, so I'm wondering what would be the best way to provide authentication.

We could make the Git Remote include a password, like so; https://user:[email protected]/peasapp.git, but then it's in plaintext and associated with the config for that particular repo.

Ideally I want to recreate the SSH handshake in pure ruby and use public/private keys with the Git SSH protocol.

For the life of me I can't get the CLI specs to run alongside the normal API specs on Travis. In fairness the CLI folder does represent a completely separate code base with its own Gemfile. I guess the usual scenario is to put the CLI into a separate repo, but I want to avoid that, I like having just one centralised repo.

The error I keep getting is;

/home/travis/build/tombh/peas/cli/spec/spec_helper.rb:3:in `require': cannot load such file -- webmock/rspec (LoadError)
    from /home/travis/build/tombh/peas/cli/spec/spec_helper.rb:3:in `<top (required)>'
    from /home/travis/build/tombh/peas/cli/spec/cli_spec.rb:1:in `require'
    from /home/travis/build/tombh/peas/cli/spec/cli_spec.rb:1:in `<top (required)>'
    from /home/travis/build/tombh/peas/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.14.8/lib/rspec/core/configuration.rb:896:in `load'
    from /home/travis/build/tombh/peas/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.14.8/lib/rspec/core/configuration.rb:896:in `block in load_spec_files'
    from /home/travis/build/tombh/peas/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.14.8/lib/rspec/core/configuration.rb:896:in `each'
    from /home/travis/build/tombh/peas/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.14.8/lib/rspec/core/configuration.rb:896:in `load_spec_files'
    from /home/travis/build/tombh/peas/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.14.8/lib/rspec/core/command_line.rb:22:in `run'
    from /home/travis/build/tombh/peas/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.14.8/lib/rspec/core/runner.rb:80:in `run'
    from /home/travis/build/tombh/peas/vendor/bundle/ruby/1.9.1/gems/rspec-core-2.14.8/lib/rspec/core/runner.rb:17:in `block in autorun'

Please could you take a look on https://github.com/dawn/dawn and say, what are the differences, pros and cons of each implementation?

Would be great to make this easy to install :)

This is the only blocker to fully support multiple pods

For instance postgres needs some auth settings in pg_hba.conf

Currently when starting Peas with existing data in the database, no attempt is made to reflect the stored scaling profiles of apps by booting the relevant Docker containers for the app's processes. This could also possible be tied into some kind of health monitoring feature.

When installing the script on Ubuntu 14.04 it hangs and outputs a bunch of single line ys.

....
Get:4 http://mirrors.digitalocean.com/ubuntu/ trusty-updates/main git-man all 1:1.9.1-1ubuntu0.1 [698 kB]
Get:5 http://mirrors.digitalocean.com/ubuntu/ trusty-updates/main git amd64 1:1.9.1-1ubuntu0.1 [2,627 kB]
Get:6 http://mirrors.digitalocean.com/ubuntu/ trusty/main cgroup-lite all 1.9 [3,918 B]
Fetched 7,553 kB in 0s (12.8 MB/s) 
y
y
y
y
y
y
y
...

So you can run one-off commands for an app.

Thomas,

Thank you for this amazing project. I would love to help.
Did you have some ideas about how can we implement this feature?

Thx.

The sudden and massive response to Peas has been unexpected. I'm deeply flattered and hugely excited. Thank you. It's clear that Peas resonates with people and so it's paramount that I work with that. I don't have an exact and unalterable plan, so I want to take this opportunity to get as much feedback about what people hope to get from Peas.

I'd like to hear from both technical people and non-technical people, whether you have years of experience or are starting out in the field. I'd like to hear about what you don't want (for example a couple of people on HN expressed a dislike for Chef Server, which I happen to agree with) just as much as what you do want. I want to hear big and small ideas.

Personally, the things I'd like to see are less to do with PaaS-specific features and more to do with the conditions that inspire healthy living software: comprehensive and engaging documentation, a culture that inspires test writing, lively discussions and not taking ourselves too seriously. All of which will of course lead to the added bonus of creating the highest quality PaaS available to mortals.

Could not connect to a primary node for replica set #<Moped::Cluster:14474880 @seeds=[<Moped::Node resolved_address="127.0.0.1:27017">]>

Ruby    /var/lib/gems/1.9.1/gems/moped-2.0.0.beta6/lib/moped/cluster.rb: in with_primary, line 248
Web GET peas.local/

The above error was seen after following the Vagrant installations instructions and visiting peas.local:4000. Does anyone know how to resolve this?

Apps can have custom domains that the proxy can recognise as belonging to a particular app.