When running elm-test
on Circle CI, your builds will run indefinitely due to an issue with determining CPU usage. The following might help be of help to you.
Configure Circle CI (i.e. circle.yml
) as follows:
machine:
module MyApp | |
class Application < Rails::Application | |
if Rails.env == 'test' | |
require 'diagnostic' | |
config.middleware.use(MyApp::DiagnosticMiddleware) | |
end | |
end | |
end |
namespace :assets do | |
desc 'Precompile assets and upload to S3' | |
task :sync => :environment do | |
assets = build_asset_dir | |
raise 'asset directory is empty: aborting' unless assets.size > 1 | |
invalid_files = build_assets assets | |
delete_old_assets assets | |
invalidate_files invalid_files unless invalid_files.empty? |
When running elm-test
on Circle CI, your builds will run indefinitely due to an issue with determining CPU usage. The following might help be of help to you.
Configure Circle CI (i.e. circle.yml
) as follows:
machine:
dependencies: | |
pre: | |
# install chrome | |
- wget -N https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb -P ~/ | |
- sudo dpkg -i --force-depends ~/google-chrome-stable_current_amd64.deb | |
- sudo apt-get -f install -y | |
- sudo dpkg -i --force-depends ~/google-chrome-stable_current_amd64.deb | |
- sudo rm /usr/local/bin/chromedriver | |
# install chromedriver | |
- wget -N http://chromedriver.storage.googleapis.com/$CHROME_DRIVER_VERSION/chromedriver_linux64.zip -P ~/ |
I have been struggling to start a new project with Phoenix 1.3 and the new vue-cli 3 for Vue.js. There are tons of example already but none of them suited my needs, because:
Assuming that you have Elixir and Phoenix 1.3 are both installed, let's build our new App.