Adam Wróbel

Current behavior is also in line with Vue's own `props`. Properties also declare default values by passing a description object and *not* using `data`.

Sorry that it took a while, but I've created a complete repro Gist. Please note how my `main` entry inside `chunks` is empty here: https://gist.github.com/amw/bfcb52b2e05412e6775af53f9531f9d9#file-webpack-stats-json-L11 And `assets` only lists the...

I'm sorry, but this project is no longer maintained as per "Status" section in readme.

Thanks for opening the PR, but this project is no longer maintained as explained [here](https://github.com/amw/jpeg_camera#project-status). I'm going to keep the PR open for other people to see.

Please read about [project status](https://github.com/amw/jpeg_camera#project-status) on the main page.

This won't be needed after capistrano-rails 1.1.2 is released as it adds these lines to it's task definitions: ``` Capistrano::DSL.stages.each do |stage| after stage, "deploy:set_rails_env" end ``` This causes Rails...

That's correct. `-E` is for setting RACK_ENV. Most setups use something like `RAILS_ENV=production unicorn -E deployment`.

No, it does not. I guess that's one way to fix this issue. I do think that setting the env variable when starting unicorn is safer though. That's what the...

I don't have a set of tests, but it fixed my production app without adding anything about gemfile to my `unicorn.rb`. Maybe you were testing without stopping unicorn first?

The main premise of that article is exactly that Alpine is missing Python binary wheels. The article at the end says: > An update: [PEP 656](https://www.python.org/dev/peps/pep-0656/) is under discussion as...