4 ms·
They continue to eschew using `foreman export` / `foreman run` / `bundle install --binstubs` in the docs, when it does simplify a lot of the installation / upgr
by mikewhy 13y ago
They continue to eschew using `foreman export` / `foreman run` / `bundle install --binstubs` in the docs, when it does simplify a lot of the installation / upgrade process. I've even sent pull requests that add capistrano / unattended deploy support that have gone nowhere.
I love the software, but the installation / upgrade docs are always hell compared to your average `git pull && bin/rake db:migrate && foreman export`.
Having said all that, I'm running it on an old box with 512MB of ran and it's tolerable.
- sytse 13y agoGitLab.com co-founder here. Thank you for the suggestions. There is a proposal in the core team to switch to --binstubs. We will also move the run logic from init.d to the bin directory so you can also use it with monit/god/bluepill/omnibus/chef/foreman.